Privacy Policy
Draft prepared October 14, 2026 · Not yet effective
1. Scope and operator
This draft describes MyFocusRing, its mobile app, and this website. The legal operator and privacy contact must be confirmed before this policy takes effect.
2. Information used to provide the app
Email sign-in uses Supabase authentication. This involves the email address supplied by the user and an account identifier. The app also handles tasks, scheduled times, and recurrence preferences. Whether task content stays on the device or is stored in a backend must be confirmed in the final policy.
3. How information is used
Account information supports authentication and account access. Task details and preferences support the planner and reminders. The final policy must identify any additional uses supported by the released build.
4. Notifications and device storage
The app schedules local preparation and start notifications, subject to device permission and settings. Notification permission can be changed in the device settings. The app uses device storage for session information. This website stores a color-theme preference locally if you choose a theme.
5. Service providers and disclosure
Supabase provides account authentication. The website hosting service may process connection information needed to serve and secure the site. The operator must confirm all additional services, SDKs, logging, international processing locations, and circumstances of disclosure before publication.
6. Analytics, advertising, and tracking
This website implementation does not include advertising pixels or third-party analytics scripts. The mobile app’s SDKs and the hosting platform’s practices must be reviewed separately; this statement is not a claim that no personal information is collected.
7. Retention and deletion
The final policy must state how long account information, task content, logs, and backups are retained; how account and associated data deletion can be initiated; and any lawful exceptions. Removing the app from a device does not necessarily delete a server-side account.
8. Choices and requests
You can manage notification permissions in your device settings and clear this website’s theme preference by clearing site data. Before launch, the operator must publish a working privacy contact and instructions for access, correction, export, and deletion requests, as applicable.
9. Security
The service should use reasonable safeguards suited to the information it processes. No transmission or storage method can be guaranteed completely secure. The final policy must accurately describe implemented safeguards without promising absolute security.
10. Children and regional rights
The operator must confirm the intended age audience and applicable regional requirements before launch. This draft does not represent that child-specific consent processes or every regional rights workflow have been implemented.
11. Changes and contact
The final policy will display its effective date and explain how material changes are communicated. A verified operator name and privacy contact are required before this draft becomes effective.