what i do with your data
i'm sharath. i run incasely by myself. this page is the honest version of what i collect and why.
who this is
incasely is a solo product. there isn’t a company behind it yet, and nobody else is sitting around reading your board. if you have a question, email hi@dupenodi.dev.
what i collect
- account: your email and a password, or whatever google shares if you sign in that way.
- pins: the urls, notes, images, and other things you save, plus the bits i fetch to build the card — title, preview, and a copy of media so the link doesn’t go missing later.
- session: an auth cookie so you stay signed in.
i don’t run ads, and i don’t sell your account or your board.
the browser extension
the chrome extension is how you pin from a tab. it talks only to app.incasely.com, using the same sign-in cookie as the web app. it does not send every page you visit.
- when you pin: the current tab’s url, title, and any text you selected. a content script on http(s) pages can read those three things so the toolbar and right-click menu work. nothing is uploaded until you pin, import, or click the in-page pin.
- on x.com / twitter.com: a pin control on posts, and an optional import of your bookmarks. import uses the same bookmark and thread requests the site is already making in that tab. it does not take your x password.
- on github.com: a pin control on repos, and an optional import of starred repos via github’s stars api while you are on that page.
- on this device: chrome local storage keeps tweet ids you already pinned, so the pin mark stays correct. no browsing history is stored.
pins land on your incasely account. the extension does not sell data, run ads, or inject other companies’ scripts.
what the product does with your pins
incasely reads what you save so it can tag it and bring it back when it matches what you’re looking for. that includes software — language models included — looking at your pins to describe them, tag them, and search them.
i won’t sell that content, and i won’t use your pile as a marketing dataset. if a model provider is involved, it’s only to run the product for you. your board is not training data.
public vs private
everything you save starts private. sharing is something you turn on. if you mark a pin public, anyone can see it, even without an account. treat that the way you’d treat posting it yourself.
export and delete
you should be able to leave with your stuff. a proper export (json, csv, markdown) is still on the way. until that button exists, email hi@dupenodi.dev and i’ll send you a copy or delete the account.
deleting your account should remove your pins from the product. if something is left behind, write me and i’ll take care of it.
cookies
two cookies matter: the auth one that keeps you signed in, and a visitor id from datafast so i can see which pages and actions actually help people find the product.
who else sees data
hosting and auth go through the usual infrastructure. today that’s supabase. analytics go through datafast (pageviews, signups, and saves — not the contents of your board). if you use “continue with google,” google sees whatever they normally see for that sign-in.
kids
incasely isn’t meant for children. if you’re under 16, please don’t make an account.
changes
if i change something here that actually affects you, i’ll update the date at the top.