Privacy policy
Every sentence here describes what the code does today. When the code changes, so does this page, on the same day.
1. Who is responsible
Viktor Kuznetsov, an individual, is responsible for how Optisaur handles your data. Write to kuznetsov.forge@gmail.com about anything on this page.
2. What we collect
As a guest: a random session id in a cookie; a hashed form of your network address (or nothing at all, if the site is run without the key needed to hash it), used only to limit how many sessions one address can start; and what you upload and build during the session.
With an account: your email address, a hashed form of your password, when you confirmed your address, your plan, and when you last signed in.
When you use the assistant: your request in plain English; the shape of your tables - column names, types, ranges, how many blanks, up to five example values per column - never the rows; the assistant's answer, how long it took and what it cost us. Your requests are kept as your own history.
When you solve: the model, the data it reads, the result and the sensitivity figures, with which version of the software produced them.
When something breaks: an error report with the error, the page or route, a request id and the browser type - never a request body, a prompt or a spreadsheet.
Counts: that the front page was shown, that a guest session started, that a first solve finished, that someone registered or signed in, that a day had activity. These are counted against a random id that is not your session, your account or your address.
Operational logs: identifiers, sizes, timings and statuses, and at the web server a request log - when, which page, with what result, from which kind of browser - with your address dropped before the line is written. Never your data, your models, your results or your requests.
3. What we do not collect
Your raw network address is never stored - only a salted hash of it, for abuse limits, or nothing. There is no advertising, no third-party analytics, no fingerprinting and no tracking cookie. We do not buy or sell data about you.
4. Why
- To run the service you asked for: storing your work, solving your models, answering your questions. This is what you came for, and the basis for it is the agreement between us.
- To keep it safe: the abuse limits on sign-ins, registrations and guest sessions. Our legitimate interest in a service that stays up.
- To know whether it works: the counts, and the error reports. The same interest; neither identifies you.
- To email you about your account only: an address confirmation, a password reset. Nothing else is ever sent.
5. Who else sees something
| Who | What they see | Where |
|---|---|---|
| Anthropic | The assistant: your request in plain English and the shape of your tables - column names, types, ranges, how many blanks, up to five example values per column - never the rows themselves. Anthropic's API terms apply; your data is not used to train models. | United States |
| Sentry | Error tracking: when something breaks, the error, the page or route, the request id and the browser type. Never a request body, a prompt or a spreadsheet. | European Union or United States, per the project's region |
| DigitalOcean | Runs the server the site and the database live on, and holds the encrypted backups. | Frankfurt, Germany (European Union) |
| PLACEHOLDER (email provider) | Delivers the emails the site sends you: an address confirmation, a password reset. Nothing else is ever sent. | PLACEHOLDER (provider location) |
6. How long
| What | Kept | Then |
|---|---|---|
| A guest session and everything it made: projects, uploads, models, results | 24 hours after your last visit, 48 hours at most | deleted, files included, by a sweep that runs every 15 minutes |
| An account, its projects, uploads, models, results and assistant history | while the account exists | deleted on request (see your rights) |
| An upload the site could not read | until you delete the dataset it belongs to | kept so you can see what went wrong, then deleted with the dataset |
| Your sign-in (the refresh cookie) | 14 days, renewed each time it is used | revoked when you sign out |
| An email-confirmation link | 24 hours, usable once | expires |
| A password-reset link | 60 minutes, usable once | expires |
| A cached assistant answer | 24 hours | expires |
| Funnel counts (a visit, a session started, a first solve, a registration, a sign-in, a day of activity) | indefinitely | they carry no name, address or session: only a random id that nothing else holds once the session or account is gone |
| Error reports | 30 days, by the error-tracking provider | deleted by the provider |
| The operator's audit log | indefinitely | holds account ids, not addresses; when an account is deleted its entries lose their author |
| The web server's request log (time, page asked for, result, browser type) | 14 days | rolled over; your address is dropped before the line is written, and no cookie or sign-in token ever enters it |
| Backups of the database and uploaded files | 30 days of nightly copies, then one copy a month for six months | overwritten; a deletion reaches a backup when that backup rolls over |
7. Your rights
You can ask to see what we hold about you, to correct it, to receive a copy, or to have it deleted. Write to kuznetsov.forge@gmail.com. A deletion is carried out within 30 days and removes everything the table above lists for an account, files included; what remains is one line in the operator's audit log saying an account was deleted (with no address in it), and the backups until they roll over. There is no self-service deletion or export yet: we do it by hand and confirm by email.
You can also complain to the data-protection authority where you live.
9. Age
Optisaur is not meant for anyone under 16.
10. Changes
When this page changes, the new version is posted here with its date, which is in the footer.