Legal
Authmarks Subprocessors
Last updated: 29 October 2026
This page lists third-party subprocessors used to operate Authmarks. All subprocessors are engaged under written agreements that include confidentiality and security controls. Enterprise customers with a signed DPA receive advance notice (typically 30 days) for new subprocessors that will process personal data on their behalf.
We do not currently use a separate marketing-analytics or transactional-email subprocessor for the public site. If that changes, this list will be updated before or promptly after the change takes effect.
Current subprocessors
| Provider | Service | Purpose | Data categories | Region |
|---|---|---|---|---|
| Auth0 (Okta, Inc.) — migration window only | Legacy identity provider | Lets existing accounts sign in once more so they can be moved to the self-hosted Authmarks identity service (Keycloak on our EU-hosted VM). Removed when the migration window closes. | Account identity data (email, name), authentication tokens, and login metadata of accounts created before the migration. | EU tenant by default (Frankfurt / EU-central); US failover only under enterprise contract. |
| Hostinger International Ltd. | Cloud infrastructure hosting | Primary application, database, and storage hosting for the sealed evidence pipeline. | Application data, sealed manifests, session telemetry, service logs, and infrastructure metadata. | European Union data center. |
| Cloudflare, Inc. — planned, not yet active | DNS, edge proxy, WAF, and DDoS protection (planned) | Planned traffic routing, TLS termination at the edge, WAF policies, and availability protection. Not currently processing any customer traffic; this row will be updated when the service is activated. | Once active: network metadata (IP address, request headers, TLS handshake); no document body content. | Global edge network. Requests from the EEA are routed to EU points of presence where technically possible. |
| Google LLC (user-enabled APIs only) | Google Docs / Drive API access | Read/write access to documents and Drive metadata for features you explicitly enable. | Scoped OAuth tokens plus document / Drive data returned by the specific scopes granted. | Google-operated regions; determined by the user's own Google account settings. |
Questions
Contact sales@authmarks.com. See also the Privacy Policy.