tinklet stores your raw, unfiltered thinking and sends it to two ai providers to generate replies. this page says exactly what's kept, who sees it, and how to get it back or make it disappear.
tinklet is made and run by two people, based in Australia. there is no separate company behind it. if you have a question about your data, a request, or a complaint, the fastest way to reach us is email: raiyannoor2000@gmail.com.
named honestly, table by table:
tinklet never asks whether you have a diagnosis, and nothing in the product is designed to infer one. that would be health data, we have no use for it, and collecting it would change everything above. there are no ads anywhere in tinklet, and your data is never sold, rented or shared with anyone for marketing purposes.
tinklet is built on a small number of outside services. each one sees only what it needs to do its job, and none of them are permitted to use your content for anything beyond that job.
| service | what it's for |
|---|---|
| supabase | database and authentication — where everything above actually lives |
| vercel | hosting the app and its server routes |
| openai | generating tink's chat replies (gpt-4o-mini) and transcribing voice messages (whisper) |
| google (gemini) | extracting structured context from your threads, and as a fallback for chat replies if openai is unavailable |
| google (oauth) | signing you in |
| posthog | product analytics — which features get used |
| sentry | error reporting when something breaks |
when you talk to tink, your words are sent to openai and, for some background steps, to google, to produce a reply or extract structure from what you wrote. both providers are used on their paid api tiers, and both providers' api terms state that content sent through the paid api is not used to train their models. tinklet itself never trains a model on your content — there is no fine-tuning pipeline, and nothing you write is used to make tink "smarter" for anyone else.
your threads, transcripts, notes and to-dos are kept for as long as your account exists. deleting your account (§7) removes all of it immediately and irreversibly from tinklet's database. supabase's own point-in-time backups age out on their own rolling window and are not something tinklet can selectively purge from, so a deleted account may persist in a backup for a short time before that window closes.
analytics and error records in posthog and sentry are pseudonymous, not tied to your name, and expire on each provider's own retention schedule. the in-app deletion flow does not reach into posthog to remove your analytics profile — there is no server-side key configured for that today. if you want it removed sooner than posthog's schedule, email raiyannoor2000@gmail.comand it'll be requested by hand.
you can download a complete copy of everything tinklet holds about you at any time, from the account menu → privacy & data → download my data. that covers access and portability in one step. the same screen has a delete-everything option that erases your account immediately and cannot be undone.
if something tinklet holds about you is wrong, email raiyannoor2000@gmail.comand it'll be corrected. if you're not satisfied with how a request was handled, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.
every table in the database is protected by row-level security scoped to the signed-in owner, so one user's threads are not reachable by another user through the normal api path. tinklet is currently in private beta, gated by invite, which limits who can reach the product at all. there is no service-role key anywhere in the codebase — nothing bypasses the per-user access rules, including tinklet's own server routes.
tinklet is intended for people aged 16 and over.
if this policy changes in a way that matters — what's collected, who it's shared with, or your rights over it — you'll get an email before it takes effect. the date at the top of this page always reflects the current version.