Security and data retention
The API stores no transactions. A statement is parsed and returned, and your system is the record.
What happens to a PDF you send#
It is read, parsed, and dropped when the response is written. It is never written to disk, put in storage or attached to an account.
What we keep#
| Kept | Why | For how long |
|---|---|---|
| A usage row per request: timestamp, status, error code, byte size, duration, issuer name, account count, row count, and the filename if you sent one. | Invoices are settled from it. | The life of the account. |
The response body behind an Idempotency-Key. | So a replay can be honoured instead of re-parsed and charged twice. | 24 hours, then deleted automatically. |
| A hash of each API key. | To authenticate you. The key itself is never stored. | Until the key is revoked. |
Idempotency replays#
A stored replay body is the only place the API holds transactions at rest. It is kept apart from the billing record and deletes itself after 24 hours.
Transport and access#
- TLS on every request. The endpoint is not reachable over plain HTTP.
- Keys are long random strings, stored hashed, and revocable by you at any time. See Authentication.
- Issuing a key and raising a cap are both recorded on our side.
- The person whose statement it is has no account here and is never contacted by us.
AI processing#
Reading a statement uses an AI model, and the statement's text is processed by our model provider to do it. Nothing else leaves our infrastructure, and the PDF does not. We train nothing on your documents. Email [email protected] if your compliance review needs the provider named and its data processing terms.
Deletion#
There is no transaction data to delete. Usage rows can be removed on request, though they are what an invoice is explained from. Email [email protected].