Trust Center

Tax documents are some of the most sensitive data you own. Here’s how we look after them.

SendTax holds W-2s, IDs, K-1s, and the other documents you share with your preparer. This page is the single source of truth for our security program — the policies that govern it, the vendors that touch it, and how to reach us if something looks wrong.

The short version

You decide which tax professional sees your documents.

A tax professional sees your documents only after you accept their invitation, and the database enforces that.

Our policy is that SendTax staff open a document only for support you ask for or to fix a processing error, and record each time they do.

Where we are on compliance

SendTax is a new company. Rather than wave compliance badges we haven’t earned, here is exactly where each framework stands today — including what we haven’t done yet.

  • Written security program (WISP)

    Published

    Our WISP goes through the FTC Safeguards Rule’s required elements one by one, uses IRS Publication 4557, and says where we fall short today. Two-step verification isn’t available yet; it switches on for pilot firms in December. We haven’t done a formal risk assessment or annual security-awareness training yet.

  • Independent audit and testing

    None

    No outside firm has audited SendTax’s security or tested our systems, so there’s no audit report to share. None is scheduled.

  • CCPA / CPRA (California)

    California residents have rights under the CCPA/CPRA to access, correct, delete, and limit use of their personal information. As our Privacy Policy explains, those rights generally don’t apply to GLBA-covered customer financial data, but can apply to other data, such as site usage; we honor them where they apply. Requests go to [email protected].

  • GDPR / UK GDPR

    N/A

    SendTax operates only in the United States. We do not knowingly serve EU/UK data subjects; if that changes, we will update this page first.

At a glance

The defaults that ship with every SendTax account.

Client documents
United States
Client documents are stored and processed in the United States. If you connect from outside the U.S., the Cloudflare or Fly.io location nearest you passes your connection on to our U.S. servers over an encrypted connection.
Encryption in transit
TLS
Connections to SendTax are encrypted with TLS, and our sites tell browsers to use HTTPS only (HSTS).
Encryption at rest
AES-256-GCM
Each document is sealed as soon as it arrives, with its own key; those keys are protected in Google Cloud KMS (us-east1).
Identity
Clerk
Two-step verification isn’t available yet; it switches on for pilot firms in December.
Access
Row-Level Security
The database itself limits each firm to the clients who accepted its invitation.
Logging
Audit log
Sign-ins, document downloads, staff opening a document and changes to who can see a client, kept for at least 7 years.

Policies & documents

Every policy that governs SendTax. Read them on this site, or download the PDF for your own records.

Security

How we protect customer data — controls, access, encryption, and response.

Operations

How we run the service reliably and manage change.

Data handling

What we collect, how long we keep it, and how vendors are governed.

Acceptable use

How customers may use the platform, and how our staff may use our systems.

Who else touches your data

The third parties that process customer data on SendTax’s behalf. All Tier 1 sub-processors are U.S. companies; the list gives each one’s region.

View the full list
  • 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

Reach the security team

We respond to security concerns from anyone — customers, researchers, regulators. If you’ve found something that looks wrong, we want to hear about it.

Please do not include sensitive customer data (full SSN, document images) in the initial email; we’ll provide a secure channel after we acknowledge.

  • Security disclosures

    [email protected]

    Vulnerabilities, suspected incidents, anything you’d rather not say in public.

  • Privacy & sub-processor questions

    [email protected]

    Data subject requests, sub-processor objections, contract questions.

  • Everything else

    [email protected]

    General inquiries — we’ll route from there.