Trust Center
Sub-processors
The third-party services that may process customer personal data on SendTax’s behalf.
Fly.io
Application hosting + managed Postgres/Redis

Cloudflare
Document storage (envelope-encrypted); DNS and proxy for send.tax

Google Cloud KMS
Key custody for envelope encryption

Clerk
Authentication + identity
Vercel
Hosts send.tax: sign-up, sign-in and onboarding pages
Resend
Transactional email
Google Workspace
Company email for send.tax addresses
Sentry
Error monitoring (scrubbed)
PostHog
Product analytics: page views and milestone events, no session recording

Modal
Cloud ML inference for document classification
This page lists the third-party services that process customer personal data on SendTax's behalf, and the services built into SendTax that are not yet switched on. It is our list of record. We maintain it under the Vendor Management Policy, which governs how these sub-processors are selected, monitored, and removed.
All sub-processors below are U.S. companies serving SendTax's U.S. operations. The Region column says where each one processes customer data. Our Privacy Policy says client documents are stored and processed in the United States. Where a Region cell says "to be confirmed", we have not yet confirmed that the vendor keeps that data in the United States. A connection from outside the United States first reaches the Cloudflare or Fly.io location nearest the person, which passes it on to our U.S. servers over an encrypted connection; nothing is stored there.
Tier 1 sub-processors
These vendors may process identifiable customer personal data in the ordinary course of delivering SendTax's services.
| Vendor | Service to SendTax | Personal data processed | Region |
|---|---|---|---|
| Fly.io Security | Application hosting, managed PostgreSQL, managed Redis (the Redis is operated for Fly.io by Upstash, reached only over Fly's private network) | All customer data stored or processed by SendTax (tax-return data, identity documents, profile, audit logs); the job queue and realtime events pass through the Redis. Document files themselves are stored in Cloudflare R2 (next row), not on Fly.io. | iad (US East — Ashburn, Virginia) |
| Cloudflare Security | Object storage (R2) for customer documents and ML models; DNS, and the proxy and TLS certificate in front of the send.tax website; Turnstile, the bot check on sign-up | Customer document files. Each uploaded file is encrypted by SendTax using AES-256-GCM envelope encryption as soon as it arrives, before processing (Encryption Policy § 7.1); R2 additionally encrypts at rest at the storage layer. For the send.tax website, the visitor data described in the Vercel row below passes through Cloudflare on its way to Vercel, and Turnstile sees the visitor's address and browser signals when they sign up. | R2: United States (a bucket created with Cloudflare's us jurisdiction). Website and Turnstile: the Cloudflare location nearest the visitor |
| Google Cloud KMS Security | Key custody for document envelope encryption (KEK) | Cryptographic key material only. KMS never sees plaintext customer data. Our provisioning sets SendTax's servers to authenticate to KMS with Workload Identity Federation, which uses no long-lived service-account key; we have not yet confirmed that production runs in that mode. | us-east1 |
| Clerk Security | Identity provider and authentication | Authentication identifiers (email, name), password material (handled inside Clerk, never seen by SendTax), sign-in event history, and two-step verification settings once it is available (it isn't yet; it switches on for pilot firms in December). Environment-segmented (Clerk-Dev / Clerk-Staging / Clerk-Production). | United States (the vendor's published documentation; to be confirmed in writing at the annual review) |
| Vercel Security | Hosting for the send.tax website, including the sign-up, sign-in and onboarding pages | IP addresses, browser details and pages requested by visitors, and the sign-in session cookie checked when a signed-in customer opens a page. What customers type during sign-up and onboarding goes from the browser to Clerk and to SendTax's API on Fly.io, not through Vercel. | To be confirmed |
| Resend Security | Transactional email | Email addresses and email content for messages SendTax sends to customers (account email, incident notifications, document-related correspondence). Receiving email from customers (forwarding documents to SendTax by email) is built but not switched on. When it is, Resend will also hold the messages and attachments customers send, and we will give notice first (see "Changes to this list"). | United States (the vendor's published documentation; to be confirmed in writing at the annual review) |
| Google Workspace Security | Company email for send.tax addresses | Messages customers send to SendTax addresses such as [email protected] and [email protected], any attachments, and our replies. | To be confirmed |
| Sentry Security | Error monitoring | Application error context. SendTax scrubs known sensitive fields before transmission; payloads may contain opaque internal identifiers and request metadata, and events from the browser carry the visitor's address and the page's address. | United States (our organization's data region; to be confirmed in writing at the annual review) |
| PostHog Security | Product analytics | Product-usage events. Configured to PostHog's U.S. cloud (us.i.posthog.com). Autocapture is off: PostHog receives page views, page-leave events and named milestone events only, with the visitor's address. Session recording is not enabled. When someone signs in on send.tax, we send PostHog their account id and link their events to it (their email address too, until the version of this page approved after 2026-10-26). No document content, SSNs or return values are captured in events. | United States (us.i.posthog.com) |
| Modal Security | Cloud machine-learning inference for document classification | Document image content while a classification job is running. Returns label predictions; does not persist customer document content beyond the inference window. If Modal is unavailable, the document is not sent anywhere else: SendTax guesses its type from the file name and marks it for review. | United States (pinned to Modal's U.S. regions in our code; Modal runs pinned functions only there) |
Vendor security documentation
Each vendor row above links directly to that vendor's canonical trust or security page, where you can review its security program, certifications, and the terms of its Data Processing Agreement (DPA).
On DPAs: SendTax has not yet executed signed DPAs with each Tier 1 sub-processor. Until we do, we rely on each vendor's standard terms, including any data-processing terms they incorporate; we will execute named DPAs when a customer's contract requires them. Customers who need a signed DPA chain in place before onboarding can contact [email protected].
Built but not switched on
These services are built into SendTax but switched off, and they receive no customer data today. Before we switch one on, we move it into the table above and give the notice described under "Changes to this list".
| Vendor | Service to SendTax | Personal data it would process | Region |
|---|---|---|---|
| Stripe Identity Trust | Identity verification: government photo ID and selfie checks for filers and tax preparers | Government-issued photo ID images, selfie images, and the name and date of birth read from them. SendTax would delete its copies 90 days after a verification completes and ask Stripe to redact its own copies, which Stripe may take up to 4 days to finish (Data Retention and Deletion Policy § 3.3). That deletion job is built and runs only in dry-run mode so far. | To be confirmed before use |
| Stripe Security | Payment processing for firm subscriptions | Firm name, billing email and usage counts, and the payment details a firm enters on Stripe's hosted checkout page. SendTax never sees full card numbers. | To be confirmed before use |
Cloud-folder delivery, which copies a firm's processed documents to the firm's own Dropbox or Google Drive, is also built and switched off. Before we switch it on, we will decide whether that storage is a SendTax sub-processor and update this page. If it is, the notice under "Changes to this list" applies.
Other vendors (not sub-processors)
The following vendors are used by SendTax operators but do not, in normal operation, process customer personal data. They are listed for transparency.
| Vendor | Use |
|---|---|
| GitHub | Source-code hosting and automated builds and tests. Customer personal data is never deliberately written to source control. |
| 1Password | Operator credential storage. Used only by SendTax staff to access tooling; does not store customer personal data. |
| Fly.io Secrets | Encrypted runtime secret storage on the same Fly.io account as the application; covered by Fly.io's data terms in the Tier 1 row above. |
| Tailscale | The private network that is the only way to our training computer; it carries traffic encrypted end to end and holds no customer personal data. |
| Anthropic (Claude) | Our source code, for development and the automated security review, on each member's own subscription with model training off; never customer personal data. |
| OpenAI | Our document-labeling tools' auto-label routes, used only on public samples and our own documents; never a customer's document or a training contribution. |
| Notion | Mirrors of these policy pages and internal coordination; no customer personal data. |
| Google Fonts | Our web fonts. A visitor's browser fetches them from Google, which sees the visitor's address and browser details; no customer personal data. Serving the fonts from our own hosts is planned. |
Changes to this list
When we add or replace a Tier 1 sub-processor, or one starts handling a new category of customer data (including when we switch on a service listed under "Built but not switched on"), we update this page and notify customers at least 30 days before the sub-processor receives that data. When we stop using a sub-processor, we update this page and tell customers in advance. Each change is recorded in the Change history at the end of this page. Vendor Management Policy § 10 describes how we notify customers.
Two exceptions, both for emergencies:
- If we must stop using a sub-processor at once, to protect customer data or because the vendor stops providing its service, we stop immediately and tell customers as soon as we can.
- If we must then replace it sooner than 30 days, the notice may be shorter. It still comes before the new sub-processor receives customer data, and it says why it is short.
Objecting to a new sub-processor
Customers who object to a new sub-processor may contact SendTax at [email protected]. We will work with the customer to identify a mutually acceptable path; if no acceptable path is available, the customer may terminate their use of the affected service.
Contact
| Sub-processor questions and objections | [email protected] |
| Security disclosures | [email protected] |
| General | [email protected] |
| Operating entity | Howell & Gibbs LLC |
Change history
| Version | Date | Author | Approved by | Changes |
|---|---|---|---|---|
| 1.0 | 2026-05-30 | Holly Gibbs | Not recorded | First version. Drafted with Claude. |
| 1.1 | 2026-06-03 | Liam Howell | Not recorded | Added Stripe Identity (identity verification for filers and tax preparers). Drafted with Claude. |
| 1.2 | 2026-09-24 | Liam Howell | Not recorded | Modal row: Modal's classification containers are now pinned to U.S. regions, and the Region column says so. Removed the sentence saying classification falls back to a local ONNX model when Modal is unavailable, which was wrong. If Modal is unavailable, the document is not sent anywhere else: SendTax guesses its type from the file name and marks it for review. Removed the "Proposed additions" section (Dropbox and Google Drive, for optional cloud-folder delivery). The feature is not switched on, and we are still settling whether a storage account a firm connects is a SendTax sub-processor or the firm's own vendor. Corrected the Fly.io and Cloudflare R2 rows: documents are encrypted as soon as they arrive in R2, not before upload. No vendor added or removed, and no new data categories. Drafted with Claude. |
| 1.3 | 2026-10-07 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | One version number and one change history for this document (WISP § 7.4; public WISP § 14). It had no version numbers before: 1.0 to 1.2 are numbered now and dated the day each was approved (merged). Their dates were wrong: the first version said 2026-05-21 (now 2026-05-30), Stripe Identity 2026-05-29 (now 2026-06-03), and two rows said 2026-10-01, a planned release day (now one row, 2026-09-24). Also records a change made without a row: #369 (2026-09-22) added a "Proposed additions" section, which 1.2 removed before it was ever published. Header: version, effective date, maintainer and review cadence (at least annually, and after any material change; none was stated before); the "Last updated" line is gone, and the Change history is now the last section. Corrected: Vercel, which hosts send.tax including the sign-up, sign-in and onboarding pages, and Google Workspace, which receives email sent to send.tax addresses, were in use but missing from the list, and so were the DNS, proxy and TLS certificate Cloudflare provides in front of the send.tax website. Corrected: PostHog receives page views and page-leave events as well as named milestone events, and its events are not pseudonymized: at sign-in on send.tax we send PostHog the person's account id and email address and link their events to that id (the page said no personally identifiable information was captured). Corrected: provisioning sets Google Cloud KMS sign-in to Workload Identity Federation, but the mode production runs in is not yet confirmed (the page said production uses it). Corrected: Stripe Identity was listed as in use from 2026-06-28 after 30 days' notice; no notice is on record, and it is not switched on. It moves to a new "Built but not switched on" section, which also lists Stripe payments and cloud-folder delivery (neither listed before), and its retention link now points to Data Retention and Deletion Policy § 3.3. Corrected: Resend does not yet receive email from customers; Clerk's row no longer implies MFA is in use (it is not available yet); the GitHub row no longer claims secret scanning on every commit, which we could not confirm; the DPA note no longer says each vendor's DPA terms apply by default, which we had not checked for each vendor. The introduction no longer says every sub-processor processes data in the United States; it says each is a U.S. company, and the Region column says where data is processed. The Cloudflare R2 region us-east-1 was a setting in our storage software, not the bucket's location, which is not yet confirmed. Changes to this list: at least 30 days' notice before a new or replacement sub-processor, or a new category of customer data, takes effect (it said "in advance where commercially reasonable"); a sub-processor we stop using is announced in advance, with exceptions for emergencies; notice follows Vendor Management Policy § 10 (it named the incident-notification fan-out, which serves incidents only). "Internal-only tools" is now "Other vendors". Listing Vercel, Google Workspace and Cloudflare's website proxy corrects the page: they were already in use, so it adds no sub-processor and starts no 30-day notice. Drafted with Claude. |
| 1.4 | 2026-10-07 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | Clarified, DPA note: we will execute named DPAs when a customer's contract requires them (it said as we move toward enterprise contracts and SOC 2 attestation). Drafted with Claude. |
| 1.5 | 2026-10-22 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | Security statements, the Qualified Individual's decision of 2026-10-21. The opening says the Privacy Policy states that client documents are stored and processed in the United States (it said the Privacy Policy says we store and process data in the United States), and that a connection from outside the United States first reaches the Cloudflare or Fly.io location nearest the person, which passes it on to our U.S. servers over an encrypted connection, with nothing stored there. This narrows a commitment, so it applies only from the day this version is published on send.tax, plus any notice we owe (public WISP § 14). Cloudflare: R2's region is the United States, in a bucket created with Cloudflare's us jurisdiction (it said to be confirmed). Modal: the United States, pinned to Modal's U.S. regions in our code, where Modal runs pinned functions only (it said United States, container region pinned to US). Clerk: two-step verification settings once it is available, which is for pilot firms in December. Drafted with Claude. |
| 1.6 | 2026-10-26 | Liam Howell | Liam Howell (QI), for Howell & Gibbs LLC | The 2026-10-26 security and legal review. Fly.io: its Redis is operated by Upstash, reached only over Fly's private network, and carries the job queue and realtime events. Cloudflare: Turnstile, the bot check on sign-up, sees the visitor's address and browser signals. Clerk, Resend and Sentry: the Region column says what the "United States" rests on (each vendor's published documentation and, for Sentry, our organization's data region), to be confirmed in writing at the annual review. Sentry: browser events carry the visitor's address and the page's address. PostHog: the visitor's address comes with each event; the email address is no longer sent at sign-in, only the account id (a reduction, from this version's publication). Other vendors: Tailscale (it was in the WISP but not here), Anthropic's Claude (our source code), OpenAI (our labeling tools, on public samples and our own documents), Notion, and Google Fonts, which a visitor's browser fetches from Google. No sub-processor added or removed; nothing here starts a notice period. Drafted with Claude. |