Memorion Privacy Policy

• Email Address — used to create and authenticate your account, send important account-related notifications, and respond to support requests.
• User ID — a unique identifier we generate to associate your data (memories, settings, preferences) with your account. We may also receive a unique identifier from your sign-in provider (Apple ID, Google ID) when you choose Sign in with Apple or Sign in with Google.

• Audio recordings captured through the Memorion wearable device or your phone's microphone, when you actively initiate a recording.
• Transcriptions generated from your audio, including AI-generated summaries, action items, and structured memories.

To produce transcriptions, your audio is sent to one of the third-party speech-to-text providers listed in Section 5.3 (Deepgram or Soniox). To produce AI-generated summaries, action items, structured memories, and chat responses, the resulting transcribed text is sent to one of the third-party AI providers listed in Section 5.4 (OpenAI, Anthropic, or Google Gemini). Each of these providers is contractually prohibited from retaining your data after processing or using it to train their AI models.

By default, audio recordings, transcriptions, and memories are stored locally on your device. If you enable cloud sync, this data is encrypted and stored in our cloud infrastructure (see Section 5.2) to support cross-device access.

• Crash Data — automated reports generated when the app crashes, including stack traces and device state at the time of the crash. This data does not include the content of your conversations.
• Performance Data — aggregated, anonymous metrics such as app launch time, response latency, and feature usage patterns. This helps us improve stability and performance.

This data is collected anonymously and is not linked to the content of your memories.

By default, your audio recordings, transcriptions, and memories are stored locally on your device. You can use the core features of Memorion without uploading any conversation data to our servers.

If you choose to enable cloud sync, your data is encrypted before it leaves your device and stored in our cloud infrastructure. We use industry-standard encryption in transit (TLS) and at rest.

We implement appropriate technical and organizational measures to protect your data against unauthorized access, loss, or disclosure. However, no method of electronic storage is 100% secure. We encourage you to use a strong password and enable two-factor authentication on your sign-in provider account.

• Apple (Sign in with Apple) — receives your email (or relay address) and Apple-issued user identifier.
• Google (Sign in with Google) — receives your email and Google-issued user identifier.

• Google Firebase / Firestore (Google LLC) — stores your account profile, conversations, memories, and settings.
• Google Cloud Storage (Google LLC) — stores your audio files and uploaded media in encrypted form.
• Modal (Modal Labs, Inc.) — hosts our backend compute layer.
• Upstash Redis (Upstash, Inc.) — caches session data and ephemeral state.
• Pinecone (Pinecone Systems, Inc.) — stores vector embeddings of your transcriptions to power semantic search.
• Typesense (Typesense, Inc.) — indexes your memories' text to power keyword search.

The Memorion app sends your audio recordings to one of the following STT providers for transcription. Audio sent to these providers is not retained by them after processing and is not used to train their models:

• Deepgram (Deepgram, Inc.) — primary real-time transcription provider.
• Soniox (Soniox, Inc.) — multilingual transcription provider.

The specific provider used depends on the language of your recording and our server-side configuration.

After transcription, your transcribed text may be sent to one of the following LLM providers to generate summaries, structured memories, action items, and chat responses. Data sent to these providers is not used by them to train their models:

• OpenAI (OpenAI, L.L.C.) — accessed via OpenRouter (OpenRouter, Inc.); used for summarization, memory extraction, and embeddings.
• Anthropic (Anthropic, PBC) — accessed via Amazon Web Services Bedrock (Amazon Web Services, Inc.); used for summarization, memory generation, and chat.
• Google Gemini (Google LLC) — accessed via Google Cloud Vertex AI; used for summarization, memory extraction, and image generation for daily reports.

• Firebase Crashlytics (Google LLC) — collects anonymous crash reports.
• Firebase Performance Monitoring (Google LLC) — collects anonymous performance metrics.

We do not sell, rent, or share your personal data with third parties for their own marketing or commercial purposes. None of the providers above are authorized to use your data to train their AI models, build advertising profiles, or pursue any independent commercial use.