DrowZe — Privacy Policy

1. Who we are

DrowZe is operated by Trevix Labs, a sole proprietorship business in Canada.

Contact:

• Email: support@drowze.ca
• Website: https://drowze.ca

For European users, Trevix Labs acts as the data controller under GDPR.

2. How DrowZe stores your data

DrowZe is offline-first. There is no sign-up, no email, and no password. Your shift schedule, sleep logs, preferences, and AI plan history are stored in a local database on your device only. We do not hold a copy on our servers, and we cannot see this data unless you choose to send it to an optional AI feature (Section 3) or attach it to a support email.

Because everything lives on your device, reinstalling the app or switching devices does not carry your data over automatically. You can create a manual backup file and restore it yourself — see Section 4.

3. AI features (optional, DrowZe Pro)

AI features require DrowZe Pro and are off by default. You turn them on in Profile → AI features, and can turn them off at any time. With AI off, your sleep plan is built entirely on your device by DrowZe's built-in recovery engine, and nothing described in this section applies.

3.1 Who receives it

When AI features are on, requests go through DrowZe's servers (Supabase Edge Functions) to OpenAI, our AI provider. Under OpenAI's API data policy, your data is not used to train their models.

3.2 What's shared

• AI sleep plans: your chronotype, target sleep hours, commute time, upcoming shift times, recent sleep sessions (including sleep imported from Apple Health or Health Connect, and notes you wrote), sleep debt, and recovery score.
• Schedule scan: the roster photo or file you choose to scan and any instructions you type alongside it.

3.3 What's never shared

Your name, email, or payment details are never sent to OpenAI — we don't collect them in the first place. Your data is never sold or used for advertising.

3.4 What AI never decides

AI only chooses between sleep options DrowZe's recovery engine has already safety-checked. It never rates your fatigue risk, judges whether you are safe to drive or work, or gives medical advice.

3.5 Fair-use quota (anonymous)

To stop abuse of our AI budget, each request carries an anonymous device identifier (a random ID generated on your device, not tied to your name or email) and, if you are a Pro subscriber, your RevenueCat subscriber ID. We use these to count how many AI plans or scans a device has used in a day or week against your plan's limit. This usage count is kept only for as long as needed to enforce that limit and is never linked to your identity.

4. Manual backup and restore (optional)

Profile → Data → Export backup lets you save a copy of your local database as a file. DrowZe hands that file to your device's native share sheet — where it goes from there (AirDrop, Files, email, cloud storage) is entirely your choice. We never receive a copy of your backup file, and restoring one only reads it back into DrowZe's local database on your device.

5. Health data (optional — Apple Health on iOS, Health Connect on Android)

• What: Sleep data synced from Apple Health or Health Connect: sleep start time, end time, duration, source app.
• Why: To supplement manually logged sessions with data from your Apple Watch, Oura Ring, or other health devices, giving a more complete sleep debt picture.
• How we access it: We only read sleep data. We never write to Apple Health or Health Connect. Imported sleep sessions are stored in your local database like any other sleep log — they only leave your device if you turn on AI features (Section 3) or send a backup file yourself (Section 4). We never share health data with advertisers.
• Your control: Revoke access at any time in iOS Settings → Privacy & Security → Health → DrowZe, or in Android Settings → Health Connect → App permissions.
• Legal basis (GDPR): Explicit consent — you must actively enable this in the app.

6. Calendar sync (optional)

If you turn on calendar sync in Profile, DrowZe writes your scheduled shifts and sleep blocks to your device's own calendar (Apple Calendar or your Android calendar app) using the operating system's calendar API. This happens entirely on your device — the events never pass through our servers. You can revoke calendar access at any time in your device's Settings.

7. Subscription status

• What: Whether you have an active DrowZe Pro subscription, plan type (monthly/annual), product identifier, and expiry date.
• Who holds it: RevenueCat manages this on our behalf, identified by a RevenueCat subscriber ID that is either generated anonymously on your device or, for accounts created before DrowZe went offline-first, a legacy identifier we kept solely to preserve an existing subscription. Neither is linked to a name or email.
• Note: We never receive your payment card details. All payment processing is handled by Apple or Google. RevenueCat only provides us with entitlement status.

8. App events (analytics)

• What: Anonymised events such as which screen opened the paywall, whether onboarding was completed, and which features were used. Emails, names, and raw shift or sleep content are excluded from event data before it is sent.
• Who holds it: PostHog, our analytics provider, processed in the United States.
• Why: To understand how the app is used so we can improve it. We use this internally only — we do not share analytics data with advertising networks.
• Legal basis (GDPR): Legitimate interest (product improvement).
• Retention: 90 days rolling.

9. Device and technical data

• What: Device type, operating system version, app version, and an anonymous device identifier (Section 3.5). IP address is processed transiently by our servers when you use an AI feature but is not stored.
• Why: For debugging, crash reporting, AI fair-use enforcement, and ensuring the app works correctly on your device.
• Legal basis (GDPR): Legitimate interest.
• Retention: 30 days in system logs.

10. Advertising identifiers (free tier only)

• What:On the free tier, Google AdMob shows ads. If you allow tracking, AdMob may use your device's advertising identifier to personalise them. If you don't, DrowZe requests non-personalised ads only.
• Why: To generate revenue that keeps the free tier available.
• Your control: You can limit ad tracking in iOS Settings → Privacy & Security → Tracking. Pro subscribers see no ads and AdMob is not initialised for Pro accounts.
• Legal basis (GDPR):Consent — where required by law, we request your consent through Apple's App Tracking Transparency framework before AdMob accesses the IDFA.

11. Third-party services

The following third-party services may process your data as part of the app's operation. Each has their own privacy policy.

We do not use:

• Google Analytics or Firebase Analytics
• Facebook SDK or Meta Pixel
• Crashlytics, Sentry, or any other crash-reporting SDK
• Any cross-app tracking SDK

12. How we store and protect your data

• Your shift, sleep, and preference data is stored in a local database inside DrowZe's private app storage, protected by your device's built-in storage encryption and passcode.
• The anonymous AI fair-use records described in Section 3.5 are stored on Supabase-hosted PostgreSQL with AES-256 encryption at rest.
• All data in transit uses TLS 1.2 or higher.
• We do not store payment card numbers, CVV codes, or full payment details anywhere in our systems.

13. Your privacy rights (GDPR, UK GDPR, CCPA/CPRA, PIPEDA)

DrowZe has no accounts and collects no names or email addresses. Most of your data never leaves your device, so you can exercise most privacy rights yourself, instantly, in the app:

The small amount of data held on servers (anonymous AI usage counts, anonymised analytics events, and subscription status) is keyed to random identifiers, not to you. We have no way to tell which records are yours, so, as permitted by GDPR Article 11, we cannot act on requests for them unless you give us something that links them to you, such as an App Store or Google Play order ID for a subscription. For anything else, or if you need help, email support@drowze.ca. We respond within 30 days.

Legal bases (EU/UK GDPR)

Withdrawing consent does not affect processing that happened before. You can also complain to your data protection authority (in the UK, the ICO at ico.org.uk).

California (CCPA/CPRA)

• What we collect: identifiers (a random device ID, and your advertising ID if you allow tracking), internet or app activity (anonymised analytics events), and, only if you turn on AI features, sensitive health information (sleep data) sent to generate your plan.
• We do not sell your personal information.
• Sharing for targeted ads:free-tier ads are non-personalised unless you allow tracking. If you allow it, AdMob may use your advertising ID for personalised ads, which California law may treat as "sharing". To opt out, turn off tracking in iOS Settings → Privacy & Security → Tracking, or delete your advertising ID in Android Settings → Privacy → Ads. DrowZe Pro shows no ads.
• Sensitive information: we use health data only to provide the features you ask for, never to infer characteristics about you, so the right to limit its use does not apply.
• You have the right to know, delete, and correct your information, and we will not discriminate against you for using these rights.

Canada (PIPEDA)

You may access and correct your information, and withdraw consent for optional processing (AI, health data, analytics), at any time as described above. Our Privacy Officer can be reached at support@drowze.ca.

14. Data retention summary

15. Children's privacy

DrowZe is not directed at children under 13 (or under 16 in the EU/UK). We do not knowingly collect personal information from children under these ages. If you believe a child has provided us with personal information, contact support@drowze.ca and we will delete it promptly.

16. International data transfers

When you use an optional AI feature, your request is processed by OpenAI and by Supabase (AWS-hosted) in the United States. RevenueCat and PostHog also process data in the United States. Your device-local data is never transferred anywhere unless you choose to send a backup file yourself.

For EU/UK users: These transfers are made under appropriate safeguards including Standard Contractual Clauses (SCCs) approved by the European Commission. You can request copies of the SCCs by emailing support@drowze.ca.

17. Changes to this policy

We will notify you of material changes through an in-app notification and by updating the "Last updated" date above. Continued use of DrowZe after the effective date constitutes acceptance of the revised policy.

18. Contact

Privacy Officer
Trevix Labs
support@drowze.ca
https://drowze.ca/privacy

For GDPR data subject requests: support@drowze.ca with subject line "GDPR Request — [your request type]"