Privacy & Data
Your data is yours. Here's exactly what we collect, how we store it, and how to control it.
Our Philosophy
Dayze is a deeply personal app. We believe your life data belongs to you. We don't sell your data, we don't show ads, and we don't share your information with third parties for marketing purposes.
What We Store
Profile
Name, email, birthday, handle, profile photo, timezone, and preferences.
Events
Events you create or import from calendar. Title, date, time, location, linked people, and optional photos.
People
People you add — name, birthday, relationship type, interaction history, and notes.
Expenses
Transactions you log — amount, category, description, date, and any splits.
Day Scores
Your daily 1-10 ratings for each day.
Dayze Agent memory
Facts the assistant has learned about you. Fully editable and deletable.
Chat History
Your conversations with Dayze Agent.
Quiz Responses
Your answers to Pulse questions and quizzes (anonymized for community stats).
Photos you upload
Meal photos (Food Diary) and calendar event photos you attach in Dayze are stored in our encrypted Supabase storage. Event photos use a private bucket — the app shows them via short-lived signed links while you are signed in, not permanent public URLs. Camera-roll hero images on Day Cards (Journaling Suggestions) are different: only metadata is stored; files stay on your device (see below).
What We Don't Store
- Day Card camera roll — Photos from Journaling Suggestions are fetched from your device. Only metadata (URL, caption) is stored. The actual image files remain on your device.
- Health data raw values — Health metrics are fetched from Apple Health on-device and displayed locally. Only aggregated summaries may be stored server-side for Day Card rendering.
- Passwords — We use Supabase Auth. Passwords are hashed and never stored in plaintext.
- Contacts raw data — Phone contacts are read locally. Only people you explicitly add are stored.
Where Data is Stored
Dayze uses Supabase (hosted on AWS) for database and authentication. All data is encrypted at rest and in transit (TLS 1.2+). Database backups are maintained by Supabase with point-in-time recovery.
Data Export
Dayze Pro and Family subscribers (and active Pro trials) can export their complete life graph at any time from Settings. Free accounts can delete their account and data anytime.
The JSON download uses dayze.life-graph format version 3.0. Its top-level manifest lists every collection, whether it is a node, edge, fact, provenance record or profile, and its row count. The lossless collections object contains the original private rows, including people, events, moments, places, trips, expenses, memories, learned facts, source/provenance envelopes, and the joins between them. If a collection isn't available yet, the file says so: it sets complete to false and names the collection in unavailable. Any other read error fails the export rather than producing an unlabeled partial file.
Account Deletion
You can delete your account and all associated data at any time from Settings. After you confirm, we target removing personal data from production systems within 30 days, subject to legal retention, billing and tax records, dispute and security needs, and infrastructure backups (including Supabase point-in-time recovery), as described in Privacy Policy §9 (Retention). End-to-end purge timing is policy, not a separately attested audit. We will:
- Delete all your profile data, events, people, expenses, and scores
- Delete all assistant memory and chat history
- Delete all quiz responses and DayzeCoin balance
- Remove any public profile page
- Cancel any active subscription
Community Data
When you answer Pulse questions or complete quizzes, your responses are anonymized and aggregated to show community statistics (e.g., "68% of users chose option A"). Individual responses are never publicly visible.
Third-Party Services
Same high-level categories as Trust & Security:
- Database, auth, storage — Supabase (AWS-hosted)
- Hosting / CDN — Netlify (and related edge delivery)
- Payments (web) — Stripe (card data stays with Stripe)
- Payments (apps) — Apple App Store and Google Play in-app purchases when you subscribe on a device
- AI model APIs — one or more third-party model providers for Dayze Agent chat/voice (providers may change; we do not brand a single vendor in product UI). We do not allow your Dayze data to train their models.
- Product analytics — Google Analytics and PostHog, for usage counts and app errors only (no message, email, or note content)
- Email / messaging delivery — transactional providers for auth links and notifications
- Integrations you connect — Google, Apple, Spotify, etc., under the scopes you authorize