Files are encrypted per job, kept 48 hours for reprints, then shredded.
Long enough to fix a spoiled copy. Not long enough to become a liability. The Reamstead appliance also opens no inbound ports and dials out only, and it proves who it is with an X.509 certificate minted from a key its own hardware holds. Both are described on the appliance page.
AES-256-GCM per job · 48 h retention · append-only audit log

What happens to a customer's file, in order
A print job is a stranger's document sitting on your premises. These five steps are the whole of its life on our side, and the reviewer who has to sign this off can check each one against the system.
- 01
Encrypted on upload
The upload is stored under a random object key that is not derived from the job id, and encrypted with a data key generated for that job alone. The data key is itself wrapped by a platform key, so the stored object on its own is not a document.
AES-256-GCM · one data key per job
- 02
Sealed to one appliance
When the job is dispatched, the data key is sealed to the public key of the appliance that will print it. No other appliance can open it, the appliance never receives the platform key, and each download is recorded against the job.
Sealed per appliance · every access logged
- 03
Held for the reprint window
The file stays readable for 48 hours so a spoiled copy can be reprinted without asking the customer to send it again. The window is set for the platform and can be shortened for a reseller, a business or a single location.
48 h default
- 04
Crypto-shredded
When the window closes, a scheduled job destroys the wrapped keys and deletes the stored blobs, and tells the appliance to purge its local cache. Crypto-shredded means the key is gone: the remaining bytes cannot be turned back into a document, by us or by anyone who later obtains a copy of the storage.
Keys destroyed, not just files marked deleted
- 05
What is left afterwards
The job record, what it cost, how it was paid and the audit rows around it stay, because that is what a business reconciles against at the end of the month. The document itself does not.
Who can see what
Five kinds of person touch the system. Visibility is decided centrally rather than in each screen, so a role cannot see further than this table by finding a different page.
The five roles
- Platform admin
- Every tenantThe people who run the platform. Privileged actions require a fresh MFA check.
- Reseller admin
- Its own clientsA dealer sees the businesses it placed and nothing belonging to another dealer.
- Business owner
- One businessEvery location, printer, job and payment inside their own business, including billing.
- Location operator
- One locationWorks at the counter from a local console opened with a PIN: jobs, reprints, counter payments.
- Customer
- One jobA token that opens exactly the job it was issued for, and nothing beside it. There is no customer account to sign in to.
Checks that apply to all of them
- Privileged writes
- MFA within 10 minApproving an appliance, revoking a certificate, sending a command, starting a support session, changing a role.
- Filters in a request
- ANDed with your scopeNaming another business in a query narrows what you see. It can never widen it.
- Granting a role
- Never above your ownNobody can grant a permission they do not themselves hold, or reduce their own.
What we do not do
- Customer accounts
- NoneThe person at the QR sign never creates one.
- Mobile app
- NoneNothing is installed on anyone’s phone.
- Files past the window
- DeletedThere is no archive to ask us for afterwards, because there is nothing left to give.
- Shell on the appliance
- NoneThe remote command list is fixed and does not include running a command of your own.
- Certifications
- None heldWe tell you what the system does. We do not claim an audit scheme we have not been through.
Every row here is enforced in one place in the code and covered by a test that calls every listing route as the wrong tenant. A route added later is covered without anyone remembering to add a case for it.
The log can tell you whether it was edited
Jobs, payments, logins, role changes, appliance approvals, certificates, remote commands, updates, support sessions and branding changes are all written to one append-only table. The database itself rejects an update or a delete against it.
Hash-chained means each row is hashed together with the hash of the row before it, so altering any row breaks every hash after it and the break is arithmetic rather than a matter of opinion. A verify endpoint recomputes the whole chain and names the first row that no longer matches.
During a support session there is no impersonation: the supporter acts as themselves with a temporary grant, and every row written while the session is open carries its id.
audit_events (append only)
Edit event2 and h2 no longer matches, and neither does anything after it.
404
A business you may not see does not exist
Ask for another company's job, appliance or invoice and the answer is not found, rather than forbidden. Whether the thing exists is itself something we decline to disclose. A generated test calls every listing route as a user of the wrong business and fails the build if a single identifier leaks.
Tell us what you found in the queue
Security reports reach a person, not a form. Send us what you did and what you saw, and we will come back to you with what we have changed.
security · retention 48 h · audit chain verifiable