Quit profile
Country, region, cigarette size, cigarettes per day, years smoked, cigarettes in one pack, cost of one pack today, and taper mode.
Internal draft - not published
QuitMap Privacy Policy Draft
This page is a working draft for app-store and domain preparation. It is not final legal advice, not published, and must be reviewed before Apple App Store or Google Play submission.
- Status
- Draft only
- Public URL
- Not published
- Last internal update
- May 29, 2026
- Owner
- QuitMap project, legal owner pending
1. Scope
QuitMap is being built as a self-awareness and planning tool for adults who want to understand their cigarette history, reduce smoking over time, and review their own habit patterns. It is not medical advice and does not replace a clinician, quitline, emergency service, or local health authority.
The current local MVP stores information on the user's device only. Future hosted versions may use Supabase, push notification providers, app-store billing providers, analytics, and support tooling after separate review.
2. Data we handle
Progress records
Token events, smoked or skipped logs, craving logs, daily receipts, progress history, and recovery estimates.
Spend estimate details
Past-year edits, selected currency, and number-quality signals.
Body Load inputs
Caffeine, alcohol, and replacement nicotine comparison inputs used to detect substitution patterns.
Notification settings
Quiet hours, opt-out state, permission status, snooze settings, and future device-token records.
Account and billing
Future sign-in identity, subscription status, billing platform, and support request content if enabled.
3. How data is used
- Calculate lifetime cigarette count, distance, cost, and number-quality notes.
- Build a gradual taper schedule and show next-token timing.
- Generate local daily receipts, progress summaries, and review reports.
- Detect possible substitution patterns across nicotine, caffeine, and alcohol inputs.
- Prepare future account sync, export, deletion, notification, and billing flows.
- Respond to support requests when a public support path exists.
4. Sharing and selling
The local MVP does not send the user's quit profile to a server. Future hosted versions should not sell personal or sensitive user data. Any future sharing must be limited to service providers needed to run the app, legal requirements, user-directed export, account support, and billing processors.
Future third-party services must be listed before launch, including hosting, authentication, push notifications, billing, analytics, customer support, crash reporting, and any map provider.
5. Security
The local MVP uses browser storage on this device. Future cloud versions must use HTTPS, user-owned rows, Row Level Security, least-privilege keys, and no server-only credentials in browser code.
6. Retention and deletion
Users must be able to export their data and request account deletion before public account launch. The final hosted version must define retention periods for local cache, account records, support requests, notification records, billing records, and backups.
Delete account controls must stay disabled until hosted accounts, identity verification, billing review, and final confirmation exist.
Current deletion controls are drafts. They do not delete a hosted account because hosted accounts are not connected yet.
7. User choices
- Use the local demo without creating a cloud account.
- Copy a local profile snapshot for internal QA.
- Review the data rights center before account attach.
- Turn notification nudges off when notification systems exist.
- Request export or deletion once hosted accounts are live.
8. Children and age rating
QuitMap should not target children. Age rating, tobacco references, medical safety wording, and regional restrictions must be reviewed before public launch.
9. App-store requirements to finish
- Apple: provide a public privacy policy URL in App Store Connect.
- Apple: complete app privacy answers accurately for all collected data and partners.
- Google Play: provide a public privacy policy URL in Play Console and inside the app.
- Google Play: complete the Data safety form and account-deletion answers if accounts are enabled.
- Both stores: publish a support URL and make deletion/export paths clear before submission.
10. Contact and support
Public support contact is not active yet. The future public page should include a support email, data request instructions, official quit-support resources by country, and response expectations.
Draft support page: Open QuitMap Support Draft.