Skip to content

Privacy Policy

Last updated: July 29, 2026

1. Information We Collect

Journal entries. Your journal text is stored in our database (Google Cloud Firestore) under Google Cloud’s encryption at rest, and is read by our backend only to generate your guidance — your Game Plan, your Weekly Report, and your Ask MULIO answers.

Health data. With your explicit permission, MULIO reads Apple HealthKit fields (sleep, steps, HRV) on your device and converts them to coarse low/medium/high signals. This data is never sold and never used for advertising, and your raw HealthKit readings never leave your device.

Account information. Your Apple ID email and display name when you sign in with Apple, plus a Firebase user ID issued at first launch.

Profile fields. Onboarding fields you enter (role, industry, goals, language preference, declared dietary preferences and supplement stack). These are sent to DeepSeek alongside the relevant week’s journal text when generating reports or answering Ask MULIO questions.

Usage analytics. Anonymous, aggregate usage patterns to improve the app. No journal content is included in analytics.

2. How We Use Your Information

Generate your Weekly Reports, your daily Game Plan, and your Ask MULIO responses, via the DeepSeek V4 Pro language model (see §5).

Build cross-week semantic memory (via Mem0, with nightly consolidation performed by Anthropic’s Claude model) so reports can reference longer-term patterns. Mem0 receives insights extracted by AI — never raw journal text.

Run web searches (via Serper, a Google Search API) and medical-literature searches (via NCBI PubMed) for research-backed citations in reports and answers. These services receive search queries derived from report themes and your questions, never raw journal text.

Generate the artwork attached to your Weekly Report (via OpenAI’s image model, which receives an AI-written artwork prompt derived from your report, never your journal text).

Send push notifications for report and Game Plan delivery (via Firebase Cloud Messaging).

Manage your subscription (via Apple StoreKit; no card data ever touches our servers).

3. Data Encryption

All stored data is encrypted at rest on Google Cloud infrastructure. Your most sensitive profile fields (such as dietary preferences and supplement stack) are additionally field-level encrypted using Evervault before they reach our database. Journal text is not field-level encrypted — our backend must read it to generate your guidance — and it is processed only for that purpose.

All data in transit uses TLS 1.2 or higher. Firebase App Check is enabled to prevent unauthorized API access.

4. Third-Party Service Providers

MULIO uses the following third-party services to operate. Each service receives only the minimum data necessary to perform its function.

ProviderPurposeData sharedPrivacy policy
DeepSeek
Hangzhou DeepSeek Artificial Intelligence Co., Ltd.
Generates Weekly Reports, daily Game Plans, and Ask MULIO responses.Journal text for the period being analyzed; your profile (goals, role, industry, language preference); your recent plans and progress; prior report summaries; and your question text for Ask MULIO.cdn.deepseek.com…
Firebase / Google CloudAuthentication, database, file storage, push notifications, cloud functions.Firebase UID, journal entries (under Google Cloud encryption at rest), reports, subscription status, FCM tokens.firebase.google.com…
EvervaultField-level encryption of sensitive profile fields.Encrypted ciphertext of the protected fields.evervault.com/privacy
AnthropicNightly consolidation of each day into long-term memory notes (Claude model).The day’s activity being consolidated, keyed by Firebase UID.anthropic.com…
OpenAIGenerates the artwork attached to Weekly Reports.An AI-written artwork prompt derived from your report (no raw journal text).openai.com…
Serper & NCBI PubMedWeb search and medical-literature search for research-backed citations.Search queries derived from report themes and your questions (no raw journal text).serper.dev/privacy
Mem0Semantic memory for personalized long-term context.Anonymized insights extracted by AI (no raw journal text), keyed by Firebase UID.mem0.ai/privacy
AppleSign in with Apple, StoreKit subscriptions, HealthKit.Apple ID (hashed), subscription transactions, health data (sleep, steps, HRV).apple.com/privacy

5. AI Models & Where Your Data Is Processed

MULIO’s core AI features — the Sunday Weekly Report, the daily Game Plan, and Ask MULIO responses — are produced by an AI language model called DeepSeek V4 Pro, operated by Hangzhou DeepSeek Artificial Intelligence Co., Ltd. (“DeepSeek”). This section explains what that means for your data.

Where the model runs

DeepSeek is a Chinese AI company. The DeepSeek V4 Pro model runs on servers located in mainland China. DeepSeek’s published privacy policy states they “directly collect, process and store your Personal Data in People’s Republic of China.” When MULIO generates a report or answers an Ask MULIO question, the relevant inputs are sent from our backend (Google Cloud, in the United States) to DeepSeek’s API, which routes the request to a model running on Chinese infrastructure.

What is sent to DeepSeek, and what is not

  • Sent:the relevant journal text, your profile fields (role, industry, goals, language preference), your goals, recent plans and progress, and any context that the report, plan, or question explicitly requires (e.g. last week’s report summary).
  • Not sent: your name, your email address, your Apple ID, your Firebase user ID, your subscription billing information, your raw HealthKit readings, your IP address, or any field MULIO does not explicitly include in the prompt. We send what the model needs to do its job and nothing else.

Your journal text is stored under Google Cloud’s encryption at rest and read by our backend only when generating your guidance. It is never used for advertising and never sold.

Jurisdictional implications

Data processed by DeepSeek is subject to applicable laws of the People’s Republic of China, which include the Cybersecurity Law (2017), the Data Security Law (2021), and the Personal Information Protection Law (2021). Under these laws, Chinese authorities may, in certain circumstances, request access to data processed within China. We are not in a position to limit such requests beyond DeepSeek’s published privacy commitments. If you are uncomfortable with this, please do not use MULIO, and existing users may delete their account at any time via Settings → Data & Privacy → Delete Account.

Why we made this choice

We chose DeepSeek V4 Pro for two reasons: (1) the model produces substantially more useful coaching responses for our domain (longitudinal behavioral analysis and evidence synthesis) than the alternatives we evaluated, at our quality bar; and (2) the cost is roughly 1/20th of equivalent-quality U.S.-hosted models, which lets us keep the subscription priced at $9.99/month rather than $40+. We considered the privacy trade-off and decided to disclose it transparently rather than hide it.

How DeepSeek handles your data

DeepSeek’s published privacy policy is the source of truth for retention, model training, and your rights as a user. Please read it directly at cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html. Two points worth pulling out, accurate at the time of writing:

  • Retention. DeepSeek’s policy states they “retain Personal Data for as long as necessary to provide our Services” and that account-tied data is kept “for as long as you have an account.” DeepSeek does not publish a specific retention duration in days for API request data. Deleting your MULIO account does not, by itself, delete prior request data already on DeepSeek’s servers — but it does ensure no further requests are made on your behalf.
  • Model training. DeepSeek’s policy describes using collected data “to improve and develop the Services and to train and improve our technology, such as our machine learning models and algorithms.” DeepSeek offers a user-level opt-out from training. Whether MULIO’s specific API calls are subject to training depends on DeepSeek’s API contract terms; if you have a strong preference, the safest path is account deletion.

If DeepSeek changes its data-handling commitments in a way that materially affects MULIO’s data flow, we will update this section and notify subscribers via the in-app changelog.

Where Anthropic fits

MULIO’s backend uses Anthropic’s Claude model for one narrow job: a nightly step that distills each day’s activity into the long-term memory notes described in §2. Anthropic is not involved in generating your reports, plans, or Ask MULIO answers — those run on DeepSeek as described above. Anthropic’s processing happens on U.S. infrastructure under the privacy policy linked in §4.

6. Data Retention

Data typeRetention periodNotes
Journal entriesUntil account deletionStored in Firestore under Google Cloud encryption at rest.
Weekly Reports & Game PlansUntil account deletionGenerated by the AI pipeline, stored in Firestore.
Health snapshotsUntil account deletionAggregated weekly from HealthKit.
Mem0 memoriesUntil account deletionDeleted via Mem0 API on account deletion.
Data export files24 hoursAuto-deleted from Firebase Storage.
Anti-abuse identifierIndefiniteA non-reversible SHA-256 hash of your Apple ID is retained after account deletion to prevent abuse of free allowances (such as the free trial and the pre-subscription question allowance). This hash cannot be used to identify you.

7. GDPR Rights

If you are located in the European Economic Area (EEA), you have the right to:

  • Accessyour personal data (Settings → Privacy → Export Data).
  • Erasureof your personal data (Settings → Data & Privacy → Delete Account).
  • Portability of your data in machine-readable format (JSON export).
  • Restrictionof processing — contact hello@exitroom101.com.
  • Objectto processing — contact hello@exitroom101.com.
  • Lodge a complaint with your local data protection authority.

Data export is available once every 24 hours. Account deletion removes all data from our systems within 30 days, with the exception of the anti-abuse identifier described in §6.

8. Children’s Privacy (COPPA)

MULIO is not intended for children under 13. We do not knowingly collect personal information from children under 13. An age verification gate is presented on first use.

9. Security

  • Encryption at rest (Google Cloud) for all stored data, plus field-level Evervault encryption for sensitive profile fields.
  • Firebase App Check to prevent unauthorized API access.
  • Sign in with Apple for secure, private authentication.
  • TLS 1.2+ for all data in transit.
  • All MULIO infrastructure is hosted in the United States (Google Cloud, Firebase). The only data flow we intentionally route outside the U.S. is the AI call to DeepSeek (mainland China), described in §5.

10. Changes to This Policy

We may update this policy from time to time. Material changes will be communicated through the in-app changelog and via email to subscribers. The “Last updated” date at the top of this page reflects the most recent revision.

11. Contact

For privacy inquiries (access, deletion, restriction, objection, portability), contact hello@exitroom101.com. For general support, contact hello@exitroom101.com.

MULIO is published by Exitroom101 LLC, United States.