Privacy Policy

1. Controller

The controller within the meaning of the GDPR and the FADP is the operator, see the Legal Notice.

2. What data we process

3. Processing by third parties

The Core Analysis transmits nothing to the services below. The following paragraphs concern the full analysis for signed-in users.

Part of the analysis runs at external services. What they receive depends on the kind of data:

Important: Sequences you analyze are sent over the internet to these third parties. Do not submit confidential, patent-protected or unpublished constructs, and no patient-identifiable sequence data without appropriate agreements. Patient-related genetic data constitutes sensitive personal data (Art. 5 lit. c FADP) and a special category of personal data (Art. 9 GDPR); processing such data through this service is neither intended nor permitted.

4. Applicable law and legal bases

The operator is domiciled in Switzerland, so the Swiss Federal Act on Data Protection (FADP) applies. Insofar as the service is directed at users in the EU/EEA, the GDPR applies in addition (Art. 3(2)(a) GDPR).

Account data is processed to perform the contract (Art. 6(1)(b) GDPR; Art. 31(2)(a) FADP). Your sequence and the search terms derived from it are transmitted to the services listed in section 3 solely on the basis of your explicit consent (Art. 6(1)(a) GDPR; Art. 6(6) FADP). It is obtained in a dedicated dialog before your first analysis from the depth Standard on, naming the recipients, the destination countries and the risks; the grant is logged with its timestamp and wording (Art. 7(1) GDPR). Without a recorded consent the server refuses every analysis from the depth Standard on; the depth Instant runs without it, because nothing leaves our server then. You may withdraw at any time with effect for the future — one click in Settings; analyses already performed are not undone (Art. 7(3) GDPR). If the set of recipients changes, existing consent ceases to apply and is obtained afresh.

Your input to the Core Analysis is processed to provide the analysis you requested (Art. 6(1)(b) GDPR; Art. 31(2)(a) FADP).

The server logs and the short-lived counting of sign-in attempts rest on our legitimate interest in secure operation (Art. 6(1)(f) GDPR; Art. 31(1) FADP).

5. Transfers abroad

Some of the services listed in section 3 are located outside Switzerland and the EU/EEA:

Risk notice: In the cases above without an adequacy decision, protection equivalent to that of Switzerland or the EU is not guaranteed. In particular, U.S. authorities may access transmitted data under surveillance powers (including 50 U.S.C. § 1881a — FISA Section 702 — and Executive Order 12333) without effective remedies being available to you. Enforcement of your data subject rights may be practically impossible there.

6. Storage location + hosting

Server hosting with Hetzner Online GmbH, data center in Germany; emails are also sent through Hetzner. The daily database backups are kept on the same server.

7. Cookies and local storage

We set a technically necessary cookie (cartcheck_token) for the login session; it expires after seven days. While the website is in a closed test phase behind an access code, we set a second technically necessary cookie (cartcheck_gate) once a valid code has been entered: it records that this browser entered a valid code, does not contain the code itself and expires after 30 days; signing out does not delete it. We use your browser's local storage only for the settings and content listed in section 2. No tracking, no analytics, no advertising.

8. Retention

Account data, your own content, settings, keys and records are kept as long as your account exists and are deleted when the account is deleted (section 10). AI search reports are kept as long as your account exists too, without any further deadline; you can delete them yourself, one by one or all of them in Settings (the three newest finished ones also in the AI search, if you have access there), with their copies in the browser you delete them in (section 2), but not all of them while an analysis from the depth Standard on or a batch of your account is running, and a running one only once it has finished; they are deleted with the account. After the account is deleted, the bookings of your AI access, the redemptions of unlock codes and the cost rows of the AI search remain, with a locked account without email address, password and name: the bookings and redemptions count towards the limits of the unlock codes and of the monthly use, the cost rows towards cost accounting. That account also keeps the time of registration and the counter of AI evaluations outside the AI search (section 2, usage data). Server logs are rotated daily and deleted after at most 15 days. The daily database backups are deleted after 14 days; until then a deleted account may still be contained in them. Password-reset codes expire after one hour; sign-in attempts are counted for five minutes. Input to the Core Analysis is not stored permanently; its result is discarded after at most one hour. Files uploaded without an account expire after at most one hour.

9. Your rights

You have the right to information, rectification, erasure, restriction of processing, data release or portability, and to object (Art. 25 et seq. FADP; Art. 15–21 GDPR). You also have the right to lodge a complaint — in Switzerland with the Federal Data Protection and Information Commissioner (FDPIC), in the EU with the supervisory authority of your country of residence. Please write to admin@car-t-check.com.

10. Delete account

In Settings, under “Delete account”, you can delete your account yourself; on request to admin@car-t-check.com we delete it as well. Deleted are your account data (email address, password, username, name, institution, short description and profile photo), your own content (domains, constructs with their versions, groups and shares), settings and keys, records and all stored reports, and, if you delete in Settings, the copies of the reports in that browser too; what remains afterwards is set out in section 8. Versions you contributed to another person's construct stay in their history, without your name. On backups see section 8.

Last updated: 11 November 2026