Privacy Policy
Draft template. Have a qualified lawyer review it before you sell anything, and make sure it matches what you actually collect. Claiming more or less than the truth are both problems.
In one line
We collect only what is necessary to sell you the product, deliver it, and let the software activate. No profiling, no tracking cookies, and we do not sell your data to anyone.
Controller
The controller for the purposes of the UK GDPR and EU GDPR is the copyright holder of PreciSim. Contact: privacy@precisim.com.
What we collect, and why
Website
| Data | Purpose | Lawful basis (GDPR) | Retention |
|---|---|---|---|
| Phone number (if you sign in with one) | Sign-in by SMS code, account recovery | Contract (Art. 6(1)(b)) | While the account exists |
| Email address | Sign-in by email code, licence delivery, transactional notices | Contract (Art. 6(1)(b)) | While the account exists |
| Password (only if you choose to set one) | Letting you sign in with a password | Contract (Art. 6(1)(b)) | While the account exists; stored as a salted hash only |
| Identifiers returned by a third-party sign-in you link (e.g. GitHub user ID, username, email, avatar) | Linking the account; inviting you to a private repository | Contract | While the link exists |
| Session data (IP address, browser identifier, sign-in time) | Showing you your signed-in devices so you can sign them out; abuse prevention | Legitimate interest | Session lifetime (30 days at most) |
| Request IP address (rate limiting only) | Stopping scripts from flooding the code endpoints | Legitimate interest | In memory for up to 24 hours; never written to the database |
| Order data (number, item, amount, time) | Fulfilment, invoicing, reconciliation | Contract; legal obligation | 10 years (statutory accounting retention) |
| Invoice details (company name, tax number) | Issuing invoices | Legal obligation (Art. 6(1)(c)) | 10 years |
| Git platform username and user ID | Inviting you to a private repository | Contract | While repository access lasts |
| Language and theme preference | Remembering your choice | Legitimate interest | Stored in your browser only |
We do not collect behavioural profiles, cross-site tracking data, IP-based location analysis or browser fingerprints.
One-time codes are kept only for their 5-minute lifetime and deleted once used or expired. Passwords are optional: you can always sign in with a one-time code. If you choose to set one, we store only a salted hash (scrypt), never the password itself, and it cannot be reversed; it is kept for as long as the account exists. Sending a code and signing in with a password both require a human check (Cloudflare Turnstile on the international site, Alibaba Cloud Captcha on the China site); neither is used for advertising or profiling. Account events (sign-in, code sent, link, unlink, password set, deletion) are written to an audit log kept for 2 years.
Site analytics use self-hosted Umami: no cookies, no full IP addresses, aggregate figures only that cannot be traced back to an individual. That is why this site has no cookie consent banner — because it genuinely does not need one.
Campaign links: when you arrive through a link carrying campaign parameters (utm_source and
similar), we record one anonymous event with those parameters and the landing path; if you click a
download on that page, we record one more with the same content. Each event gets a random ID and
nothing is stored in your browser, so two visits cannot be linked, and no IP address is kept.
Nothing is sent when your browser has Do Not Track on. The only purpose is knowing which channels work.
Desktop software
| Data | Purpose | Note |
|---|---|---|
| Machine code | Licence activation and seat management | A hash of motherboard and disk serials; not reversible, contains no personal data |
| Software and OS version | Update and compatibility checks | |
| Anonymous usage events (can be switched off) | Knowing whether the product is actually being used | See below |
About anonymous events
Two fields only — an anonymous ID and an event name:
{ "anonId": "a3f2… (generated on this machine, tied to no account)", "name": "first-lab-completed" }Not included: machine code, licence key, file paths, calibration data, images, anything that links to an IP address.
There is one purpose: knowing how many people actually complete the first lab. That number says more about whether the product works than the order count does.
To switch it off: Settings → Privacy → Anonymous usage statistics. Nothing else changes.
What we never collect
Stated explicitly, because industrial users worry about exactly these:
- not your calibration results, recipes, part drawings or camera images;
- not the contents of machine configuration files;
- no automatic log upload — logs stay local and you decide whether to send them;
- not your network topology or other devices on it.
Who receives your data
| Recipient | What they get | Why |
|---|---|---|
| Merchant of Record (Paddle) | Order and billing data | They are the legal seller for international orders; they collect payment and remit tax |
| Email provider (Resend) | Email address, message content | One-time codes and transactional email |
| SMS provider (Alibaba Cloud SMS, China site only) | Phone number, code | Sign-in codes |
| Human-check provider (Cloudflare Turnstile / Alibaba Cloud Captcha) | Browser environment signals | Telling scripts from people before a code is sent |
| Third-party sign-in platform (GitHub, only if you link it) | Your identifier on that platform | Linking the account |
| Code hosting platform (GitHub, or self-hosted GitLab) | Git username | Repository invitations |
| Cloud provider | Hosting of our database and services | Infrastructure |
Beyond what is necessary to perform the contract, we disclose your personal data to no one, and we never sell it.
We never see or store your card number — the Merchant of Record handles payment on its own infrastructure under its own privacy policy.
Where data is stored
International data is stored outside mainland China; the China-region site stores its data inside mainland China. The two deployments are independent and we do not synchronise user data between them — this avoids cross-border transfer issues and keeps the boundary clear.
Your rights
Under the GDPR (and comparable laws elsewhere) you may:
- access — your account page shows everything we hold about you;
- rectify — edit it yourself, or write to us;
- erase — Account → Sign-in & security → Delete account, self-service. Deletion starts a 30-day cooling-off period (signing in again cancels it); after that we remove your account and personal data, but order and invoice records are retained for 10 years with personal data removed, as required by accounting law. Deletion revokes every licence on the account and removes source repository access;
- port — Account → Sign-in & security → Export data gives you a JSON file immediately;
- object / restrict — to processing based on legitimate interest;
- withdraw consent — turn off anonymous statistics, unsubscribe from email, at any time.
Write to privacy@precisim.com. We respond within 30 days. You also have the right to complain to your local supervisory authority.
Security
- HTTPS everywhere;
- secrets and tokens live in a secret store, never in the repository;
- email one-time codes are stored hashed; SMS codes are deleted after 5 minutes;
- logs are redacted: no full licence keys, no machine codes, no full phone numbers or codes in clear text;
- daily database backups, with restore drills;
- the admin area requires elevated privileges, and every manual action is written to an audit log.
Children
The product is aimed at engineers and students, normally adults. We do not knowingly collect personal data from children under 16. If you believe we have, contact us and we will delete it.
Changes
Revisions are published on this page with a date. Changes that broaden what we collect are announced by email in advance.
This is the English version. Where the Chinese and English versions differ, each governs in its own jurisdiction.