Subprocessors

Last updated: 2026-06-10

Docusift is built on a small set of subprocessors. The table below names each subprocessor, where it operates from, what we use it for, and what data they touch. Updates to this list are posted here and notified to subscribed customers in advance.

ProviderLocationPurposeData
Amazon Web Services (AWS)United States, IndiaCompute (EC2), managed database (RDS PostgreSQL), object storage (S3), KMS, CloudWatch.All customer data — documents, extracted JSON, audit logs, telemetry.
Microsoft Corporation (Azure AI Foundry)United States (East US region by default)Large-language-model inference (document classification, field extraction, OCR cross-check) via Azure AI Foundry. Microsoft is the sub-processor of record; underlying model deployments (currently GPT-5.2) run under the Microsoft Online Services Terms and the Microsoft Products and Services Data Protection Addendum.Document pages and prompts at inference time. Use is governed by the Azure Online Services DPA: customer data is not used to train the foundation model, is not shared with the model provider for their own purposes, and is processed only to return the inference response. Standard Contractual Clauses for EU/UK transfers are part of the Azure DPA where applicable.
Dodo PaymentsUnited States, IndiaMerchant of Record for all subscription sales. Dodo is the seller of record on customer invoices, collects card / UPI / wallet payments, and collects + remits applicable taxes (US sales tax, EU/UK VAT, India GST, and other jurisdictions Dodo supports) on Docusift’s behalf.Customer billing email, plan, transaction amounts, region. Card details are collected by Dodo directly; Docusift never sees the PAN.
SMTP relay (configurable per tenant)Varies by chosen providerTransactional email (verification, password reset, invitations).Recipient email address and message body.

How to subscribe to changes

Email hello@docusift.co with the subject line Subprocessor updates and we will add your billing contact to the announcement list.

For the underlying privacy commitments, see our Privacy Policy and Data Processing Addendum.