greatgenes

Raw DNA privacy: why your file stays on your device and how to check it

A raw DNA file can be analysed in two main ways: you upload it to a company’s server, or a program runs on your own device and the file never leaves it. Both are used by real services. This page explains the difference and the trade-offs, and shows how to check for yourself, in about five minutes, that greatgenes does not send your file.

Upload model
the file is copied to the service’s server and analysed there; what happens next depends on the service’s policy
In-browser model
the program and reference data come to your device; the file is read there and not sent
greatgenes
analyses in your browser; neither the file, nor any part of it, nor its name, nor the report is sent to the server
How to check
the browser’s Network tab lists every request a page makes

Why raw DNA is sensitive

In short: your DNA cannot be changed like a password, and it says something about your relatives too.

Two models side by side

QuestionUpload to a serverAnalysis in your browser
Where the file goesa copy goes to the service’s serverit stays on your device; the program comes to it
Who could access itthe service, its hosting provider and anyone who breaks in, for as long as it is storedwhoever can access your device
Deletionyou rely on the service to delete it when promisednothing to delete on the server; you delete your own copy
What you can verifythe policy text; what happens on the server cannot be seen from outsideevery request the page makes, in the browser’s Network tab
Account and historyresults can be kept in an account and reopened lateryou save the report yourself; the service keeps nothing to reopen
Computing powerthe server can run heavy methods, for example filling in unmeasured positions (imputation)limited by your device; the first visit downloads the program and reference data
Trust in the codeyou trust the server program, which you cannot seeyou trust the program sent to your browser, which can change between visits — the Network tab shows what it does each time

Neither model is automatically safe or unsafe. An upload service with a strict policy and prompt deletion can be a reasonable choice; an in-browser tool still needs you to trust the code it sends. What differs is how much you can check yourself. For how specific services describe their handling, see greatgenes compared with other raw DNA tools.

How to check that your file stays with you

In short: sending a file needs a POST or PUT request with a body about the size of the file. If every request is GET, the browser only received data.

You do not have to take our word for it. Your browser can show every request the page sends, and it takes about five minutes on a computer.

Every desktop browser has developer tools. Their Network tab lists each request the page makes: where it goes, whether it sends or receives data, and how much.

Important: open the Network tab before you choose the file. The browser records requests only while the panel is open; if you opened it later, reload the page and start again.

Chrome, Edge, Opera

  1. Open the greatgenes page and press F12 (on a Mac, ⌘+⌥+I).
  2. Select the Network tab.
  3. Choose your file: the analysis starts at once. Wait for the report.

Firefox

  1. Open the greatgenes page and press Ctrl+Shift+E (on a Mac, ⌘+⌥+E): the Network tab opens directly.
  2. Choose your file: the analysis starts at once. Wait for the report.

Safari (Mac)

  1. Once: Safari → Settings → Advanced → tick “Show features for web developers”.
  2. Open the greatgenes page, then Develop → Show Web Inspector (⌘+⌥+I) and the Network tab.
  3. Choose your file: the analysis starts at once. Wait for the report.

On a phone, the Network tab opens only with the phone connected to a computer, so a computer is easier. The page and the analysis are the same on both.

What you will see

Every request on the analysis page uses the GET method, which asks for data instead of sending a file: the Method column says GET in every row (if there is no Method column, right-click the table header and turn it on). Type method:POST into the Filter box (Chrome, Edge, Firefox) — the list stays empty.

Diagram: the method:POST filter gives an empty list The Network tab filter box contains method:POST and is highlighted. The table of requests is empty: not a single request that sends data. This is how it should be. Elements Console Network Sources method:POST NameMethodStatus TypeSize The list is empty ✓ Not a single request that sends data — this is how it should be
Figure 1. The method:POST filter (Chrome, Edge, Firefox) shows only requests that send data. After an analysis in greatgenes the list is empty. This is a diagram, not a screenshot.

What you will not see: any request that sends your file — no upload with a size close to the size of your file, and no requests to other sites.

What an upload would look like

If a site sent your file to its server, the Network tab would show:

On greatgenes there is nothing like this. The only POST on the site is the feedback form, from its own page and only when you press “Send”; it sends just the text you typed. If you ever see your file being sent, it is a bug — please tell us through the feedback form.

Browser extensions run separately and are not covered by this check. If you are unsure about yours, open the page in a window without them (for example, a guest profile).

Questions to ask any service

  1. Is the file analysed on my device or on your server?
  2. If it is uploaded: is it stored, for how long, and where?
  3. Can I delete the file and the results, and is deletion confirmed?
  4. Do I need an account, an e-mail address or a payment to use it?
  5. Is the data shared with or sold to anyone, including for research?
  6. Can I check any of this myself?

Technical details

Every request the page sends, its parameters and what the server records are described in the methodology and the privacy policy.

Analyse your file — in your browser, without uploading it.