Privacy Policy

1. Information We Collect

2. How We Use Your Information

3. Data Encryption

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.

5. AI Models & Where Your Data Is Processed

MULIO’s AI features — the Sunday Weekly Report, the seven-day This Week playbook, and Ask MULIO consultation 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 week’s journal text (decrypted server-side immediately before the call), your profile fields you entered during onboarding (role, industry, goals, language preference), and any context that the report or question explicitly requires (e.g. last week’s diagnosis summary).
• Not sent: your name, your email address, your Apple ID, your Firebase user ID, your subscription billing information, your HealthKit data, 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 encrypted at rest in our database (via Evervault). It is decrypted only on our backend, only at the moment of an AI call, and only inside a single function invocation that does not persist plaintext.

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, ADHD-shaped protocols, 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 daily journal feature free and the subscription priced at $14.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.

Anthropic SDK, not Anthropic the company

A technical note for the curious: MULIO’s backend uses an open-source SDK published by Anthropic to communicate with DeepSeek’s API, because DeepSeek’s API speaks the same wire format. Anthropic the company is not in our data path. Your journal text never touches Anthropic’s servers. The SDK is a translation layer, no different from any other HTTP client.

6. Data Retention

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 → Account → Delete Account).
• Portability of your data in machine-readable format (JSON export).
• Restrictionof processing — contact support@mulio.ai.
• Objectto processing — contact support@mulio.ai.
• 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)

9. Security

• End-to-end encryption via Evervault for journal entries.
• 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 that leaves the U.S. is the AI call to DeepSeek (mainland China), described in §5.

10. Changes to This Policy

11. Contact