Last updated:
Language: English is the authoritative version. A Czech translation is provided in Zásady ochrany osobních údajů; in case of any discrepancy, this English version prevails.
This Privacy Policy explains how Methos processes your personal data when you use the Methos service. It is written for the live service (account + data vault + MCP server), not the pre-launch waitlist.
The controller responsible for your personal data is:
Methos is the controller of the data you store: you are the data subject, and you use Methos to store, organise, and retrieve your own data. Methos does not act as a processor for third-party controllers in respect of your personal use of the service.
We have not appointed a Data Protection Officer, as we are not required to under Article 37 GDPR. Data protection matters can be raised at [email protected].
| Category | Examples | Sensitivity |
|---|---|---|
| Health and biometric data you upload | Blood test results, DNA exports, HRV, sleep, heart rate | Special category (GDPR Art. 9) |
| Wearable and integration data | Steps, sleep stages, heart rate (Apple Health, Oura, Whoop, Garmin) | Special category |
| User-authored content | Notes, goals, supplement logs, plans | Standard personal data |
| Identity and authentication data | Email address, passkey credentials, an anonymised internal user ID | Standard personal data |
| Technical metadata | Access logs, consent records, processing-activity logs, request metadata | Standard personal data |
| Billing data (only if you buy a paid feature) | Name, email, payment/tax information — handled by our payment provider | Standard personal data |
We process only data you upload or authorise us to import. We do not perform cross-user profiling using your health data.
You can withdraw consent, and reject or terminate the contract, at any time by closing your account, which deletes all of your data (see §9). Withdrawal of consent to the processing of personal data does not affect processing that took place before withdrawal.
We process your data solely to:
Your data is not used for marketing, advertising, profiling, or automated decision-making with legal or similarly significant effect. We do not sell, rent, or trade your personal data.
Known limitation (transparency). During the current self-hosted phase, infrastructure is located at our premises in Brno and access to it is held by a single founding member. This is a documented, accepted early-phase risk; mitigation (multi-person access control, redundancy) is planned before the stable release. See Open Transparency.
AI is used in the ingestion pipeline only for technical functions, none of which interpret your health data or make decisions:
AI is never used to interpret health values, give recommendations, or make automated health decisions. The MCP interface returns stored records, not AI-generated answers. All AI inference runs through Microsoft Azure AI Foundry in EU regions (see §8–9).
All user data is currently stored and processed on infrastructure physically located in Brno, Czech Republic (EU). AI model inference runs through Azure AI Foundry in EU Azure regions (Sweden), so inference stays within the EU and does not constitute a transfer outside the EU in the normal course of operations, additionally covered by Microsoft's Data Processing Agreement incorporating EU Standard Contractual Clauses.
We do not share personal data with third parties for commercial or analytical purposes. The following processors may receive data under a Data Processing Agreement:
| Sub-processor | Role | Data received | Safeguard |
|---|---|---|---|
| Microsoft Azure AI Foundry | AI inference (categorisation, normalisation/anonymisation, embedding, and non-health uses) | Document content during ingestion; only normalised, de-identified text for embedding; short strings for ancillary uses | Microsoft DPA (no training on customer data); EU regions only |
| Paddle (only if paid features are introduced) | Payment processing and billing (Merchant of Record) | Billing details only (name, email, payment/tax info). No health, biometric, or vault data. | Paddle DPA; Merchant-of-Record model keeps card data out of Methos |
| SparkPost | Transactional email delivery (login magic links, service notifications) | Email address, email content, and delivery metadata only. No health, biometric, or vault data. | SparkPost DPA; EU sending region only |
Note on paid features. If paid features are introduced, the handling of stored data on cancellation of a paid feature alone (as distinct from closing the account) will be stated here. Closing your account always deletes your data, and your GDPR rights to export and erasure apply regardless of any paid status.
You have the right to:
| Right | Article | Status |
|---|---|---|
| Access to your data | Art. 15 | Implemented (access is logged) |
| Rectification | Art. 16 | Planned |
| Erasure ("right to be forgotten") | Art. 17 | Implemented (account closure deletes all your data) |
| Data portability (export) | Art. 20 | Planned for MVP |
| Withdraw consent | Art. 7(3) | Implemented (closing your account withdraws consent and deletes your data) |
| Restriction of processing | Art. 18 | Planned |
| Object to processing | Art. 21 | Applicable |
Where a right is exercised through the service's own functionality, please use that path first. You also have the right to lodge a complaint with a supervisory authority — in the Czech Republic, the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, ÚOOÚ), www.uoou.cz.
To exercise any right, contact [email protected].
Methos is a data storage and retrieval infrastructure with no medical purpose. It is not a medical device under EU/US medical software regulations, and the AI functions are assessed as minimal-risk under the EU AI Act. GDPR is the primary regulation that applies.
We may update this Policy. Material changes will be notified in advance through the service or by email. The "Last updated" date reflects the current version.
Privacy matters: [email protected].