Sleep Mode privacy

effective august 24, 2026

Sleep Mode is designed to keep calendar decisions and alarm scheduling on your iPhone. We do not sell personal data, show ads, or track you across apps or websites.

data processed on your device

With your permission, the app reads calendar events to identify qualifying calls and schedule alarms. Settings, alarm state, and a 14-day activity history are stored locally. Calendar titles, notes, locations, and full event contents are not uploaded to the Sleep Mode relay.

optional connected services

If you connect one or more Google Calendar or Outlook Calendar accounts, the relay processes only what is required for realtime calendar-change notifications:

• a random app-installation identifier;
• provider account identifiers and email address;
• OAuth and APNs device tokens, encrypted at rest;
• webhook identifiers, processing status, and short action receipts.

Google Calendar and Microsoft Graph notifications contain no event contents; they tell the app to refresh the iPhone calendar. Slack and Gmail integrations are deferred and are not available in public v1.

retention

Connection credentials remain until the connection is removed or deletion is requested. Temporary watch data expires after the meeting window. Webhook idempotency records are retained for up to seven days, relay receipt metadata for up to 30 days, and local activity entries for 14 days.

service providers

The optional relay uses Vercel for hosting and Supabase for encrypted database storage. Apple, Google, and Microsoft process data under their own privacy policies when you use their platforms. We do not give these providers data for advertising.

your choices

All connected services are optional. You can revoke Sleep Mode from Google or Microsoft account-security settings at any time. To request deletion of relay data for an installation, email contact@sleepmodeapp.com. We will verify the request and delete the associated connection, watch, device-token, and receipt records.

security and changes

We use scoped access, encrypted credentials, authenticated webhooks, row-level database controls, and short retention windows. No system can guarantee absolute security. Material policy changes will be reflected by updating the effective date here.