Last updated: [PUBLICATION DATE]
Effective: [EFFECTIVE DATE — pending release review]
1. Operator and contact
The Routine Planner is operated by [PUBLIC OPERATOR / LEGAL NAME], [POSTAL ADDRESS, COUNTRY]. Contact: [MONITORED SUPPORT EMAIL].
These details will be completed before this policy takes effect. The website’s support page and operator notice provide the current contact status.
2. Which planner this covers
The standalone planner supports daily tasks, weekday templates, completion times, skipped tasks, measurements and ratings, journal entries, manual meals and nutrient values, shopping lists and reports. It has a local demo mode and optional account access. Account access and registration depend on the deployment configuration.
The existing hosted German planner is a separate service with a different backend. Its data is not automatically transferred into the standalone planner. Its operator must provide the applicable notice before any migration or replacement takes place.
3. Data you enter
| Data | Purpose |
|---|---|
| Email and authentication information, when accounts are enabled | Sign-in, account confirmation and recovery through Supabase |
| Tasks, templates, completion times and skipped states | Daily planning and history |
| Measurements, ratings, journal text, meals and nutrient entries | The records and summaries you choose to maintain |
| Shopping lists | Planning purchases |
| Workspace revisions and backup copies | Sync, conflict detection and restoration |
| Technical request information processed by hosting/authentication providers | Delivery, authentication and service security; exact retention to be confirmed |
Journal text, measurements and meal entries may reveal health or other sensitive information. Enter only what you need for your own planning. The planner does not need medical records to manage a checklist.
4. Local storage, offline use and shared devices
Demo data and account-specific working copies are stored in the browser. The local demo uses a separate storage key and is not automatically uploaded to an account. The offline app shell caches application files after an online visit. Authentication and sync requests are not cached by that app-shell service worker.
Authentication sessions and offline working copies may remain on the device. Signing out does not by itself remove all saved planner copies. Use the planner’s local-data removal control or clear the relevant site’s browser storage when you want to remove them. Clearing local storage does not delete a cloud account or its cloud workspace. Browser copies are not encrypted against other users of the device.
5. Accounts and cloud sync
When enabled, Supabase handles authentication and stores the signed-in account’s synced workspace and cloud backup history. The planner separates account-specific drafts and checks revisions to prevent silent overwrites. Offline edits may remain only on the device until a successful sync.
The intended production account relationship with FitnessTracker is [CONFIRM SHARED OR SEPARATE AUTH ACCOUNTS]. If accounts are shared, deleting the shared account can also remove associated data in the other product. That scope must be explained in the released deletion flow. Signing in on one website does not automatically sign you in on another origin.
6. Exports, reports and migration
JSON exports and printed or saved reports can contain private planner data. Reports let you choose whether to include journal entries. Store exported files securely; deleting browser or cloud data does not recall files you already downloaded or shared.
Imports require an explicit choice of source and destination. Recovery exports from the old website preview may contain copies from multiple accounts used on that device. Select the intended copy. The legacy converter is partial: read its warnings and keep the original export until you verify the destination. Exporting a file does not transfer authentication sessions or automatically grant access to another account.
7. Providers and processing locations
The intended standalone setup uses Cloudflare for application hosting and Supabase for optional authentication, database storage and cloud history.
- Supabase production project/region: [CONFIRM PROJECT AND REGION].
- Hosting and authentication request-log retention: [CONFIRM RETENTION].
- Processor arrangements, subprocessors and any international-transfer safeguards: [CONFIRM AGAINST THE SELECTED PRODUCTION SERVICES].
The website shop, native FitnessTracker and future Rise app have separate purposes and are not covered by this planner notice.
8. Purposes and legal bases
Planner data is used to provide the planning, storage, reporting, recovery and sync features described above. Before account registration opens, the operator must confirm and document [ARTICLE 6 BASIS FOR EACH PURPOSE], and, where sensitive data is processed, [APPLICABLE ARTICLE 9 CONDITION AND REQUIRED CONSENT FLOW].
Entering sensitive text is not, on its own, a substitute for a reviewed explicit consent process. This draft does not assert that such a production process has already been verified. Any consent-dependent feature must explain withdrawal and its consequences before collection starts.
9. Retention and deletion
Local copies persist until removed or cleared by the browser. Export files remain where you save them. The production retention periods for cloud workspaces, application backup history, provider backups and inactive accounts are [RETENTION PERIODS TO CONFIRM].
Cloud deletion, identity verification and any shared-account consequences must be documented and tested before account access opens. [CONFIRM ACCOUNT DELETION PROCESS, REQUEST CONTACT AND BACKUP EXPIRY]. Removing a local copy and signing out are not cloud-account deletion.
10. Your data rights
Depending on the applicable law and processing basis, you may have rights of access, correction, erasure, restriction, objection, portability and withdrawal of consent. You may also complain to the competent supervisory authority.
Requests will use [MONITORED SUPPORT EMAIL], with proportionate verification of identity. The operator must establish this process before publication. Under GDPR, requests generally require a response without undue delay and within one month; permitted extensions require notice and reasons. See GDPR Articles 12–22.
11. Eligibility and changes
Minimum age and the corresponding registration safeguards are [CONFIRM PLANNER ELIGIBILITY POLICY]. The tracker’s age policy is not automatically the planner’s.
The effective version will identify its publication date and explain how material changes are communicated. Contact and policy changes will be reflected on this page.