Privacy policy
What happens to your DNA file, what the greatgenes server learns and what it records.
Version of 2026-10-21. The version published on this page applies.
In short
- Your browser reads and analyses the DNA file. Neither the file, nor parts of it, nor the report are sent to the server.
- The server receives only service requests, like any website, a signal that the main page was viewed and short signals about the progress of the analysis (the step and a result code).
- Server logs are kept for 14 days. The program’s log contains no addresses.
- No third-party analytics, advertising or third-party scripts. There is one cookie — a technical one, for 30 minutes.
- The service is run by the operator of greatgenes, a private individual. Server logs contain no addresses or other personal data (their contents — in “Logs and retention”). A possible exception is the web server’s error log when a connection fails, and the hosting provider’s logs.
Your DNA file and report
Your browser reads the file — on your computer or phone. Parsing the file, comparing it with the knowledge base and preparing the report all happen inside the open tab. Neither the file, nor parts of it, nor the file name, nor the report are sent to the server.
The report exists only on your screen. If you saved it as HTML or PDF, it is kept by you, and we have no access to it. You can check this yourself — on the “How to check that your file stays with you” page.
What the server learns
The browser downloads from the server the analysis program, a session key and the part of the knowledge base for your chip model. From these requests the server sees:
- The connection address (IP) and the time — like any website. The address is kept in memory only for the limit (no more than 3 analyses per hour from one address): by the program, as an irreversible tag that is forgotten after an hour.
- The session number in the
geans_scookie. - The chip model — from the name of the downloaded part of the database. It is the same for everyone who has that chip.
- Whether the full database was needed — that is, whether the file has positions outside the chip’s standard set (which ones is unknown), or whether the chip model or genome build was not recognised.
- Signals about the progress of the analysis. When the main page has loaded, the browser sends one short request that says only “page viewed”. After the file check, after the analysis and after the report is shown, it sends a short request: which step finished and how — “ok” or the kind of error (for example, “no connection” or “file not recognised”). No file data, no chip model and no cookie.
- Intervals between requests and the ordinary browser information (type, version, language). The contents of the file cannot be recovered from them.
The server does not receive the contents of the file, genotypes, the file name or the report. If you write to us through “Contact us”, the server receives what you wrote (see “Feedback messages”).
Cookies and browser storage
| What | Why | How long it lives |
|---|---|---|
Cookie geans_s (set by the server) | Session number after the browser check. A random number signed by the server; it contains nothing about you. Not accessible to page scripts. The analysis does not work without it. | 30 minutes |
The geans_lang entry in browser storage (localStorage) | The selected page language. Not sent to the server. | Until you delete it |
There are no other cookies. Both entries can be deleted in the browser settings (“Clear site data”).
Logs and retention
- The logs of the server program and the web server contain the time, the method, the request path without parameters, the response code and size. The paths show for which chip models parts of the database were downloaded. There are no addresses, cookies or browser types in them.
- When a connection fails, an address may get into the web server’s error log: the format of that log cannot be configured.
- Logs are kept for 14 days and then deleted automatically.
- The session and address tags for the limits exist only in the server’s memory, for up to 30 minutes and up to an hour (tags of IPv6 networks for the form’s daily limit — up to a day).
- The hosting provider and internet providers may keep their own logs. They are outside our control.
Feedback messages
- If you send the “Contact us” form, we receive the message text, the contact you gave (optional) and the date — without the time and without your address.
- The operator of greatgenes reads messages to answer you and to fix the service. Please do not include genotypes or health information.
- Messages are kept for one year: they are stored in monthly files, and each file is deleted a year after its last message, so a message is kept for at most 13 months.
- To have your message deleted earlier, send a new message with the date and the first words of the one to delete.
Consumer health data
This section is our consumer health data privacy policy under US state laws such as the Washington My Health My Data Act, the Nevada and Connecticut consumer health data laws and the California Genetic Information Privacy Act.
- greatgenes does not collect, store, share or sell consumer health data or genetic data on its servers. Your DNA file, your genotypes and your report are analysed only in your browser, on your device, and never reach us.
- What the server receives from your browser is listed under “What the server learns”: service requests, the chip model of the downloaded part of the knowledge base, a “page viewed” signal and short signals about the steps of the analysis. None of it contains your genotypes or your results.
- The only health-related information we could receive is what you choose to type into the feedback form — please don’t. We use such a message only to answer you and to fix the service, never share or sell it, and delete it as described under “Feedback messages”. You can ask us to delete it at any time through the “Contact us” form.
Legal bases and your rights
- Who is responsible. The operator of greatgenes, a private individual, is responsible for the data described on this page. You can reach the operator through the “Contact us” form.
- Legal bases. Server logs, the session cookie and the address tags for the limits: our legitimate interest in running the service and protecting it from abuse (Article 6(1)(f) of the GDPR and the UK GDPR). Feedback messages: our legitimate interest in answering you and fixing the service (the same article). We do not process your genetic data at all.
- Your rights. Where data protection law such as the GDPR or the UK GDPR applies, you may ask us for access to, correction or deletion of personal data we hold about you, ask us to restrict its processing, and object to it. In practice the only such data we may hold is a feedback message and the contact you gave.
- Complaints. You can complain to the data protection authority of the country where you live or work.
- Disclosure. We do not sell or share personal data. We disclose the little data we hold only when the law requires it.
What we do not have
- Accounts and registration: there are none, and no personal data is collected for access.
- Third-party analytics, advertising, third-party scripts and fonts. The page cannot connect to other sites — this is
forbidden by the
Content-Security-Policysecurity rule. - Any of your data to delete, correct or hand over on request: the file and the report never reach us, and the program’s log has no addresses. The exception is a feedback form message, if you sent one (see “Feedback messages”).