Privacy Policy
Effective September 1, 2026. MorningKeep is provided by Mabry Ventures LLC.
1. What MorningKeep handles
Sparks may include text, voice recordings and transcripts, images, drawings, links, and metadata you choose to capture. MorningKeep also handles product settings, permission state, purchase entitlement, bounded usage state, and diagnostic events needed to operate the app.
2. Where your content lives
On Apple devices, primary Spark storage is on your device and, when iCloud is enabled, in your private CloudKit database. Apple Watch recordings remain on the Watch while delivery is pending and are removed from its queue only after the paired iPhone confirms a durable save. On Android, primary Spark storage is a local Room database on your device; MorningKeep does not sync Android Spark content to iCloud and does not store Android Spark content on its servers. Wear OS recordings remain on the watch while delivery is pending and their raw-audio queue entry is removed only after the paired Android phone confirms a durable save.
3. Cue and cloud processing
Eligible bounded work uses Apple Foundation Models on device first. After explicit cloud consent, selected structured workloads may send the minimum required text and source context through MorningKeep’s authenticated Cloud Run service to Google Vertex AI. The client cannot choose the provider or model. MorningKeep does not send raw audio to its cloud AI service and has no OpenAI runtime or secondary provider fallback.
4. Actions and platform permissions
Cue output is a proposal, not an instruction. MorningKeep creates an Apple Reminder or Apple Calendar event only after you approve the outcome and grant the applicable permission. On Android, an approved outcome writes to the system Calendar provider or your chosen reminder destination under the same approval and permission rules. Contact recognition is optional and performed locally.
5. Accounts, purchases, and operations
Firebase App Check and Firebase Authentication protect cloud routes on every platform; Android devices attest through Play Integrity. StoreKit transaction evidence on Apple devices and Google Play Billing purchase evidence on Android are verified to maintain Dawn entitlement and prevent abuse. Operational telemetry is structured and excludes Spark text, transcripts, attachment contents, reusable credentials, and receipt bodies. MorningKeep does not sell your personal data or use your Sparks for advertising.
6. Export, deletion, and retention
You can export your data or request deletion from MorningKeep Settings. If you have an active Dawn subscription, MorningKeep makes no local or cloud deletion until you link Sign in with Apple and the current verified StoreKit transaction records the recovery proof needed to restore your entitlement later. MorningKeep tells you when that preparation is required. After the safety check passes, local deletion begins and CloudKit and account deletion remain pending until remote completion is confirmed. If a remote step fails, MorningKeep retains the minimum recovery credential and deletion checkpoint so you can retry. This preparation applies to Apple accounts, which are the accounts that hold synced CloudKit records and StoreKit entitlement recovery proof. On Android, Spark content lives only in the local Room database on your device, so removing the app’s data or uninstalling MorningKeep removes it and MorningKeep holds no Android Spark content to delete. Server request receipts and hashed entitlement records are retained only as needed for security, billing continuity, fraud prevention, and legal obligations.
7. Your choices
You can decline microphone, speech, reminders, calendar, contacts, analytics, and cloud AI permissions. Some related features will be unavailable, but local capture remains the core path. You can manage Dawn through Apple Subscriptions on Apple devices or through Google Play subscriptions on Android.
8. Contact and changes
For privacy questions or requests, email support@morningkeep.com. Material policy changes will be reflected here and, when appropriate, communicated in the app.