privacy policy.

clinch keeps your intercept history in a local file on your phone (events.jsonl, inside the app's sandboxed app group). that file holds the things the app uses to draw your patterns, run coach, and tally minutes saved:

• which app each intercept fired for (instagram, tiktok, etc.)
• which interceptor showed (breathing, did-you-know, etc.)
• which intention you picked on the reflect screen (bored, avoiding, habit, ...) — if you picked one
• whether you continued to the app or stayed in clinch
• the time the intercept happened
• which day-of-arc you were on

this file is never uploaded. nobody — not me, not apple, not the analytics service — sees its contents. uninstalling clinch deletes it along with the rest of the app's data. the reset onboarding button in customize also wipes it (along with everything else).

clinch sends a small set of anonymous aggregate signals to telemetrydeck, a privacy-first analytics service used widely in indie iOS apps. these signals help me see whether the app is actually working at population scale — "are people staying more after a breathing moment than a tile puzzle?" — without seeing anyone's individual story.

here's the full list of what gets sent:

signal	what it means	parameters
app.launched	the app was opened cold.	none
intercept.shown	an interceptor started rendering.	interceptor type · day-bucket
intercept.stayed	you tapped "i'll stay" on the reflect screen.	interceptor type · intent · day-bucket
intercept.proceeded	you tapped "continue to [app]" on the reflect screen.	interceptor type · intent · day-bucket
intercept.skipped	you dismissed the reflect screen without picking.	interceptor type · day-bucket
coach.suggestions.shown	coach surfaced a pattern-based block suggestion.	count
coach.suggestion.accepted	you tapped "block this window" on a coach card.	weekday · start-hour · intent
coach.locked.tapped	a free user tapped the coach pro teaser.	none

the day-bucket parameter is coarse on purpose — it groups your day-of-arc into one of 0 / 1-7 / 8-29 / 30+. that's enough for me to see if users behave differently in their first week vs after a month, without leaking a per-user lifetime number. no individual user can be pinned to a bucket.

crucially, which app you were intercepted on (instagram, tiktok, etc.) is not sent. the analytics tells me what users did, not which app they did it on.

explicitly, none of the following ever leaves your device:

• your name
• your email
• your phone number
• your location
• your ip address (telemetrydeck doesn't retain it)
• your apple id
• your idfa / advertising id
• which apps you opened
• screen recordings or screenshots
• health, fitness, contacts, or photos data
• any cross-app tracking signals
• any data sold to anyone, ever

the toggle that runs the whole thing is at customize → privacy → help improve clinch. switch it off and analytics.signal silently no-ops on every call — no events leave the device. the toggle is read on every signal (no caching) so the change takes effect on the very next intercept. no relaunch needed.

delete everything. uninstalling clinch wipes the local events.jsonl along with all app data. if you'd rather start fresh without uninstalling, customize → about → reset onboarding clears the event log and sends you back to the cinematic.

screen time access. the block feature uses apple's screen time (familycontrols + deviceactivity) framework. when you grant it, the system shows you a prompt written by apple; clinch never sees the apps you pick (apple gives the app opaque tokens, not names). revoking access at any time: iOS settings → screen time → see all activity → app limits / always allowed → remove clinch's app group.

only one third-party processor handles any of your data:

• telemetrydeck — receives the anonymous aggregate signals listed above (if you've left the opt-in on). gdpr-compliant by design, no idfa, no ip retention. their privacy policy: telemetrydeck.com/privacy.

analytics for this website (vercel web analytics) measures page views with privacy-preserving methods — no cookies, no cross-site tracking. that's separate from the app and not tied to any data inside it.

payments for clinch pro are handled by apple's app store. clinch never sees your card or apple id; it only receives an anonymous "user is subscribed" signal from storekit.

clinch is not directed at children under 13 and does not knowingly collect data about them. if you believe a child has installed the app and you'd like the local data on their device deleted, simply uninstall clinch from that device — that wipes everything.

because clinch keeps your intercept data on your phone and the analytics service collects no personal data, most "right to access / right to delete" requests are answerable in one step: uninstall clinch, or flip the analytics toggle off.

if you'd still like a written confirmation that no personal data is held about you, email vedantjainben10@gmail.com and i'll reply within 30 days. that's also the address for any gdpr / ccpa / lgpd / pipeda request, or any other privacy question.

if the data clinch collects ever changes — new event, new parameter, new third party — this page is updated and the "last updated" stamp at the top is bumped. material changes (new third party, new category of data) will also be announced in the app and on @vedantj_03 before they take effect.

privacy questions, take-down requests, or just curious how a signal gets routed — email vedantjainben10@gmail.com. one person reads them. usually replies within 24–48 hours.