Privacy policy & data practices

• Account identifiers — your email address, your first name (where you choose to provide one), and a password you set. We do not collect a username that is publicly displayed.
• Authentication session — a session cookie used to recognise you across requests once you sign in. The session expires when you sign out or after a period of inactivity.
• Uploaded lab files — photographs, scanned PDFs, or other files you send to the analyzer to be read. Hemavoy treats an uploaded lab file as containing personal health data; it is processed to extract biomarker values and is not retained long-term on Hemavoy's own servers.
• Manually-entered biomarker values — the values you type into the analyzer row by row, alongside the age and gender you provide for scoring.
• Extracted interpretation outputs — the per-marker scoring results and the plain-language explanations produced from your inputs, including any saved reports on your account history.
• Language preference — the locale you pick on the language switcher (Romanian or English). Stored in a cookie called NEXT_LOCALE so the whole site reads in the language you chose.
• Newsletter and waitlist submissions — if you opt in, your email address and (for the waitlist) your first name, used to keep you posted about new language launches and major feature releases.
• Support correspondence — any email you send to office@hemavoy.com or privacy@hemavoy.com, plus the replies we send back.

• Contract — to provide the Hemavoy analyzer, your saved reports history, and the account features you sign up to (Art. 6(1)(b)).
• Consent — for the newsletter, the waitlist, and any optional features we add later. You can withdraw consent any time (Art. 6(1)(a)).
• Legitimate interests — to keep the site secure, prevent fraud, debug issues, and respond to your support emails, where these interests are not overridden by your rights (Art. 6(1)(f)).
• Legal obligation — to comply with accounting, tax, and consumer-rights obligations (Art. 6(1)(c)).

1. Sign in and open your account page. Use the Delete account action to trigger an immediate account deletion request tied to your session.
2. If you no longer have access to your account, write to privacy@hemavoy.com from the email address used at signup. We confirm the request over a verified channel before acting on it.
3. Once the request is verified we delete your account row, the saved interpretation history tied to it, and your authentication session. We also instruct our subprocessors to delete any data they hold for this account within their respective retention windows.
4. We send a confirmation email when the deletion is complete. The retention periods for the data we hold on your behalf are listed in section 6 — each is a working placeholder pending legal review.

AI extraction (lab-file reading and interpretation)

When you upload a lab file we send it to a Cloudflare Worker running the Hemavoy-AI extractor. The worker reads your file, returns anonymised biomarker values to the Hemavoy app, and does not retain the file beyond the request. [PENDING LEGAL VERIFICATION] — Verified processor name and data-processing agreement reference.

Payments (Stripe Connect)

Paid tiers are processed by Stripe via the Polsia Stripe Connect integration. Stripe receives your card details on its hosted checkout page and returns only a payment confirmation to Hemavoy. Hemavoy does not see or store your card number. [PENDING LEGAL VERIFICATION] — Verified Stripe entity, region, and the data-processing addendum reference.

Other infrastructure

• Hosting — Polsia-managed hosting on the Polsia platform. [PENDING LEGAL VERIFICATION] — Verified hosting region and data-processing agreement reference.
• Email delivery (transactional + newsletter) — the Polsia-managed email proxy. [PENDING LEGAL VERIFICATION] — Verified processor name and data-processing agreement reference.
• Authentication — session cookies and account records are managed by the Polsia auth module (better-auth). [PENDING LEGAL VERIFICATION] — Verified processor name and data-processing agreement reference.

• Access — request a copy of the personal data we hold on you (Art. 15).
• Rectification — ask us to correct inaccurate data (Art. 16).
• Erasure — ask us to delete your data (Art. 17), subject to the obligations in section 7.
• Restriction and objection — restrict processing or object to processing based on legitimate interest (Art. 18, 21).
• Portability and complaint — receive your data in a portable format (Art. 20) and complain to your national supervisory authority (Art. 77).