Privacy Policy
Revised November 14, 2026 (app version 1.2). Contact: budael@icloud.com
In short
- Ygra works without an account. Your tasks, habits, Lock in and Screen Time data stay on your phone. Only what is described below reaches our server: the anonymous “Now in Lock in” counter and, if you join a squad, the numbers your squad sees.
- Screen Time data — which apps you block and how long you spend in them, what you tried to open and when, pull hours — never leaves your phone: not to our server, not to the assistant. If you join a squad, only numbers go to the server: minutes in Lock in today and this week, how many times today you tried to open a blocked app, days without breaking, and whether a Lock in is running now. App names, never.
- The global “In Lock in now” counter receives only an anonymous status icon and session time; you can turn it off.
- No ads, no tracking, no selling of data. No third-party analytics.
App blocking and Screen Time
Lock in, schedules and the morning lock use Apple’s Screen Time APIs with your permission. Your app selection is stored on the phone as encrypted system tokens: Ygra cannot see which apps you chose. Taps on the block screen (pulls), their times and your answers to “Why?” are stored only on the phone and shown only to you — in the regime report, the weekly report and pull hours. If you’re in a squad, it gets only today’s number of pulls — no app names, times or answers. To revoke access: iPhone Settings → Screen Time.
Global “In Lock in now” counter
When you start Lock in, the app — without an account, using an anonymous random id in Supabase — sends our server the status icon you picked (one of 8 presets, not custom text) and the session start and end time. This is used only to show how many people are in Lock in right now. To turn it off: Settings → Notifications → “Global ‘In Lock in now’ counter”. Anonymous ids unused for 30 days are deleted automatically.
Account and sync (optional)
If you sign in (email and password or Sign in with Apple), the following syncs through our server on Supabase: tasks and projects, habits and check-ins, log, charge, targets, rituals, templates, Lock in profiles and schedules (name, duration, strictness — not the app list), Lock in session minutes and modes, settings and your name. Photo attachments stay on the phone. Only you can access your data (Row Level Security). With Sign in with Apple, Apple may share a private relay email and your name (first sign-in only).
Squad (optional, needs an account)
A squad has up to 10 people. Members see your nickname, your status (a preset or your own text), whether you’re in Lock in, the numbers listed in “In short”, and feed events: started and finished Lock in, joined and left, and gave up via emergency exit. The give-up event and its push go to the squad by default; you’re told this when joining and can turn it off in squad settings. In a joint Lock in, participants see each other’s state: holding, broke, left, done.
Moderation: you can report a member (a reason and optional text). The report and the member’s nickname and status are stored in our Supabase database and forwarded to the developer on Telegram; we review reports within 24 hours. You can also block a member, the squad creator can remove one, and anyone can leave. Squad names, nicknames and statuses are filtered for profanity. Leaving deletes your membership; deleting your account deletes all your squad data, events, your nickname in report copies, and push tokens.
Push notifications
Reminders are local, created on the phone. Squad pokes, “a friend gave up” and joint Lock in invites arrive as push notifications: our server (a Supabase Edge Function) sends them through the Expo Push Service and Apple Push Notification service. For this we store your device’s push token linked to your account. Each type of push can be turned off in Settings → Notifications; a push you turned off is not sent.
AI assistant (optional)
If your iPhone has Apple Intelligence (iOS 26), the assistant answers with Apple’s model right on the phone: nothing is sent to us or anyone else. Voice: your iPhone recognizes speech itself (on-device recognition) and audio never leaves it; microphone and speech recognition access is requested only on the first tap of the mic. Answers are read aloud by the iPhone’s system voice. Otherwise (or if you chose Cloud) the cloud assistant is used, which needs an account:
When you message the assistant, our server receives your message and a short summary: today’s and tomorrow’s tasks, this week’s habits and charge, monthly targets, and the log only if you turned that on. The server passes them to Anthropic’s Claude model to get a reply. Anthropic does not use this data for training. We keep only usage records (time, token counts) for limits; the chat itself stays on the phone. Lock in and Screen Time data are never sent to the assistant.
Support and bug reports
If you contact support from the app, we receive your text, a reply email (if you enter one), a screenshot (if you attach one) and a technical summary: app version, device model, iOS version, language, theme, font scale, a random install id and your account id (if signed in). Task, habit and log content and Screen Time data are not sent. The message is stored in our Supabase database and forwarded to the developer on Telegram; the screenshot is not stored in the database. We keep messages as long as needed to reply, no longer than 12 months, and delete them on request.
Other
- You pick photos for attachments and bug screenshots; write-only Photos access is used only to save posters.
- Face ID is checked by iOS; Ygra receives no biometric data.
- App updates download from Expo servers (EAS Update); requests carry only technical data (version, platform).
Deleting data
Profile → account → Delete account: the account and all server data, including support messages and squad data, are deleted at once; the app wipes the phone. Without an account, delete the app. Questions: budael@icloud.com.
Children
Ygra is not intended for children under 13 and does not knowingly collect their data.
Changes
We will post changes on this page and in the update notes.