Security
How Emboss handles the documents you send it, and what to do if you find a problem.
How documents are handled
- In transit, every request and response is encrypted with TLS.
- At rest, documents sit on the object store described on the subprocessors page.
- Model calls (field detection, context fills) go through the model providers described on the subprocessors page.
- API keys are stored hashed, never in plain text.
Ephemeral processing
Ephemeral processing: source and output documents are deleted 60 to 70 minutes after the last activity on a form.
Deleted:
- the uploaded form, the fillable copy and the thumbnail
- the supporting documents
- every filled output and batch output
- the session's values, the proposal's evidence and the receipt's values
Kept:
- the blank form's layout (field names, positions and types; nothing about the person)
- the execution receipt's skeleton: what happened and when, file hashes and sizes, no values
- payment records and usage records
- security logs
The pay-per-job door is always ephemeral; account holders switch it on per request or for the whole account. See the pay-per-call guide for how the pay door works.
Reporting a vulnerability
Email contact@getemboss.ai and we will reply within five business days. See our security.txt for the machine-readable version of this contact.