Data retention
What a request leaves on our servers, and for how long.
| What | Kept | Why, and how |
|---|---|---|
| A PDF, image or ZIP stored for a link | 24 hours | Or until you delete it: DELETE /v1/files/{id}. |
| The file in a response | not kept; with an Idempotency-Key, an hour | For a repeat of the key (the SDKs send one with every request they may retry): it gets the same file, nothing printed twice. |
| A job: its request, its result | 24 hours | The request until the job is done; the job and its result 24 hours from its creation. |
An Idempotency-Key's response | 24 hours | The response, and a digest of the body (not the body). |
| The source of a print | Pro, Max: not kept. Free: 30 days | A paid plan's prints leave nothing on our servers. A Free account's: the HTML and the options, without encryption passwords, attachments' bytes or an ICC profile, so that a print that went wrong can be reproduced; then deleted. |
| A print the engine could not make | Pro, Max: not kept. Free: 14 days | Its source, with the same left out, to find the engine's fault. |
| A line in the log of prints | with the account | For the plan's counting and support: when, the sizes of the document and the PDF, its paper, pages, how long it took and whether it succeeded. A Free account's line also names the address the request came from, the document's name and an error's message; a paid plan's does not. |
| The PDFs merged, split or compressed | not kept | Worked on in a folder of their own and removed when the response is written; only the result is kept, by link, as above. |
A page of url | not kept | Fetched for its print, then gone, as if it was sent as html (a Free account's source of a print keeps it, as above). |
Requests reach us through Cloudflare, which ends their TLS connection and passes them on to us. The documents are printed on our own servers and sent nowhere else: the engine fetches only what a document names itself (its images, stylesheets, fonts; allow_remote: false fetches nothing).
ReflowPDF is operated by INSEAW LLC, South Carolina, United States, and its servers are in the United States. Your rights, and what the editor keeps: the privacy policy.
@reflowpdf/engine prints where it runs: no document reaches us. It asks this API only for its license's token and, when a document names them, a print condition's profile and the faces of a catalogue family it has none of.