Legal menu · Stolid Privacy Policy
Legal
Stolid Privacy Policy
Version: 2026-11-16 · Effective date: 16 November 2026
This policy explains what personal information Stolid collects, why, who handles it and how long it is kept. It covers the website stolid.dev, requests for access, public-preview accounts, the Stolid PDF API and email with us.
Stolid is operated by Andrei Okhotnikov, an individual doing business as Stolid, in Washington, USA ("Stolid", "we", "us"). Contact: hello@stolid.dev.
The data handling page is the technical companion to this policy: it lists, store by store, what the API keeps and for how long.
The short version
- The website sets no cookies and runs no analytics.
- We collect what you send us by email, and what the API needs to run your account.
- The public preview is for sample data only. Please do not send real personal data in documents.
- API documents are rendered and stored on Amazon Web Services (AWS) in the United States, and expire automatically.
- We do not sell personal information, show ads, or share information for advertising.
1. What we collect and why
1.1 Visiting the website
| What | Why | Kept |
|---|---|---|
| Network data: your IP address, browser type and the page requested. Our hosting provider (AWS CloudFront) receives this to deliver the page. | To serve the site and protect it from attack. | We have not turned on website access logs, so we keep no record of visits. AWS may process this data briefly to operate and secure its network. |
Theme preference: if you switch between light and dark, your browser stores that choice on your device (local storage, key stolid-theme). It is not sent to us. | To remember your choice. | Until you clear your browser's site data. |
The site sets no cookies, runs no analytics and has no advertising or social-media trackers. Its fonts, styles and scripts are served from stolid.dev itself, so viewing a page does not contact any other company.
Because we do not track visitors across sites or over time, the site behaves the same whether or not your browser sends a "Do Not Track" or Global Privacy Control signal.
1.2 Requesting access
When you email us to request access, we receive your name, email address, the organisation or project you work on, your country, what you plan to render, the language you use, and anything else you write.
We use these details to respond, to decide whether we can offer access (including checks required by US sanctions rules), to arrange your preview access and to support your account. We do not add you to a marketing list.
1.3 Your preview account
| What | Why |
|---|---|
| An account ID, a short operator note saying who the account is for (for example your name and organisation), plan, status and creation time | To run your account |
| A one-way hash of each API key, the key's first characters, its mode (live or test), status and dates | To check your key on each request and to recognise it in support |
| Usage records: one record per successful render and monthly counts | To apply your monthly allowance |
| Your acceptance email, with the version and date of the terms you accepted | To keep a record of our agreement |
Your API key during onboarding. The API database stores only a one-way hash of your key. During onboarding the key itself also exists in a few other places: in the getting-started guide and examples index that we email to you, in the copy of that email in our mailbox, and in restricted files on the operator's computer that are used to build your guide. Section 4 says how long those copies are kept. Copies that you hold are under your control.
1.4 Documents you send to the API
The API receives your HTML and files, and produces a PDF, a render record and a render report. The report can quote short pieces of your document, for example the first 60 characters of the text next to a warning, an error message from the page, and web addresses the page tried to load.
The public preview is for sample data only. Our terms ask you not to send real personal data, confidential documents or secrets. If personal data is sent anyway, we process it only to render the document, on your behalf, and it expires on the schedule in section 4. Tell us and we will remove it sooner.
We use your documents only to make your PDF and its report, to help you when you ask for support, to investigate a specific security or abuse report, and to comply with the law. We do not use them for advertising, analytics or training machine-learning models.
1.5 API request logs
For each API request we log the time, method, route, status code, response size, a request ID and the IP address the request came from. The service also logs timings, render IDs, statuses and error types. These logs do not contain the content of your documents. We use them to operate, secure and debug the service.
1.6 Email and support
When you write to us we receive your email address, your message and any attachments. We use them to answer you and to fix problems. Please do not email real customer documents, whole API keys or PDF download links.
2. Who handles your information
We use a small number of providers.
| Provider | What it does | What it handles | Where |
|---|---|---|---|
| Amazon Web Services (AWS) | Runs the API: rendering, storage, database and logs | API documents, PDFs, render records, account and usage records, request logs | US East (N. Virginia), us-east-1 |
| AWS (CloudFront and S3) | Delivers the website | Website network data (section 1.1) | CloudFront serves pages from locations around the world, usually one near you; the site's files are stored in the United States |
| Fastmail | Our email | Access requests, acceptance emails, support email, and the onboarding email that contains your guide and key | Mailbox data is stored in Fastmail's United States region |
| AI coding assistants (Anthropic's Claude Code, OpenAI's Codex) | Help the operator develop and operate the service | May process account records (including the note saying who an account is for), key prefixes, usage counts, API request logs including IP addresses, and support details the operator shares with them. They are denied reading API documents, PDFs, render records and worker logs (section 3) | United States |
We do not send the contents of API documents to any other rendering provider. Email and website delivery are separate from document rendering: Fastmail does not receive your API documents unless you email them to us.
Stolid currently runs in an AWS account that also hosts another project of the same operator. Access is restricted with AWS access controls. We plan to move Stolid to an account of its own before paid plans start.
3. Who can see your information, and when we disclose it
- Routine human access to API documents is limited to the operator, and happens only when you ask for troubleshooting.
- Development and operating tools. The AWS identity that AI coding assistants use when they work for the operator has an explicit AWS permissions deny on reading API documents, PDFs, render records and worker logs, in place since 16 November 2026. This guards against accidental access; it is not a complete technical barrier, and it does not restrict the operator's own administrator access.
- Security and abuse. We may look at specific renders and records to investigate a specific security problem or abuse report.
- Legal reasons. We may disclose information when the law requires it, for example in response to a valid court order, or when it is needed to protect someone's safety or our legal rights. Where we are allowed to and it is practical, we will tell you.
- Link holders. Anyone who holds a PDF download link can use it until it expires (up to one hour). Keep links private.
- Business change. If Stolid moves to a company formed to operate it, or the business is transferred, your information moves with it under this policy, and we will tell you.
We do not sell personal information. We do not share it for advertising. We have no data brokers, advertising partners or analytics providers.
4. How long we keep things
Different stores run on different clocks. "Set to expire" means the item becomes eligible for deletion at that time; AWS then removes it in the background, which can take longer.
| What | Kept for |
|---|---|
| Your HTML and files, your PDF, and working copies | Set to expire one to two days after they are stored (AWS counts to the next midnight UTC). AWS removes expired files in the background, so removal can take longer. |
| PDF download link | Works for up to 1 hour. |
| Render record and render report | The API stops returning it after 24 hours. AWS then removes it in the background, usually within a few days. |
| API request and service logs (including IP addresses) | 7 days. |
| Account record, API key hashes and usage records | Until your account is removed. |
| Plaintext key file on the operator's computer | Deleted after you confirm your first successful render, or 30 days after we send your key, whichever comes first. |
| Generated copy of your guide on the operator's computer | Deleted together with the key file: after you confirm your first render, or 30 days after we send your key, whichever comes first. |
| Sent onboarding email that contains your key | The sent copy and its attachments are deleted from our mailbox after you confirm your first render, or after 30 days, whichever comes first. |
| Access-request and support email | While your account exists and for 12 months afterwards; 12 months for requests that did not lead to an account. |
| Acceptance email and the record of version, date and account | While your account exists and for 3 years afterwards. |
| Backups of the operator's computer and mailbox | Routine backups of the operator's computer or of the mailbox may hold a copy that we have deleted until the backup is overwritten. We have not set a fixed period for this. |
The API's document storage has no backups, no versioning and no replication to another region. Copies that you download, and copies in email, are separate from that storage.
We may keep specific information longer when the law requires it, or while it is needed for an open investigation or dispute.
5. Your choices and requests
- Remove something sooner, or close your account. Write to hello@stolid.dev. We remove account records and stored documents by hand, and we delete the operator-held key copies listed above. Request logs are not removed individually; they expire after 7 days.
- See, correct or delete the personal information we hold about you: write to hello@stolid.dev.
- Replace a key. If a key may be exposed, write to security@stolid.dev. We revoke it and issue a new one.
- Stop email. We write to you about your access and your account. If we ever send news or offers, each message will say how to stop them.
We may need to confirm that a request really comes from you, usually by replying to the address on your account. We aim to answer within 30 days. We will not treat you differently for making a request. In some cases we must keep certain records, for example your acceptance email or records needed for a legal claim; we will tell you if that applies.
Depending on where you live, the law may give you further rights, such as the right to complain to a privacy regulator.
6. Where information is processed
Stolid is operated from the United States, and the API runs in an AWS region in the United States. If you contact us or use the preview from another country, your information is transferred to and processed in the United States, where privacy laws may differ from those where you live. Website pages may be delivered from an AWS location near you.
The preview is not offered for processing personal data under a data processing agreement, and we do not offer processing in the EU or UK. If you need either, please do not send personal data, and tell us what you need.
7. Security
The API accepts HTTPS only. Stored files and database records are encrypted at rest by AWS. Each document is rendered in a fresh browser session that is closed afterwards, on shared AWS infrastructure, and the page cannot reach the internet. API keys are stored as one-way hashes.
No service can promise perfect security. If we learn of a security incident that affects your information, we will tell you and follow the notification laws that apply. To report a weakness, write to security@stolid.dev.
8. Children
Stolid is a service for developers and businesses. It is not directed to children, and you must be at least 18 to use the preview. We do not knowingly collect personal information from children under 13. If you believe a child has sent us personal information, write to hello@stolid.dev and we will delete it.
9. Changes to this policy
We may update this policy. Each version carries a version label and an effective date. If a change is material, we will email account holders before it takes effect and note the change on this page.
10. Contact
- Andrei Okhotnikov, doing business as Stolid, Washington, USA
- Privacy and general questions: hello@stolid.dev
- Security reports: security@stolid.dev