Contact

Before you write

The user guide walks through every analysis, the FAQs answer the questions people ask most, and the developer documentation covers the REST API.

Report a problem

A report that includes these can be acted on:

• The address of the page
• What you did, step by step
• What you expected to happen
• What happened instead, with the exact error text
• The date, time and time zone
• Your browser and operating system
• The job id, if the page shows one

If you use the API, add the X-Request-ID header of the failed response when it has one; errors from the proxy, such as a 413 for an oversized upload, carry none, so give the status code and time instead. Never include passwords, access tokens or verification codes, and never patient-level clinical data.

There is no published address to send a report to yet. Keep these details; they are what the site's operator will ask for.

Your data and privacy

You do not need to write to anyone to use your rights over your data. In Settings → Privacy you can download a copy of your account records (not your files, figures or results), ask for all your data to be erased, and turn usage analytics off; Settings → Account deletes the account. The Privacy Policy explains what is collected and why.

Account and sign-in

• Forgot your password? Reset it by email, or by SMS where this site offers it.
• Locked out after failed attempts? Wait for the lock to lift, then sign in again; the guide gives the limits.
• Saw a sign-in you do not recognise? Sign that device out in Settings → Account, change your password, and turn on two-factor authentication.

Accessibility

The accessibility statement lists what is known not to work yet and what to include when you report a barrier.

Using the API

Errors, limits and retries are covered in Handle errors and rate limits, and every status the API returns is in the reference.