Built on cryptographic signing
Every signed PDF is sealed with PAdES, a tamper-evident digital signature standard. Change one byte of a signed PDF and a standard PDF reader shows the seal is broken.
9 · Governing law
This Agreement is governed by the laws of the State of California, without regard to its conflict-of-laws rules. It may be executed electronically and in counterparts, each deemed an original.
10 · Signatures
- Seal certificateAppliFlo, not public
- Signing keyKMS HSM, Sydney
- nda-northwind.pdfPAdES
- Audit trail+ certificate
- PAdES sealing on Cloud KMS
- AES-256 at rest, TLS in transit
- Tenant-isolated workspaces
- Audit trail with IP address
Change one byte, the seal breaks
PAdES embeds a cryptographic signature in the PDF, bound to its contents. If the document is altered after signing, the seal breaks, and a standard PDF reader shows that it was changed.
The certificate is issued by AppliFlo rather than a public certificate authority, so some PDF readers may show it as “validity unknown”. That does not by itself affect whether the signature is legally effective, but consider it for documents that need a publicly trusted signature (see Terms, section 5).
The signing key is held in a hardware security module in Google Cloud KMS, Sydney, and never leaves it. Our application servers pass the PDF through for signing but never hold the private key. A certificate of completion and the audit trail ship with every signed PDF.
Example bytes and digests, shortened.
Encrypted at rest and in transit
Your documents and data are stored in Australia (Google Cloud, Sydney region), since 12 November 2026. They are encrypted at rest by Google Cloud with AES-256, and in transit with TLS.
The sensitive details you keep as saved Fill as me details (passport, date of birth, tax and bank details) are also encrypted again in the application, with a key of their own. Other data, including client records and uploaded documents, relies on Google Cloud’s encryption at rest. CRM connector credentials are kept in Google Secret Manager, not in our database.
- Name
- Priya Sharma AES-256
- priya@example.com AES-256
- Passport
- N1234542 AES-256 + app key
- Date of birth
- 14/03/1994 AES-256 + app key
- Tax number
- 123 456 782 AES-256 + app key
- Bank account
- 062-000 1234 5678 AES-256 + app key
One request, one workspace
Every request, from the dashboard or an API key, is resolved to a single workspace before it touches a document. One workspace can never read another’s files, fields or envelopes.
Authorization: Bearer aflo_live_…3c
- lease-2026.pdf
- env_8f2 · 2 signers
- fields: 14
Example workspaces with made-up names.
Who, when, from where
Each envelope carries an audit trail: who acted, when, and from which IP address. It ships with the certificate of completion.
Example rows. Documentation IP ranges, made-up names.
Keys shown once
API keys are shown once, in full, at creation. From then on we store only a SHA-256 hash: a lost key can be revoked and reissued, never recovered.
- Per key
- 120 requests / min
- Shared pool
- 20 / min across detect, fill, send
Example key and hash.
What AI sees, feature by feature
To find a document’s fields, AppliFlo sends the whole uploaded document to Microsoft Azure Document Intelligence (Australia) and its text and layout to Google Vertex AI Gemini (United States). A workspace owner can turn this off with “Read documents with AI” in Settings. Drafting in Docs sends your prompt and the document text to Anthropic (United States).
Only AppliFlo for Chrome and AI assign work from field labels, without sending your values. We do not use your data to train AI models, and our agreements with AI providers prohibit it.
What each feature sends, and how long providers keep it: AI Terms and Sub-processors.
Chrome: sent to AI
- Family name
- Date of birth
- Passport number
- Upload: passport scan
Chrome: never sent to AI
- SHARMA
- 14/03/1994
- N1234542
- passport.pdf
AppliFlo for Chrome only. Example values. Documents you upload to AppliFlo are read by AI in full.
Compliance, stated plainly
AppliFlo is designed to support ESIGN/UETA electronic-signature workflows. Whether a signature is valid depends on the document and the law where it is used. We do not claim certifications we do not hold; as formal programs progress, we will state their status plainly here.
Sub-processors and status
The companies that process data for us, what each receives and where, are listed on our Sub-processors page. We do not publish a status page yet. For a security review, contact us.
