Last updated: [date]
This policy explains what DIVE IN collects, why, and the choices you have. DIVE IN is built around a promise from our product principles: the app should disappear when you work, and your data should stay yours.
Information we collect
DIVE IN stores the following on your device as part of your personal flow record:
- Session records: when a session starts and ends, its length, and whether the entry ritual and review were completed.
- Self-reflections you choose to give on the watch: a 1 to 5 rating of how deep you went and how much resistance you felt before starting. These are learning signals, never scores shown to others.
- Context tags you confirm: time-of-day, coarse location (only if you grant location access), and project or event labels you pick from suggestions. You may also create your own tags.
- Optional journal notes: free-text thoughts you write on your iPhone. Entirely optional, never required.
- A gentle weekly goal, if you turn it on: only a target count you set for yourself.
- Health context, only if you grant HealthKit access: a non-scored statement such as "you seemed calmer at the end." We do not read or store continuous heart-rate or health metrics for scoring.
We do not require you to create an account to use DIVE IN.
How we use information
- To show your personal flow journal and timeline on your iPhone.
- To pre-fill likely context tags from time, location, and calendar so review takes seconds.
- To present a gentle weekly mirror that states your rhythm, with no ranking or comparison.
- To improve the ritual over time, for example through optional copy variations of the entry questions.
We do not use your sessions to score, rank, or compare you, and we do not build advertising profiles from them.
Data storage and security
Your session records, notes, and tags are stored locally on your devices and, if you enable sync, across your own Apple devices via your iCloud account. We do not upload the content of your sessions to our servers for storage. Where we operate backend services, such as delivering optional ritual copy updates, we handle data with standard security practices and minimize what is processed.
Third-party services