Beta · Launching 1 October 2026 (). Features may change. Feedback welcome at contact@ampliova.com

Legal

Privacy Policy

Ampliova is designed for scientific work. We collect only what is strictly necessary to operate the service and never share or monetise your data.

Data controller

Who is responsible for your data

Louis Müller, micro-entrepreneur (France)
Address: 21 Avenue Pauline, 94000 Créteil, France
SIRET: 108 830 514 00015
Code APE/NAF: 63.11Z – Traitement de données, hébergement et activités connexes
TVA: Non applicable (article 293 B du CGI)
Contact: contact@ampliova.com

Data collected

What we collect and why

DataPurposeLegal basis
Email address + passwordAuthentication (Supabase Auth, EU West, Ireland)Contract performance
Display nameAccount personalisation (optional)Legitimate interest
Uploaded RDML filesqPCR analysis. Stored temporarily on Supabase Storage (EU). Never shared with third parties. Never used to train AI models.Contract performance
Analysis data (Cq values, results, parameters)Stored in Supabase EU database to allow later review and export.Contract performance
Beta waitlist emailBeta access contact only. No marketing without explicit consent.Consent
Primer database search queriesLogged with your account ID (if signed in) to surface genes researchers search for but can't find, so we know what to add next. Never used for advertising or shared with third parties.Legitimate interest
Primer database contributionsPrimer pairs and efficiency measurements you submit are linked to your account for attribution and curation history. Entries marked public are visible to all Ampliova users as part of the shared primer database.Contract performance / consent
Payment dataNot collected at this time. Stripe will be integrated later; no banking data will ever transit through Ampliova's servers.

Infrastructure

Hosting and subprocessors

ProviderRoleData residency
SupabaseDatabase + file storageEU West (Ireland), GDPR compliant
VercelFrontend hostingEU, GDPR compliant
Vercel AnalyticsAggregate page-view countsCookieless: no cookies or persistent identifiers are set, no individual visitor is tracked. Only aggregate, anonymized page-view statistics are collected.
RailwayPython analysis engineComputation data transmitted transiently; not persisted on Railway.
Mistral AIPlate layout parsing (Mistral Small)Only scientific data (sample names, gene names) is transmitted (no personal data). Data processed transiently and not retained per Mistral AI's API data policy. EU-based company (Paris). AI features available on paid tiers only.
ResendTransactional email delivery (team invitations, beta access notifications)Recipient email address transmitted for delivery only. No marketing emails sent without explicit consent. GDPR compliant.
StripePayment processingNo payment data transits Ampliova's servers. Stripe handles all card data directly under PCI-DSS compliance.

Security

How your data is protected

  • In transit: all connections to Ampliova are encrypted (TLS).
  • At rest: the underlying database and file storage are encrypted at rest by Supabase (AES-256, EU infrastructure).
  • Batch names and notes(the free-text labels and comments you write yourself) are additionally encrypted at the application level (AES-256-GCM) before being stored. The decryption key is held only in Ampliova's server infrastructure; it is never stored in the database and never sent to your browser.
  • Access between accounts: row-level access control ensures a batch (including sample and group labels, gene names, Cq values, and computed results) is only ever visible to its owner and, where explicitly shared, their team or organisation, never to other Ampliova customers.
  • Who can access your data: database access is limited to what is needed to operate and support the service (e.g. diagnosing a reported bug) and is never used to browse, share, or analyse your research data for any other purpose.

Retention

How long we keep your data

  • Account data: retained until you delete your account.
  • Uploaded plate files (RDML, or QIAGEN GeneGlobe CSV/XLS exports): stored in Supabase EU storage for the lifetime of the batch, to allow re-analysis. Deleted when the batch is deleted or upon account deletion.
  • Beta waitlist emails: deleted on request.

Cookies

Cookies and tracking

Ampliova sets exactly two cookies, both strictly necessary for authentication. No advertising or tracking cookies are used. Page-view statistics are collected through Vercel Analytics, which is cookieless: it sets no cookie and assigns no identifier to your browser or device.

Cookie namePurposeDurationNecessary
sb-[ref]-auth-tokenmay be split into chunks .0 .1… if the JWT payload exceeds 4 KBStores the authenticated session (JWT access token + refresh token). Set by Supabase Auth when a user signs in. Read on every request by the Next.js middleware to verify authentication.400 days✓ Strictly necessary
sb-[ref]-auth-token-code-verifiermay be chunkedPKCE (Proof Key for Code Exchange) verifier. Created at the start of an OAuth2 / magic-link / invite flow and deleted immediately after the code is exchanged for a session. Prevents authorisation-code interception attacks.Transient (seconds)✓ Strictly necessary

Both cookies are set by Supabase Auth, hosted in the EU (Ireland). They contain no personal information beyond the authenticated session token and are never transmitted to advertising networks or analytics platforms.

No consent banner is required. Under Article 5(3) of the ePrivacy Directive and the CNIL guidelines on cookies, strictly necessary cookies (those without which a service explicitly requested by the user cannot function) are exempt from the prior-consent requirement. Both cookies above fall squarely within this exemption. Vercel Analytics falls outside the scope of these cookie rules entirely, since it stores nothing on your device.

Your rights

GDPR rights (Art. 15–22)

You have the right to access, rectify, erase, port, and object to the processing of your personal data.

Changes

Policy updates

In the event of a material change, registered users will be notified by email at least 14 days before the change takes effect.

Effective date: 1 June 2026