# What happens to the documents you send

This page says, in plain words, where your documents go, who can see them and how long they are kept. The public preview is for sample data; the [Privacy Policy](https://stolid.dev/legal/privacy/) covers your account, email and the website.

## The short version

- **Processing.** Stolid uses Amazon Web Services (AWS) to render and store the documents you send to the API. We do not send API document contents to another rendering provider, and we run no analytics on them. Your documents are used to make your PDF and its render report, to help you when you ask, and, if it is ever needed, to investigate a specific security or abuse report or comply with the law.
- **Deletion.** Files and PDFs are set to expire one to two days after they are stored (AWS counts to the next midnight UTC), and render records after 24 hours; AWS then removes them in the background, usually within a few days. Your account, API key hash and usage counts stay until your account is removed. Want something gone sooner? Write to hello@stolid.dev and we do it by hand. Request logs expire after 7 days.
- **Access.** Routine human access by Stolid is limited to the operator when you request troubleshooting. Limited access or disclosure may also be necessary to investigate a specific security or abuse report or to comply with the law. 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. Your files are stored privately and are not public. Anyone who holds a download link can use it until it expires.
- **Location.** API documents are rendered and stored in one AWS region, US East (N. Virginia), `us-east-1`. The API is HTTPS only, and stored files are encrypted at rest. Email and website delivery are handled separately, as described in the [Privacy Policy](https://stolid.dev/legal/privacy/).

## Use sample data while you try the preview

Your real templates are welcome. Fill them with made-up names and amounts, and keep real customer details, personal data and secrets out of the preview. This is part of the [Preview Terms](https://stolid.dev/legal/terms/). Sent something by mistake? Write to hello@stolid.dev and we remove it.

## What we keep, where, and for how long

Files, PDFs and render records are set to expire automatically. We keep your account, API key hash and usage counts until your account is removed.

| What | Where | How long |
| --- | --- | --- |
| Your HTML and files (`assets`) | Private AWS storage (S3), encrypted | 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. |
| Your PDF | The same storage | The same, including temporary working copies and a copy of the render report. The download link works for up to 1 hour. |
| The render record: status, any error, page count, a fingerprint of your request, your `Idempotency-Key`, and for a successful render the render report and its options | AWS database (DynamoDB), encrypted | The API stops returning it after 24 hours. AWS then removes it in the background, usually within a few days. |
| Your API key | The API database stores a one-way hash. During onboarding, your key also appears in the guide emailed to you and in restricted operator copies. | The hash: until your account is removed or the key is replaced. Operator copies: see the [Privacy Policy](https://stolid.dev/legal/privacy/). Copies you hold are yours to manage. |
| Account and usage counts | The database | Until your account is removed. |
| Request logs: timings, status codes, error types and the IP address of each request, not the content of your documents | AWS CloudWatch | 7 days |
| Email with us | Our email provider (Fastmail) | Kept separately from API documents. See the [Privacy Policy](https://stolid.dev/legal/privacy/). |

The render report can quote short snippets of your document, such as the first 60 characters of the text next to a font or overflow warning. The API's document storage has no backups, versioning or replication. Copies you download, and anything you email to us, are separate.

## How a document is rendered

- **A fresh browser session.** Your page is rendered in a fresh browser session that is closed afterwards. The service runs on shared AWS infrastructure.
- **No internet from the page.** Loading remote files is not available during the public preview. Send the files your page needs with the request.
- **Private download links.** The download link in an answer works for up to an hour. Anyone who holds it can use it until it expires, so treat it like a password.

## Controls for keys and agents

- A monthly allowance per account and mode: live and test usage are counted separately. `GET /v1/usage` shows the allowance for the mode of the key you use.
- A separate test allowance: test calls are counted apart from live calls. Build and test your integration with sample data without using your live allowance.
- Spending caps per key (coming soon): each key will be able to carry its own cap.
- Untrusted-content labelling (coming soon): labels will help agents distinguish document text from instructions.

## Questions

Ask us anything about your data: hello@stolid.dev. A person replies. The [Preview Terms](https://stolid.dev/legal/terms/) and [Privacy Policy](https://stolid.dev/legal/privacy/) are the written versions; if your team needs something they do not cover, tell us.

[Preview Terms](https://stolid.dev/legal/terms/) · [Acceptable use](https://stolid.dev/legal/terms/#acceptable-use) · [Privacy Policy](https://stolid.dev/legal/privacy/) · [Data handling](https://stolid.dev/data/) · Report abuse or copyright infringement: hello@stolid.dev

© 2026 Stolid · Operated by an individual in Washington, USA

Source: https://stolid.dev/data/
