Sub-processors
The services EsignCenter is built on, what each one is for, and what reaches it.
Sub-processors
| Service | Purpose | What it receives |
|---|---|---|
| Render | PurposeHosting: the application, background jobs and the PostgreSQL database | What it receivesEverything the application stores, in a US region |
| Amazon Web Services (S3) | PurposeFile storage: uploaded and signed PDFs, images and account exports | What it receivesYour document files, in a US region |
| Postmark (an ActiveCampaign company) | PurposeEmail delivery: signing invitations, reminders, receipts and account notices | What it receivesRecipient email addresses, the message and delivery events (delivered, bounced, complained) |
| Stripe | PurposePayments: the paid plan, trial and invoices | What it receivesYour name, email address and card, entered on Stripe's own pages; card numbers never touch EsignCenter |
| Sentry | PurposeError monitoring, so a failure is fixed before you have to report it | What it receivesTechnical details of a failure, which can include parts of the request that caused it |
| Cloudflare Turnstile | PurposeA bot check on the sign-up and support forms | What it receivesYour network address and the browser signals the check needs, when you use one of those forms |
| PurposeOptional sign-in with a Google account | What it receivesYour Google email address and name, only if you choose to sign in with Google | |
| Apple | PurposeOptional sign-in with an Apple ID | What it receivesYour Apple ID email address, or a private relay address from Apple that forwards to it, and your name, only if you choose to sign in with Apple |
| DigiCert | PurposeTrusted timestamp authority for every signed PDF | What it receivesA hash of the signature, never the document |
The formal list is in the Privacy Policy. Questions go to support@aceddev.com.