Privacy policy

Nothing non-essential runs before you say yes. No analytics, no marketing, no health data processing.

If you just read the site

If you have an account

If you connect health data

Lab results, device and wearable metrics, and anything you upload. This is the most sensitive thing we hold and it has its own notice: health data and consent.

If you contact a clinic through us

Your name, contact details, the service you asked about and anything you typed in the message. That is passed to the clinic, which becomes responsible for it as its own controller. Enquiry forms warn you not to include medical details, because they are routed to sales inboxes rather than treated as clinical records.

Health data is a special category under Article 9. We process it only on your explicit consent, given per purpose and per recipient, and recorded with a timestamp and the policy version you agreed to. Consent is the basis, so withdrawing it stops the processing. Account and billing data is processed to perform our contract with you; security logging rests on our legitimate interest in keeping the service safe.

Health data for this market is stored in the European Union and is not replicated outside it. Where a sub-processor is outside the EEA, the transfer runs on the European Commission’s standard contractual clauses plus a transfer impact assessment, and we name the sub-processors in the privacy notice.

Account, billing and content data is separate from health data and may be processed in a different region from your health data. The split is deliberate: the health database has a narrower access path and a stricter audit trail than the rest of the platform, and a staff member with full access to the main database still cannot read a lab result.

• Infrastructure and email providers acting on our instructions under a data processing agreement.
• Payment providers, for the transaction only.
• A clinic, when you send it an enquiry or explicitly share health data with it. It becomes a controller of what it receives.
• Law enforcement, where we are legally compelled. We require valid legal process, we push back on overbroad requests, and we tell you unless we are legally forbidden from doing so.
• Nobody else. In particular: no data brokers, no insurers, no employers, and no advertising networks.

• Server logs: 30 days.
• Analytics: aggregated after 14 months, with no individual-level retention beyond that.
• Account data: until you delete your account, then 30 days in backups before it is gone.
• Health data: until you delete it or your account. Deletion is immediate in the live database and propagates through backups within 30 days.
• Consent records and audit logs: kept for six years after the consent ends, because the proof that you consented is the thing that protects you if we are ever questioned about it.
• Billing records: as long as tax law requires, which is typically six to seven years.

Detailed in the cookie notice, which also has the control that clears your stored choices so you can answer again.

You are covered by General Data Protection Regulation (EU) 2016/679. Under it you can:

Where to send a request

Data subject requests: privacy@longlifelist.com. Access, correction, deletion, restriction, objection and portability. We verify identity before acting, because handing your health data to someone who says they are you would be the larger failure.

Data Protection Officer: dpo@longlifelist.com. The statutory contact under Article 37 of the GDPR. Use this route for anything you do not want going through general support, including a complaint about how we have handled a request. We publish a role address rather than an individual’s name so the route keeps working when the person in the role changes.

How long we take: One month from receiving a verified request, extendable by two further months for complex requests — we tell you inside the first month if we need the extension and why.

If we get it wrong

• Your national data protection authority (find yours via the European Data Protection Board) — You may complain to the authority in the country where you live or work. You do not have to contact us first.

Encryption in transit and at rest, per-record encryption for health data, mandatory multi-factor authentication for any staff or clinician access to patient data, row-level access control in the database, and an append-only audit log of every read of patient data. If you have found a vulnerability, please tell us: responsible disclosure.

• This is a pan-EU English-language surface. Where your national law gives you more than the GDPR does — and several member states do for health data — the national rule wins and we apply it.