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
- Account: email address, password (stored only as a bcrypt hash), username, optionally a display name, institution, short description and profile photo. Username, display name, short description and profile photo are public: they appear on your profile page at /u/<username> and on the content you share publicly. A photo you upload is redrawn on our server (square, 400 × 400, WebP); this drops the camera metadata, including the location many phones store with a picture. Without a photo of your own your account shows a pattern computed from your username and stored nowhere.
- Your own content: the domains and constructs you create, including their versions, your groups and shares (with groups or with your institution), and the email addresses of people you invite to a group.
- Settings and keys: the AI provider you chose (with model and, where applicable, base URL) and, if you provide them, your own access keys — for the AI provider, for NCBI (with the email address given there; it also goes to EMBL-EBI as the contact address), Lens, EPO, KIPO, Elicit, Consensus, a web search (Brave, Tavily) or a Google Cloud service account; also whether the server's key is to be preferred to your own. Keys are stored encrypted (Fernet).
- Usage data: for the AI search, the bookings of your AI access (among others time, kind, amount, reason — for a correction by us also its explanation —, expiry of granted uses and what they refer to, such as a search, an unlock code or a refund), one cost row per search (among others the ids of the search and of the report, depth, outcome, route of the AI calls — your own key or the server's —, number of model calls, failed attempts and tokens, models, cost, start and end) and, when you redeem an unlock code, which code it was (we keep the code itself only as a hash, plus its last four characters) and the time; besides, the number of AI assessments per month outside the AI search (for the free allowance).
- AI search reports: Every completed run of the AI search, at the depth Instant too, is stored as a report so that you can retrieve it later: with the link to your account, your email address (in the report's audit record), the construct name, the sequence and the results. You can delete reports yourself (section 8).
- Core Analysis (without an account): The sequence or file you enter into the Core Analysis is processed in our server's memory only to answer your request. For the Pfam and BLAST search it is kept as a temporary file for the duration of the run and deleted afterwards. We keep the result in memory for at most one hour so that you can download it; it can only be fetched with a random key that only your browser receives, and is then discarded. Input and result are not stored permanently, not linked to an account and not transmitted to third parties: the library comparison, Pfam/HMMER and BLAST against UniProtKB run on our server.
- Uploaded files without an account: are kept in memory only, for at most one hour, and are not stored in the database.
- Domains made public: If you make one of your domains public, everyone can read it, also without signing in, labelled "user-submitted"; without signing in, neither your e-mail address nor your display name is shown. Signed-in users continue to receive the owner's display name and e-mail address for public domains (the display name is shown; when a domain is copied, the e-mail address stands in if there is no display name).
- Records: when you granted or withdrew which version of the consent (section 4) and which version of the terms of use you accepted — without IP address and without device data.
- Password reset: a one-time code, stored only as a hash and valid for one hour.
- Server logs: for every request the web server logs the IP address, time, requested address, status code, amount of data transferred, referrer and browser identifier — for secure operation, troubleshooting and fending off attacks.
- Sign-in protection: To limit repeated sign-in and registration attempts and overload from analysis, upload and BLAST requests, the web server briefly counts requests per IP address in memory; in addition, the application counts sign-in attempts in memory for five minutes. Rejected requests are recorded with the IP address in the web server's error log (retention as for server logs, section 8).
- In your browser: Language, course progress, view settings (including the quality level of the 3D view) as well as locally saved constructs, own domains and domain colours are kept in your browser's local storage. Handing a construct between the Composer, the analysis and the Plasmid view uses session storage, which ends with the browser tab. Without signing in, changes to the 3D view's settings last for the current session only; signed in, we store the 3D view's settings, the cell appearance and your domain colours in your account, so that they apply on every device. The project file exists only if you download it yourself and is not transmitted to us. The report of an AI search run that finished in this browser is kept as a copy in the browser's database (IndexedDB), so that the last report can be shown without a connection to the server; if you delete a report in this browser, its copy goes, and if you delete all reports or the account, all copies go. Apart from that, none of this storage is transmitted to us.
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:
- Your sequence (amino-acid or DNA sequence; at the AI provider together with the construct name) is sent during a full analysis from the depth Standard on to: EMBL-EBI (Hinxton, United Kingdom) for the BLAST search, with the email address you stored for NCBI as the contact address (without one, our server's), for DNA also NCBI (Bethesda, USA); the AI provider for the AI evaluation (see section 5). At the depth Instant it does not leave our server.
- Derived search terms — names of the identified domains, genes and target antigens and descriptions of BLAST hits, without your sequence and without personal data — are sent for literature, structure and database research to: NCBI (PubMed), EMBL-EBI (Europe PMC, AlphaFold DB, Ensembl), UniProt, RCSB PDB, STRING, IEDB, ClinicalTrials.gov, OpenAlex, Semantic Scholar and Reactome.
- Patent and web search, your own keys: With your own AI key the AI evaluation goes to the AI provider you chose, under your account; your NCBI key is used for the BLAST search at NCBI and for looking up patent hits there, while PubMed is never asked with yours, but with our server's, where it has one. The keyword patent search asks Lens, EPO, KIPO and Google Patents (through Google BigQuery, only where it is set up on the server) only with your consent to the patent search, also with your own keys: at the depth Standard with our server's credentials, where it has any, at Complete with your own for Lens, EPO and KIPO, if stored, otherwise with our server's; a Google Cloud service account of your own applies at both depths. The search of your sequence in the sequence listings of patents runs on our server from Standard on, where it is set up, also without this consent; we look up its hits at NCBI by their identifiers (never with your sequence), with the email address and the key you stored for NCBI. The web search asks Brave or Tavily with your own key, otherwise with our server's, where it has one. Elicit and Consensus are asked only with your own key. Where neither you nor our server has access, that search does not take place.
- 3D structures: structure files from the AlphaFold DB and the RCSB PDB are fetched by our server; your browser does not connect to these services for them.
- Email: password-reset messages are sent through the mail server of Hetzner Online GmbH (Germany).
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:
- United Kingdom (EMBL-EBI, Europe PMC): transfer based on the adequacy decisions (Art. 45 GDPR; Art. 16(1) FADP in conjunction with Annex 1 DPO).
- USA — Anthropic (AI evaluation with the operator's key, the default): Anthropic is not certified under the Data Privacy Framework. The transfer rests on the European Commission's standard contractual clauses including the Swiss addendum, which form part of Anthropic's data processing addendum (Art. 46(2)(c) GDPR; Art. 16(2)(d) FADP).
- USA — Google (only with your own Gemini key): Google LLC is certified under the EU-U.S. and the Swiss-U.S. Data Privacy Framework; transfer based on the corresponding adequacy decisions (Art. 45 GDPR; Art. 16(1) FADP in conjunction with Annex 1 DPO).
- Other providers with your own key (OpenAI or another OpenAI-compatible service; patent and web search with your own key): the request goes to the provider you chose, under your own contract with them. Where there is no adequacy decision, the transfer rests on its being necessary to perform the contract with you, because you chose that provider yourself (Art. 49(1)(b) GDPR; Art. 17(1)(b)(1) FADP).
- USA — NCBI (National Center for Biotechnology Information, NIH/NLM): as a U.S. federal agency, NCBI is not certified under the Data Privacy Framework, and standard contractual clauses cannot be concluded with it. The transfer therefore relies solely on your explicit consent after having been informed of the risks (Art. 49(1)(a) GDPR; Art. 17(1)(a) FADP).
- Australia (The Lens, optional patent search): no adequacy decision; transfer only with explicit consent (Art. 49(1)(a) GDPR; Art. 17(1)(a) FADP).
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