Security
Security
Each statement below is marked Built when the code or configuration exists, orDesigned when it is decided and described but not built yet.
Where data is stored
Built Receipt content and job records are stored in AWS eu-west-1 (Ireland) and are encrypted at rest. The services involved are listed on the sub-processors page.
Restricted API keys
Built Every API key is restricted. When you create a key you choose what it may do, resource by resource, as scopes such as jobs:write, jobs:read orprinters:read. A key made for printing cannot read your customers, and a key made for monitoring cannot print. Only a hash of each key is stored, and the key is shown once, when you create it.
A printer URL is a secret
Built Each printer has its own URL, and the last part of it is secret. One printer's URL gives access to that printer only. Only a hash of the secret is stored.
Built A printer's URL is issued in the dashboard and shown once.
How long data is kept
Built Receipt content is deleted when a job is printed, failed, cancelled or expired. Job records without content are kept 7 days after the job's final state. Receipt content is never written to logs.
Designed Receipt content will be deleted at most 7 days after a job was queued, plus up to an hour while the printer's confirmation is awaited, whatever the job's state. Monthly usage records will be kept 7 years, because they back the invoices.
This website
This website sets no cookies and loads no script, font or image from another site. It counts visits with PostHog, in its EU Cloud: the page you open, the page you came from and a click on Sign up or Sign in, with nothing stored on your device. The library is part of this website, and the counts go to PostHog's server in the EU and nowhere else. If you change the theme or, on the blog, pick a code language or a product, your choice is kept in your browser's local storage, on your device only. It is never sent to us. The privacy notice says what is counted.
What we do not claim
We hold no security certification and do not claim one. No independent security review or penetration test has been done. If that changes, this page will say which and since when.
Report a problem
Write to contact@tillcast.com. The details are in security.txt.