Allelewise

Privacy Policy

Last updated: October 28, 2026 · Draft for legal review

The operator’s legal identity, country and public contact address have not yet been provided. These draft notices describe the current service but need those details and qualified legal review before being relied on as final policies.

1. Genetic files stay on your device

Raw DNA files, Promethease reports, saved SNPedia pages, genotypes, imported findings and blueprint results are processed in your browser. Allelewise does not upload them to account services, save them in online report folders, or send them to AI. Imported scripts are not executed and imported HTML is not rendered as a webpage.

Workspace data is held in memory and clears when you refresh, close the tab, sign out, or change accounts. Your original files and any downloaded reports remain wherever you saved them. In-memory processing is not a guarantee against a compromised device, browser extensions, screen capture, or anyone with access to your device.

2. Account and sign-in information

Lovable Cloud handles account access, including your email address, password authentication or supported Google sign-in, account identifiers, confirmation and recovery, and session information. Authentication credentials are handled by the authentication service, not stored in genetic reports. Allelewise does not create additional user profiles or online genetic report storage.

Browser storage may hold authentication session tokens to keep you signed in. This is separate from genetic workspace data. Google sign-in is also governed by Google’s own policies.

3. What Helix sends

When you explicitly request a Helix explanation, the service sends only a public gene symbol or rsID and a preset topic as the AI research input. Your genotype, trait outcome, imported explanation, file and report are not included. A finding’s Ask Helix button sends its public rsID with the explanation topic.

The request uses an account access token to verify access. Hosting and AI services may process technical information such as network addresses, timestamps, request metadata and usage records. No saved chat history is created by Allelewise. Public marker requests can still reveal what you are interested in; do not treat AI requests as anonymous. Provider operational logging is separate from your browser-only genetic workspace.

4. Hosting, external services and links

Hosting, authentication, email delivery and AI processing involve service providers. Loading externally hosted fonts can disclose your network address and request metadata to the font provider. Following a SNPedia reference or other external link takes you to a service with its own privacy practices.

Operational security, reliability and error monitoring can involve technical logs. Do not put genetic information into account fields or support messages. Provider retention periods, hosting locations, and any jurisdiction-specific transfer safeguards require confirmation before this draft is finalized.

5. Purpose, retention and security

Account information is used to provide and secure access; general AI requests are processed to answer the explanation you ask for. Genetic report content is not part of those requests and is not retained online by Allelewise.

Account records may remain after sign-out, which ends access but does not delete your account. Exact account and operational-log retention periods are not yet specified. No internet service or device can guarantee absolute security. Protect your device, login details and downloaded reports; PDFs are not password-protected.

6. Your choices and privacy rights

You can clear the imported report, refresh or close the tab, or sign out to discard workspace data. Delete downloaded reports and original files using your device’s own controls if you no longer want them. Genetic files cannot be retrieved from Allelewise after the workspace is discarded because they are not stored online.

Depending on your location, you may have rights to access, correct, delete or restrict account information, object to processing, withdraw applicable consent, and complain to a data protection authority. Sign-out is not an account-deletion request. A public contact address and the process for account/privacy requests must be supplied before this draft is finalized.

7. Policy updates

The date above identifies this draft version. The final policy must identify the operator, relevant legal bases where required, verified provider arrangements and retention details, and a working privacy contact. This draft is not a claim of GDPR, HIPAA, or other regulatory compliance.