Subprocessors
Last updated 8 November 2026
Veydrum engages the infrastructure, zero-training AI inference, and billing subprocessors below to deliver GigaClerk. Each subprocessor is bound by written confidentiality, security, and data-protection obligations.
The short version
- Amazon Web Services hosts GigaClerk compute, PostgreSQL databases, encrypted S3 storage, KMS keys, and Cognito authentication in the United States.
- OpenAI processes bounded prompt context via zero-training commercial API endpoints.
- Stripe processes commercial billing and invoice metadata without receiving communication or calendar content.
This summary is for convenience. The full text below applies.
1Authorized Subprocessors
| Provider | Purpose | Data Scope | Region |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Container compute (ECS), pooled RLS & Private Tenant PostgreSQL databases (RDS), versioned encrypted blob storage (S3), envelope key management (KMS), and OIDC authentication (Cognito). | Encrypted workspace records, blobs, OAuth envelopes, and authentication metadata. | United States (us-west-2; Cognito us-east-1) |
| OpenAI, L.L.C. | Commercial API language model inference for message triage, briefing synthesis, and operator-requested reply drafts under zero-model-training API terms. | Bounded prompt context required for active workspace tasks; never used to train generalized models. | United States |
| Stripe, Inc. | Commercial pilot invoicing, payment processing, and subscription billing records. | Billing contact name, email address, invoice metadata, and payment tokens (never inbox or calendar content). | United States |
2Subprocessor Updates & Inquiries
We update this page before authorizing any additional subprocessor to process Customer Data, and notify commercial workspace owners in advance of material subprocessor changes. Questions regarding subprocessors, security controls, or Private Tenant deployments may be sent to privacy@gigaclerk.com.