egressif.

Trust / Sub-processors

Who we rely on, and for what.

A sub-processor is a third party that processes data on our behalf to run the service or the business. Here is the current list, what each does, and where it processes data.

Data flow

Where your data goes.

YOUR DATA EGRESSIF United States INFRASTRUCTURE Google Cloud · PureVoltage FiberState UNITED STATES WEB FORMS Twilio SendGrid · Cloudflare UNITED STATES BUSINESS Stripe · Intuit QuickBooks Mercury UNITED STATES
Your data flows through Egressif to grouped sub-processors - infrastructure, web forms, and business - all processing in the United States.

Last updated 2026-06-22.

Sub-processor Purpose Data involved Processing region
Google Cloud Primary infrastructure: compute, storage, and networking for the platform. Delivery metadata, account data, hosted mailbox storage. United States
Google (Analytics / Tag Manager) Website analytics (GA4 / GTM) on egressif.io. Website usage data (not customer sending data). United States
Twilio SendGrid Delivery of website form notifications (contact and report-abuse forms). Form submissions you send us (name, email, message). United States
Cloudflare Bot protection on web forms (Turnstile) and edge/DNS where applicable. Form anti-abuse challenge data; request metadata. Global edge (US-administered)
PureVoltage Server hosting / colocation for parts of the sending infrastructure. Infrastructure hosting (delivery metadata in transit/at rest). United States
FiberState Server hosting / colocation for parts of the sending infrastructure. Infrastructure hosting (delivery metadata in transit/at rest). United States
Stripe Payment processing. Billing contact and payment details (held by Stripe). United States
Intuit QuickBooks Accounting and invoicing. Billing/invoice records. United States
Mercury Business banking. Payment/transaction records (held by Mercury). United States

How to read this

Scope and what stays out of it.

Egressif processes data in the United States. We hold minimal personal data: delivery metadata, account information, and (where you use hosted mailboxes) mailbox storage. We do not read message content and do not store message bodies for delivery. See data retention for how long each kind of data is kept.

Your routing choices can add sub-processors you control. If you keep an ESP in your routing as part of an overlay setup (for example SendGrid, Amazon SES, Postmark, or Mailgun), that provider becomes a sub-processor you have opted into, under your own agreement with them.

Payment, invoicing, and banking records are held by Stripe, Intuit QuickBooks, and Mercury under their own terms; we do not separately store card numbers. Each provider above maintains its own security program and sub-processors.

Need this as part of a vendor review, or want advance notice of changes to this list? Ask us and we will set that up. For requirements that exceed our standard posture, the custom-infrastructure path builds inside your own environment.

Need this for procurement?

Tell us what your vendor review needs. We answer plainly, and we will flag any change to this list.

Talk to our team