MorningKeep

Privacy

MorningKeep Privacy Policy

MorningKeep is a daily ritual for your own thinking: capture Sparks, reflect with Cue, and begin each morning with a clear brief. Privacy is foundational to that experience. Your Sparks belong to you.

Last updated: July 17, 2026

1. Introduction

This policy explains what data MorningKeep handles, how it is used, and what controls you have. We designed MorningKeep around local-first and CloudKit-first storage so your information stays in your Apple ecosystem.

2. What We Collect

  • Sparks and content: Stored on-device and in your iCloud via CloudKit. Your Sparks stay in the local/iCloud path unless you explicitly enable Cue processing.
  • Voice and microphone: With your permission, MorningKeep can capture voice Sparks using your device microphone. Voice recordings are stored locally while capture and transfer are in progress. Apple Speech may process audio when on-device recognition is unavailable or not enforced. Transcripts and Spark text can be processed through Cue after AI consent is enabled. MorningKeep does not upload raw voice recordings to its Cue workers.
  • Email address: Optionally provided during onboarding, purchase, or support. Used for account support, lifecycle messages, and product updates when you opt in. You may skip this entirely.
  • Contacts: Optional and local-only. If you enable Contact Recognition, MorningKeep reads Contacts on device to match names you mention. Contact names, phone numbers, and emails are not sent to Cue providers.
  • Usage analytics: Anonymized product telemetry through TelemetryDeck. No personal identifiers are included.
  • Account information: Apple Sign In only. We receive a stable Apple identifier, not your email unless you explicitly share it.

3. How We Use Your Data

We use your data to generate your Morning Briefs, answer Cue requests, detect patterns in your thinking, and identify your optimal creative conditions. The product is designed to operate local-first with CloudKit synchronization, rather than central server-side profiles.

Apple Calendar and Reminder items are created only when you grant the relevant permission and enable the matching setting. Apple Notes export is manual through the system share sheet. Journal Suggestions receive content-free capture context, not raw Spark text.

4. How We Use AI

MorningKeep uses Cue services to process your Sparks and generate insights, briefs, and Cue responses. Bounded Cue tasks can run with Apple Foundation Models on supported devices. Tasks that require cloud processing use the following providers after you enable AI processing:

  • Apple Foundation Models and speech services (device-first): Handles eligible bounded Cue work, transcription, and voice playback using Apple platform capabilities. Apple service behavior depends on device support, downloaded assets, language, and system settings.
  • Google Gemini API (cloud route): Processes content for cloud-backed insights, Morning Briefs, and eligible Cue requests. Provider data use follows the Gemini API terms and the account configuration used by MorningKeep.
  • OpenAI API (fallback): Used only when Gemini is unavailable. Same data handling principles apply. Provider data use follows OpenAI's API terms and MorningKeep's account configuration.

Cloud AI requests are routed through MorningKeep's proxy infrastructure over TLS. Firebase App Check is the required production device-authentication control; this pre-release policy does not claim that control is verified until the current Release/TestFlight authentication drill passes. MorningKeep does not operate a central Spark-content database. Offline caching of AI results is stored locally on your device.

5. What We Don't Do

  • We do not sell your data.
  • We do not sell your Sparks or share them for advertising.
  • We do not operate a centralized database of your Sparks.
  • We do not use your data for advertising.
  • We do not use your Sparks to train MorningKeep-owned models.

6. Data Storage & Security

Primary storage lives on your device and in your iCloud through CloudKit. MorningKeep does not operate centralized databases of your Sparks.

CloudKit uses Apple-managed encryption and private-database access control. MorningKeep Release does not claim full application-layer end-to-end encryption for synced CloudKit content.

Security measures include: biometric authentication (Face ID / Touch ID) with immediate lock on background, Keychain storage for sensitive data, and TLS for network traffic. Firebase App Check is the required production API-request verification control and must pass signed Release/TestFlight validation before launch.

7. Data Deletion

You can delete your account and associated data from Settings > Privacy > Delete My Data. MorningKeep deletes local data immediately and requests removal of synced CloudKit records. CloudKit deletion syncs asynchronously through Apple infrastructure, so exact server-side timing can vary. Locally cached Cue responses are deleted with local app data.

8. Contact

For privacy questions, email support@morningkeep.com.