Skip to content

Legal

Subprocessors.

This page lists the third parties that process data on DOGM's behalf: what each one does, which data it handles and where.

Last updated

1. Status#

The hosted service is live in the early-access beta, so these providers process customer data today. PayMongo runs in test mode, so no real payment passes through it yet. Where a region is not chosen yet, the table says so.

2. Current list#

Subprocessors, their purpose, the data involved and location
ProviderPurposeData involvedLocationStatus
WorkOSAuthentication and sign-in emailName, email, sign-in identifiersUnited StatesIn use
AnthropicAI spec draftingSchema metadata, prompts, and masked sample values when a project turns them onUnited StatesIn use
InngestWorkflow orchestration for runs and scheduled jobsJob identifiers and metadataUnited StatesIn use
CloudflareR2 artifact storage, DNS and network protection; Turnstile once the contact form arrivesGenerated artifacts, IP addresses, request detailsGlobal network; R2 region to be chosenIn use
ZeptoMailTransactional emailName, email, email contentTo be confirmedIn use
PayMongoQR Ph paymentsPlan, amount, payment referencePhilippinesIn use, test mode
Google CloudKey management (KMS) for encryption keysEncryption keys onlyRegion to be chosenIn use
SentryError monitoringError reports, which can include IP addresses and user IDsTo be confirmedIn use
Managed PostgreSQL hostApplication databaseAccount data, schema metadata, billing recordsSingapore; provider to be chosenIn use
Fly.io or RailwayAPI and worker hostingAll data the API processesTo be confirmedIn use
VercelWebsite and app hostingIP addresses, request detailsGlobal networkIn use

3. Changes to this list#

We will update this page before a new subprocessor starts processing personal data, and note the change in the changelog.

Questions: privacy@dogm.ai.