Data security & protection

1. Choose your processing path

The free browser tools render PDFs on your device. Saving a template or branding uploads that saved content to your account. API and MCP generation send the supplied certificate data to our servers. Background jobs retain inputs and temporary outputs so generation can finish independently of the initiating request. Public verification is an explicit publication step. Saving contacts uploads names and email addresses to your account. Optional email delivery uploads generated PDFs for temporary delivery through Brevo; it does not occur automatically when you generate a PDF.

2. Account and integration access

Workspace endpoints require an authenticated account and restrict records to the relevant account. Administrative routes have additional authorization checks. API and MCP clients use bearer keys with selectable scopes, expiration and revocation. Treat a bot’s access as access to the permissions granted to its key.

Key verification uses a hash. Keys eligible for repeat copying also have encrypted recoverable material protected by a server-side secret; this is not end-to-end encryption. Revocation disables use and removes that recoverable key material. A connection challenge checks possession of the selected key; a client-supplied bot name is not independently verified identity.

3. Application safeguards

The application validates request bodies, constrains upload and batch sizes, enforces API quotas and concurrency limits, and checks authorization for job status and downloads. Private API responses use cache restrictions where appropriate. Public certificate records are intentionally accessible by their verification URL.

Hosted access uses HTTPS. Database connectivity uses the provider’s protected connection facilities. Infrastructure encryption, backup and access practices depend in part on our providers. We do not claim that every provider log excludes certificate data or that no privileged operator access is possible.

4. Hosting and file lifecycle

Vercel hosts the application and workflows; Neon hosts the database and authentication. Configured server compute and database are in Singapore. Global content delivery and provider operations may involve other regions. There is currently no EU-only residency option.

Direct render responses deliver output immediately. Background downloads are authenticated and expire after one hour; expired outputs and old jobs are cleaned by the application’s cleanup routine. Expiry, deletion from active storage and removal from infrastructure backups are different events. See the privacy policy for retention limitations.

5. Assurance and shared responsibility

We do not currently claim Certinator SOC 2 or ISO 27001 certification, an independent penetration-test report, 24/7 staffed incident response, or a guaranteed recovery time. A provider’s certification is not a certification of this application.

Use the minimum necessary recipient data, protect account access and keys, review certificate content, and keep your own output copies. Customer bot platforms may retain payloads and logs under their own policies. Review those platforms before connecting them.

6. Report a concern

Email support@certinator.com with the affected URL, a concise description, impact and safe reproduction steps. Do not send live keys, passwords, full recipient lists or other customers’ data. Test only accounts and resources you are authorized to use; avoid disrupting service. We will assess reported issues, but this page does not promise a bounty or a fixed response window.