Sub-processors
Last updated: September 29, 2026
This page is the authoritative, dated record of who Digitload engages to help process personal data on behalf of Customers, referenced by the DPA and Privacy Policy §5. When we add or replace a sub-processor, we update the table below and its "Since" date rather than only editing the Privacy Policy's summary — so a change here is always visible as a dated addition, not a silent edit.
Sub-processors engaged by Digitload
These are third parties Digitload itself engages to provide the Services. Each is bound to data protection terms at least as protective as our own DPA.
| Sub-processor | Purpose | Data involved | Location | Since |
|---|---|---|---|---|
| Google Cloud Platform / Firebase (Google LLC) | Hosting, database (Firestore), authentication, file storage | All Account and Content data | United States | July 25, 2026 |
| Amazon Web Services, Inc. (SES / S3 / SNS) | Sending emails on behalf of Customers who verify their own domain, and receiving inbound mail for Customers who enable it | Sender/recipient email addresses, message content and attachments | United States | July 25, 2026 |
| Cloudflare, Inc. | Content delivery, DNS, security, and TLS for mailinapp.com and for the custom tracking and portal domains Customers connect; serving the images, calendar files, and charts embedded in emails at the network edge | Request data from every visit to the Services and from Recipients opening or clicking emails: IP address, user agent, and requested URL (which can carry a signed token linking the request to a Recipient) | United States, and globally across Cloudflare's network | July 31, 2026 |
| Google LLC (Gemini API) | Generating optional AI subject-line/copy suggestions | Customer's own project copy excerpt (opt-in feature only) | United States | July 25, 2026 |
| Functional Software, Inc. (Sentry) | Crash and performance diagnostics for the MailInApp mobile app | Device/OS metadata and in-app error traces; no default PII beyond that | United States | August 28, 2026 |
| Branch Metrics, Inc. (Branch.io) | Deep-link routing and install attribution for the MailInApp mobile app | Device and install identifiers | United States | August 28, 2026 |
| Watch-IP (Digitload Inc., running on Cloudflare, Inc. infrastructure) | Checking contact email addresses when contacts are added or a list is re-checked: format, whether the domain can receive mail, and disposable, role (info@, sales@) or likely-mistyped addresses | Contact email addresses, used only for the duration of each check and not stored by Watch-IP | Canada, United States, and other countries where Cloudflare operates | September 29, 2026 |
Watch-IP is an email and IP checking service that Digitload also operates. It's listed here so this page shows every service that receives personal data, even though it isn't a separate company. It never contacts a Recipient's mailbox or mail server.
Third parties you or your Recipients engage directly
These aren't Digitload's own sub-processors — they're services you or your Recipients connect directly, under your own account with that provider. We note them here for transparency since the Services integrate with them, but Digitload isn't a party to that relationship.
| Service | Who engages it | Purpose |
|---|---|---|
| Stripe, Inc. | You, via your own Stripe Connect account | Processing payments for products you sell through the checkout feature — Stripe holds the payment/card data, not Digitload |
| Google OAuth / Gmail API, or another IMAP/SMTP email provider (Outlook, Yahoo, etc.) | You or a Recipient, at their own initiative | Powering the optional Mailbox/native-inbox reading and sending experience |
| Shopify, Inc. or WooCommerce (Automattic Inc.) | You, by connecting your own store | Syncing your store's customers, abandoned checkouts, and paid orders into your MailInApp contacts list; Shopify also calls our mandatory compliance webhooks directly to request or redact a customer's synced data |
| Anthropic (Claude), OpenAI (ChatGPT), or Google (Gemini) | You, by connecting an AI assistant under Connections in your dashboard | Whatever project, contact, campaign-results, mailbox or ticket data the permissions you grant allow that assistant to read, transmitted to the provider you chose to power your own chat session — governed by that provider's own terms, not Digitload's |
Changes
Adding or replacing a sub-processor updates this page with a new "Since" date; removing one is likewise reflected here. For a material change, we'll also notify Customers by email or an in-app notice per Terms of Service §20, giving a reasonable opportunity to object per DPA §4 before the change takes effect.
Questions about this list: [email protected].