Trust Center

Vendor Management Policy

How third-party vendors and sub-processors are selected, monitored, and removed.

Version: 1.5Effective: 2026-10-26Owner: Howell & Gibbs LLCDownload PDF

This policy describes how SendTax selects, evaluates, contracts with, monitors, and terminates relationships with third-party vendors and sub-processors that touch customer data or operate infrastructure on which SendTax depends. It is the service-provider oversight part of our information security program under the FTC Safeguards Rule (16 CFR 314.4(f)).

It is a companion to our Information Security, Access Control, Encryption, Incident Response, and Data Retention and Deletion policies. The current list of sub-processors is maintained as a separate Sub-processors page within our Trust Center.

Items marked Roadmap are not yet in production.


1. Principles

  1. Customer trust is non-transferable. When a vendor handles customer data on SendTax's behalf, the customer's trust still sits with SendTax. We are responsible for our vendors' behavior with respect to customer data.
  2. Necessity before convenience. Every vendor relationship begins with a question: is this service necessary, or are we adding surface area for ergonomic reasons? Vendor count is treated as a cost, not as a free decision.
  3. U.S. data residency. Customer data must be stored and processed in the United States, by providers using U.S. data regions (§ 6). The one thing outside it is the network edge: TLS for a visitor's connection terminates at the Cloudflare or Fly.io location nearest them, before the traffic reaches our U.S. servers. Nothing is stored there.
  4. Defense in depth across the supply chain. No single vendor's compromise should be sufficient to expose customer data; our encryption and access controls remain in place even when a vendor is involved.
  5. Transparent to customers. The current list of sub-processors is published, and changes to it are announced as § 10 describes.

2. Definitions

TermMeaning
VendorAny third party that provides a service to SendTax. Includes both customer-data sub-processors and internal-only tools.
Sub-processorA vendor that processes, stores, or transmits personal data on SendTax's behalf in the course of delivering SendTax's services. A subset of "vendors."
Internal-only toolA vendor used by SendTax staff that does not, in normal operation, process customer personal data (e.g., source-control hosting, password manager, design tools).
DPAData Processing Agreement. The contractual instrument that documents how a sub-processor will handle personal data and what their obligations to SendTax (and to data subjects) are.

3. Vendor tiering

Every vendor is classified into one of three tiers. The tier determines what evidence is required at onboarding, what monitoring is required ongoing, and what changes require customer notification.

Tier 1 — Customer-data sub-processors

Definition. The vendor processes, stores, or transmits identifiable customer personal data (including tax-return data, identity documents, contact information, authentication data, or behavioral telemetry tied to identified users).

Examples in current use: Fly.io (hosting + database), Cloudflare R2 (document storage), Clerk (identity), Google Cloud KMS (key management), Vercel (the website, including sign-up and onboarding), Resend (email), Google Workspace (company email), Sentry (error monitoring with PII scrubbing), PostHog (product analytics), Modal (ML inference). The Sub-processors page is the complete list.

Onboarding requirements:

  • Signed Data Processing Agreement (DPA) meeting § 5.
  • Documented data flows: what personal data category goes to the vendor, why, and how it returns or is destroyed.
  • Review of the vendor's most recent independent security attestation (SOC 2 Type II, ISO 27001, or equivalent). The attestation must cover the service we use; a parent company's report counts only if its scope does. We don't take on a Tier 1 vendor without one. Vercel and Google Workspace were in use before we reviewed them, and we review both by the next annual review of Tier 1 vendors (Information Security Policy § 5.5).
  • Confirmation that customer data stays in U.S. regions (§ 6).
  • Listing on the public Sub-processors page, and the customer notice in § 10, at least 30 days before production cutover, except as § 10 allows.

Ongoing requirements:

  • Annual review of the vendor's published security posture (refreshed SOC 2, breach disclosures, status-page incidents).
  • Inclusion in our internal vendor inventory with the data categories they touch.
  • Material changes (vendor swap, new data category) trigger customer notification under § 10. A vendor may not move customer data out of the United States (§ 6).

Tier 2 — Operational vendors with incidental customer-data exposure

Definition. Vendors that, in the course of normal operation, do not handle identified customer personal data, but could see limited customer data in operator-driven workflows (e.g., debugging sessions, support escalations).

Examples in current use: GitHub (source control — should never contain customer data).

Onboarding requirements:

  • DPA where the vendor provides one as a standard offering.
  • Confirmation that customer personal data is not deliberately written to the vendor.
  • Internal access controls limiting which operators can pull customer data into the vendor's surface.

Ongoing requirements:

  • Reviewed at the annual vendor review.
  • Not listed as sub-processors on the Sub-processors page (they are not sub-processors in the technical sense), but recorded in our internal vendor inventory.

Tier 3 — Internal-only tools

Definition. Vendors used by SendTax operators that have no exposure to customer personal data in any normal or abnormal mode of operation.

Examples in current use: 1Password (operator credentials), our domain registrar, design tools, productivity software.

Onboarding requirements: Standard vendor terms-of-service acceptance. No formal DPA required.

Ongoing requirements: No active monitoring beyond normal account hygiene; covered at the annual vendor review only by inventory verification.


4. Selection criteria

When evaluating a candidate vendor for any tier, SendTax considers:

CriterionWhat we look for
Security postureThe vendor's independent attestations (SOC 2 Type II preferred); a published security program; a credible disclosure history.
Data residencyU.S. regions available, with clear regional controls, so customer data stays in the United States.
EncryptionTLS in transit; AES-256 at rest; KMS-backed key custody where applicable.
Access controlsSSO support; role-based access; audit logs available to us as the customer.
Sub-processor transparencyThe vendor publishes its own sub-processor list and notifies of changes.
DPA qualityClear breach-notification timeline; clear sub-processor flow-down; clear deletion-on-termination commitment.
Financial stability and longevityA credible runway and either a stable customer base or open-source fallback.
Exit pathReasonable export of data; ability to migrate without re-engineering.
CostConsidered last, after security and fit.

For Tier 1 vendors, the evaluation is recorded in our internal vendor inventory (§ 13), with the vendor's DPA status. A formal templated vendor-review checklist is on our roadmap. (Roadmap)


5. Contractual requirements

For Tier 1 sub-processors

Each Tier 1 sub-processor relationship must be governed by a written DPA (or equivalent contract terms). The DPA must address, at minimum:

  • The categories of personal data processed and the purposes of processing.
  • The vendor's obligation to process personal data only on documented instructions from SendTax.
  • Confidentiality commitments for the vendor's personnel.
  • The vendor's technical and organizational security measures.
  • The vendor's obligation to notify SendTax of any personal-data breach without undue delay (and within any contractually agreed timeline).
  • The vendor's use of further sub-processors, including SendTax's ability to object.
  • The vendor's obligation to assist SendTax with data-subject requests, data protection impact assessments, and breach notification.
  • Deletion or return of personal data on termination of the relationship.
  • Audit rights — typically satisfied by the vendor's independent attestation reports rather than on-site audits.

We have not yet signed a DPA with every Tier 1 sub-processor in use today. Until we do, the relationship runs on the vendor's standard terms, including any data-processing terms they incorporate. We check those terms against this list at each annual vendor review. Signing a DPA with each of them is on our roadmap. (Roadmap) A new Tier 1 sub-processor needs a signed DPA before it receives customer data (§ 3).

For tax return information

We disclose tax return information to a sub-processor only so it can provide its service to SendTax, as IRC § 7216 allows for auxiliary services, and only within the United States (§ 6).


6. Data residency

SendTax operates only in the United States. Our Privacy Policy says client documents are stored and processed in the United States, and where: our API, database, background workers and the apps customers use after signing in run in Fly.io's Ashburn, Virginia region; documents are stored in a U.S. Cloudflare R2 bucket; the keys that protect them are held in Google Cloud's us-east1 region; and the service that reads documents to sort them runs in Modal's U.S. regions.

Every sub-processor that receives customer data must process it in a U.S. region, chosen at onboarding where the vendor offers a choice. We do not take on a sub-processor that would store or process customer data outside the United States. The Sub-processors page gives each one's region. Where it says "To be confirmed", we have not yet confirmed the region with the vendor. If a vendor turns out to process customer data outside the United States, we move that data to a U.S. region or replace the vendor, with notice under § 10.

The network edge is the one thing outside this rule. TLS for a visitor's connection terminates at the Cloudflare or Fly.io location nearest them, which passes the traffic on to our U.S. servers over an encrypted connection. Nothing is stored there.

If this rule ever changed, it would be a new version of this policy, with notice under § 10, and no tax return information would leave the United States without the consent IRC § 7216 requires. Social Security numbers would not be included.


7. Onboarding process

For a Tier 1 vendor, the onboarding process is:

  1. Need check. Document the specific job the vendor will do and confirm no existing vendor already covers it.
  2. Candidate evaluation. Apply § 4 criteria to a short list (typically two or three candidates).
  3. Security and contractual review. Pull the vendor's SOC 2 or equivalent; review the DPA against § 5 requirements; negotiate changes where necessary.
  4. Data-flow mapping. Document what personal-data categories will leave SendTax, in what form (plaintext, encrypted-by-us, etc.), and how they return.
  5. Integration with security baseline. Configure access controls, audit logging, and secret storage per Information Security and Access Control.
  6. Sub-processors page update. Add the vendor to the public Sub-processors page before any production data flows.
  7. Customer notification. Give customers the notice § 10 requires, at least 30 days before step 8 except as § 10 allows.
  8. Cutover. Production traffic begins.

For Tier 2 and Tier 3 vendors, onboarding is documented in the internal vendor inventory but does not require the full checklist above.


8. Ongoing monitoring

What we monitor

  • Published security incidents. Vendor status pages and breach disclosures are checked when a vendor publicly reports an incident affecting customers.
  • DPA and policy changes. Notifications from vendors about changes to their DPAs, sub-processor lists, or data-handling policies are reviewed and acknowledged.
  • Attestation renewals. Annual confirmation that the vendor's SOC 2 (or equivalent) is current.
  • Service health. Vendor outages are tracked when they affect SendTax service delivery and are recorded in our incident timelines per the Incident Response Policy.

How often

  • Tier 1: Reviewed at least annually. Material vendor events (breach, ownership change, region change) trigger out-of-cycle review.
  • Tier 2 and Tier 3: Reviewed at the annual cycle only, unless an event warrants attention.

Findings are recorded in our internal vendor inventory. A material adverse change in a vendor's security can lead to reclassification, more diligence, or replacing the vendor.

What we don't do

  • We do not conduct on-site vendor audits; we rely on independent attestations and the DPA's audit-rights framework. This is standard practice for a company of our size and a deliberate scope decision.
  • We do not run automated vendor-risk-scoring tools. A formal vendor risk register and structured annual scoring is on our roadmap. (Roadmap)

9. The Sub-processors page

SendTax maintains a public list of Tier 1 sub-processors as part of its Trust Center: the Sub-processors page. It is the complete and authoritative list. It includes, for each entry:

  • The vendor's name and the URL of their security/trust page.
  • The service they provide to SendTax.
  • The category of personal data they may process.
  • The processing region.
  • A link to their security documentation, and, where their standard terms incorporate data-processing terms, to those; the page says where our signed DPAs stand (today, with none of them).

The page is updated whenever a Tier 1 vendor is added, removed or replaced, with an entry in its Change history, and reviewed for accuracy at the annual vendor review.


10. Customer notification of changes

When a Tier 1 sub-processor is added, removed, or replaced — or when an existing sub-processor expands the data categories it handles — SendTax notifies customers in advance. For an addition, a replacement or a new data category, the notice comes at least 30 days before the sub-processor receives that customer data.

We give notice in two ways:

  • The Sub-processors page. We update the Sub-processors page and record the change in its Change history. The page is the record of every change.
  • A notice in SendTax. Filers and tax professionals who open SendTax while the notice is up see it as a banner, and we record which accounts were shown it. The notice stays up at least until the change takes effect.

We do not yet email every account holder about these changes. Email updates you can sign up for on the Sub-processors page are on our roadmap. (Roadmap)

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 first and tell customers as soon as we can.
  • If we must replace a sub-processor sooner than 30 days for one of those reasons, the notice may be shorter. It still comes before the new sub-processor receives customer data, and it says why it is short.

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.


11. Incidents involving vendors

When a security incident originates with or is exacerbated by a sub-processor, the incident is handled per the Incident Response Policy, with two specific obligations:

  • We engage the vendor's published incident-response or support channel without delay.
  • The vendor's communications are tracked on our own incident timeline so customer notifications reflect the full picture, not just SendTax's actions.

SendTax remains responsible for customer notification regardless of whether the underlying issue was within SendTax-operated infrastructure or a vendor's.


12. Termination and offboarding

When a vendor relationship ends — whether at SendTax's initiative, the vendor's, or because a contract ends — the offboarding process includes:

  1. Migration. Customer data, where applicable, is migrated to a replacement vendor or back to SendTax-operated infrastructure.
  2. Deletion request. SendTax issues a formal deletion request to the vendor under its DPA or other terms. The vendor's confirmation of deletion is captured for our records.
  3. Credential rotation. All API keys, OAuth grants, and service-account credentials issued to the vendor are revoked at the source and the references in SendTax secret storage are removed.
  4. Sub-processors page update. The vendor is removed from the public page.
  5. Customer notification. For a Tier 1 sub-processor, customers are notified per § 10.
  6. Record. The offboarding, its reason and the vendor's deletion confirmation are recorded in our internal vendor inventory.

In an emergency, such as a security incident at the vendor, the same steps apply, compressed in time (§ 10).


13. Internal records

SendTax maintains an internal vendor inventory recording, for each vendor:

  • Tier classification.
  • Service description and data categories.
  • Region(s).
  • DPA / contract status and renewal date.
  • When we last reviewed the vendor's SOC 2 (or equivalent).
  • Listing status on the public Sub-processors page (Tier 1 only).
  • Owner inside SendTax for ongoing relationship management.

The inventory is reviewed at the annual vendor review and updated whenever a vendor changes tier, scope, region, or contractual status.


14. Policy review

This policy is reviewed at least annually, and additionally whenever:

  • A Tier 1 sub-processor is added, removed or replaced.
  • A new vendor tier or category is introduced.
  • A change in law affects how vendors may handle customer data (for example, IRC § 7216 or the FTC Safeguards Rule).
  • A vendor-driven incident reveals a gap in this policy.

Each version, and each annual review, is recorded in § 16, Change history.


15. Contact

Vendor-related questions and objections[email protected]
Security disclosures[email protected]
General[email protected]
Operating entityHowell & Gibbs LLC

16. Change history

VersionDateAuthorApproved byChanges
1.02026-05-30Holly GibbsNot recordedFirst public text, shown as "v1" in its status line. Drafted with Claude.
1.32026-10-07Liam HowellLiam Howell (QI), for Howell & Gibbs LLCOne version number and one change history for this policy's internal and public texts and its Notion page (WISP § 7.4; public WISP § 14); earlier versions were numbered separately (internal 1.0–1.2, public 1.0 shown as "v1", Notion draft 1.0). Section numbers below are the public text's unless marked internal. § 9 and internal § 3: the Sub-processors page is the one complete list (internal § 3 named WISP § 4.4 and a page deleted on 2026-06-02). § 10 and internal § 7: customers get at least 30 days' notice before a sub-processor is added or replaced or handles a new category of customer data, given on the Sub-processors page and in the app; email sign-up is Roadmap. A sub-processor stopped at once, to protect customer data or because the vendor stops its service, is announced as soon as we can afterward, and a replacement forced by either may get shorter notice, still in advance (the public text said every change was announced in advance). Corrected: § 10 named the Incident Response notification system, which serves incidents only. § 3: a Tier 1 vendor needs an independent attestation that covers its service; the compensating-controls alternative is removed. §§ 1, 2, 4, 5 and 6: customer data must stay in the United States, with no exceptions; regions not yet confirmed are marked on the Sub-processors page. The EU/UK transfer terms (§§ 2 and 5) are removed because we operate only in the United States. Corrected: we have not yet signed a DPA with every Tier 1 sub-processor (§§ 4, 5); a new one still needs a signed DPA. § 5 adds the IRC § 7216 limit on disclosing tax return information to sub-processors. Corrected: § 3 said GitHub was not listed on the Sub-processors page, where it is listed as a vendor that is not a sub-processor; internal § 7.1 said the email sign-up form was on the Trust Center, where it has been on no page since 2026-06-02; internal § 7.3 said the emails met RFC 8058, but they carry the unsubscribe link in the body only. § 3 no longer says GitHub is checked by automated secret scanning, which we could not confirm. § 12 and internal § 5: one six-step offboarding list, recorded in the vendor inventory; internal § 5 names every secret store (it left out Vercel and Modal). Internal § 2: a vendor must report a breach to us without undue delay (it said within 24–72 hours), and vendors already in use are checked against it and against U.S. residency by the next annual review; Vercel and Google Workspace, in use but not listed, were added to the vendor inventory on 2026-10-01, with no DPA requested yet, and are reviewed against all six checks by then. Internal § 4: a monthly status-page check of Tier 1 vendors replaces a quarterly review that was never scheduled. Internal § 7.4: the cutover protocol adds the in-app notice and the 30 days, and replaces the finished Postmark example. § 14 and internal § 8: reviewed at least annually (the Notion draft and the compliance register said semi-annual), and after each sub-processor change. Past row dates corrected to the day each version was merged (internal 1.1: 2026-05-26 to 2026-05-27; public 1.0, whose Effective date said 2026-05-21, is dated 2026-05-30). Also records a change made without a row: #345 (2026-09-11) changed internal § 7.1's email transport from Postmark to Resend. The two emergency exceptions to advance notice (§ 10; internal § 7.2) narrow a commitment, so they apply only from the day this version is published on send.tax. No notice is owed: SendTax has no customers yet. Drafted with Claude.
1.42026-10-22Liam HowellLiam Howell (QI), for Howell & Gibbs LLCSecurity statements, the Qualified Individual's decision of 2026-10-21. Corrected, public text: § 3 said a Tier 1 vendor without a current independent attestation is not used; we don't take one on, but Vercel and Google Workspace were in use before we reviewed them, and both are reviewed by the next annual review of Tier 1 vendors. Public § 1 item 3 and § 6, and internal § 6, said customer data stays in the United States with no exceptions, which wasn't so: TLS for a visitor's connection terminates at the Cloudflare or Fly.io location nearest them before the traffic reaches our U.S. servers. They now keep U.S. storage and processing as the rule and name that network edge as the one thing outside it, 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). Public § 6 gives where client documents are stored and processed (it said the Privacy Policy says we store and process customer data in the United States). Internal § 6: document files are kept in an R2 bucket created with Cloudflare's us jurisdiction, which keeps them in the United States. Public §§ 4 and 13 say whose SOC 2 they mean: the vendor's. Internal § 7: the notification records answer an auditor or a customer (it said a SOC 2 reviewer). Drafted with Claude.
1.52026-10-26Liam HowellLiam Howell (QI), for Howell & Gibbs LLCThe 2026-10-26 security and legal review. Public § 3 examples add Vercel and Google Workspace, both Tier 1 on the Sub-processors page. Public § 7: a vendor's record links its security documentation and any data-processing terms its standard terms incorporate; the page says where our signed DPAs stand (it asked for a link to a published DPA, which the page never carried). Internal § 6: Clerk, Resend and Sentry are shown as United States on the strength of each vendor's published documentation, checked 2026-10-26 and to be confirmed in writing at the annual review (the text said their regions were not confirmed, while the page showed United States). Internal § 5: offboarding also removes a vendor from the provisioning scripts and build files; Microsoft Clarity, removed in #67, was still read by the Vercel sync script and three Dockerfiles until 2026-10-26. Drafted with Claude.