FinishTax handles Social Security Numbers, tax documents, and signatures. Here is exactly how we protect them — down to the algorithm — so you can answer your clients with confidence.
Security isn't a page we bolted on — it's built into how FinishTax stores, transmits, and grants access to every record. Below is a plain-English account of the protections in place, and what they mean for you and your clients.
Sensitive data is encrypted before it is written to disk and again as it moves across the network.
Social Security Numbers, EINs and organizer answers to questions that name an SSN, bank account or routing number are encrypted with authenticated AES-256-GCM before they ever touch the database.
When you link Gmail, Outlook, Google Calendar, or QuickBooks, the OAuth access and refresh tokens are encrypted at rest with the same AES-256-GCM scheme.
All traffic between your browser, our servers, and our providers is protected in transit with TLS (1.2+). Your data is never sent over an unencrypted connection.
Cloud data is stored in US-based infrastructure built on SOC 2-compliant providers, and is accessible only through your authenticated account.
Getting into an account is deliberately hard for everyone but you.
Passwords are never stored in plain text. They are hashed with bcrypt (cost factor 12), so even we cannot read them.
Turn on 2FA using any authenticator app (TOTP). You also get single-use backup codes for the day you lose your phone.
Access tokens are short-lived (15 minutes) and refreshed through an httpOnly, Secure, SameSite cookie that JavaScript can't read — limiting the blast radius if a token ever leaks. Firm accounts are also signed out after 60 minutes of inactivity, or 12 hours when you choose to stay signed in.
Login and 2FA attempts are rate-limited, an account locks itself after repeated failed sign-ins, and abusive IP addresses can be blocked outright — so guessing attacks fizzle out fast.
Signing Form 8879 electronically has real compliance requirements. Here is what FinishTax's signer checks do, and what they don't.
Collect authorizing signatures on Form 8879 (and other documents) electronically, with the identity check you choose per envelope.
Set the identity check each signature requires — from an emailed one-time code, to internal security questions built from the client's own record on file, up to a government-ID + live-selfie check run by our verification provider, Stripe Identity. You choose the check per envelope.
None of these checks is the record check IRS Publication 1345 asks for on a remote Form 8879: the taxpayer's name, SSN, address and date of birth checked against outside records (an agency, a credit bureau or similar), usually as knowledge-based questions from a credit reporting company. The internal security-questions rung is a convenience check, not Pub-1345-compliant KBA: it draws on the record you typed, not a credit bureau or other third party. The government-ID + live-selfie check runs no SSN, date of birth, address or credit-bureau check, and FinishTax takes only the first and last name from the result. So FinishTax does not claim any of its checks meets Pub 1345 for a remote 8879. For an 8879 signed in person, Pub 1345 lets you inspect the client's photo ID yourself and record their name, SSN, address and date of birth.
Your firm never sees the photos. The ID image and selfie are captured and held by our verification provider, Stripe Identity, on its own page. FinishTax's server keeps only the result (a pass/fail status, a session reference and the first and last name printed on the ID) and never downloads or stores the images.
We compute a SHA-256 hash of each document when it's added to an envelope, before anyone signs, and print it on the completion certificate. When the envelope completes, we record a second hash of the final signed PDF on our side; it cannot be printed on the certificate, which is part of that PDF. Both hashes are kept for every completed envelope, sealed or not, and a sealed PDF also shows any later change through its digital seal (below).
Every completed signature produces a certificate with the document details and the original's hash, each signer's identity-check result, consent time, IP address and device, and a full audit trail of the signing events.
Completed envelopes are sealed with a PAdES digital signature and, when the timestamp service answers, a trusted timestamp (RFC 3161), using FinishTax's own signing certificate, and the app labels an envelope “digitally sealed” only when that really happened. Our certificate is not issued by an Adobe-trusted (AATL) authority, so Adobe Acrobat shows the seal as “validity unknown” until the reader chooses to trust it. The SHA-256 hashes and the audit trail on the completion certificate, described above, remain the primary evidence. We would rather say that plainly than imply a seal every reader validates on its own.
FinishTax uses Anthropic's Claude API for two separate things: classifying tax files, and the AI assistant you can ask questions in. They send very different amounts of data — here is exactly what triggers each, and what it does and doesn't mean for your clients' records.
Uploading a file does not, by itself, send it anywhere. A file reaches Anthropic for classification only when you click Classify on a document, run a batch classification (up to 50 files at once), or when the optional daily triage agent is turned on. Uploads sit untouched until one of those three actions happens.
For manual and batch Classify, the document itself — as an image, a PDF (capped at 20MB), or extracted text — goes to Anthropic's API so it can read the file and return a suggested name, document type, tax year, and summary. The daily triage agent works differently: it's opt-out, not opt-in (on by default, with a toggle in Settings to turn it off, and it never runs for a firm that has turned AI features off), and it sends only the filename, file type, and your active client list — never the document's contents — to suggest which client and pipeline stage an unrouted upload belongs to. Both are paid-plan features; the triage agent additionally requires the Small Firm plan or higher.
The assistant is a separate, paid-plan search tool you ask a question in — it never runs on its own. Each time you ask it something, FinishTax sends Anthropic a working set of your practice data as context so it can answer: client names, emails, statuses, tax years, and filing statuses; task titles, priorities, and due dates; invoice numbers, totals, amounts paid, and due dates; uploaded file names plus their previously generated AI type and summary; document-checklist items and their received/missing status; and upcoming appointment titles, times, and locations. That's a materially broader flow than file classification, it happens on every question, and nothing about it is optional once you use the assistant — there's no separate toggle to narrow what it sends. The response is returned to you and is not stored server-side as a transcript.
We're not going to make that promise on Anthropic's behalf — we don't control their model training pipeline and can't verify it from our side. What we can tell you plainly: your documents go to Anthropic's commercial API, governed by Anthropic's own commercial terms, not by anything FinishTax writes here. Read Anthropic's commercial Terms of Service for their current policy on API data and training.
The triage agent never files, renames, or reassigns anything on its own. It records a suggestion you review and accept (or ignore) from Assistant activity, under Clients → Automations; only accepting it applies the change, and it will never reassign a file that's already attached to a client.
The firm owner or an admin can turn AI features off for the whole firm in Settings, under Your firm. It is on by default and applies to the one practice it is set in, so a firm with several practices turns it off in each. While it is off, nothing from that firm is sent to Anthropic by anyone on the team, from the web app or the phone apps: no documents, file names, client lists, messages or questions typed into the in-app help. Classify, batch classify, the AI assistant, Read these documents, Describe the automation, the daily triage agent and Ask for help stop working for everyone at the firm, and the server refuses the request, so it does not depend on a button being hidden. Each change is recorded in the firm's activity log. Every person also has their own AI features switch in Settings, under Security, and is asked before the first AI request is sent.
On team plans, everyone sees exactly what they should — and every important action is recorded.
Permissions are controlled through 30 distinct permission keys across clients, documents, financials, communication, workflow, and administration — grouped into five ready-made role templates you can customize.
Client access can be scoped so a team member sees all clients, only the clients assigned to them, or none — the same applies to client messages.
A per-client activity timeline records who did what and when — document uploads, status changes, messages, and other key actions, each tied to the team member who did it.
All card payments are processed by Stripe through its hosted checkout and billing portal. Full card numbers never touch — and are never stored on — FinishTax servers.
Proven, managed building blocks — not homegrown storage.
Cloud data is stored in US-based infrastructure built on SOC 2-compliant providers. Records are held in an encrypted, SSL-connected PostgreSQL database, and uploaded documents are stored in S3-compatible object storage (Supabase Storage, with Cloudflare R2 support).
All data is encrypted in transit (TLS 1.2+) and accessible only through your authenticated account. Social Security Numbers, IRS preparer credentials (EFIN/PTIN), and connected-account tokens are additionally encrypted by FinishTax with AES-256-GCM before they reach the database; other data, including uploaded documents, is encrypted at rest by our storage providers. For the full list of the subprocessors we rely on and the data each one handles, see our Privacy Policy.
The database is backed up every night and before every structural change. Backups are encrypted with a key that never lives on the same infrastructure, stored in a separate object store, and kept for 30 days. Downloads of client files from the Documents area of the firm app and from the client portal are recorded in that client's activity log, and a full export records one entry per client.
As a paid preparer, you have data-security duties under IRS Publication 4557 and the FTC Safeguards Rule. FinishTax gives you concrete tools to help satisfy them.
FinishTax helps you put the IRS Publication 4557 safeguards into practice with encrypted storage of taxpayer data, multi-factor authentication, and access controls for your staff.
FinishTax helps you meet key elements of the FTC Safeguards Rule through encryption of customer information, per-user access limits, and activity logging you can point to during a review.
Export a backup of your clients, tasks, invoices, activity, messages, organizer answers and e-signature records as a single JSON file at any time, or use Download everything to save every document too: originals and signed PDFs in a folder per client, your firm files and the backup, together in one zip on your computer. Social Security numbers and the organizer answers we encrypt stay encrypted in the file, unless the firm owner chooses to include them in full after entering their password again; each such export is recorded and the owner is sent an email notice. A portable copy you fully control.
You can permanently delete your account from the app. It removes your database records, including client, task, and file metadata.
The questions tax professionals ask us most.
Not yet. The managed cloud providers FinishTax is built on — database, file storage, and hosting — maintain SOC 2 audits, but the FinishTax application has not completed a SOC 2 certification of its own. That is why we describe our foundation as built on SOC 2-audited providers, rather than claiming a certification of the FinishTax application itself.
SSNs, EINs and organizer answers to questions that name an SSN, bank account or routing number are encrypted with authenticated AES-256-GCM before they are written to the database, each with a unique initialization vector and authentication tag. They are decrypted only in memory when needed, and in production the app will not start without a valid encryption key configured.
Yes. You can enable 2FA with any authenticator app that supports TOTP (such as Google Authenticator or Authy), and you receive ten single-use backup codes for account recovery. Backup codes are stored only as hashes.
For a remote Form 8879, no FinishTax check is the record check IRS Publication 1345 asks for. That is a check of the taxpayer's name, SSN, address and date of birth against outside records, so we do not claim any of our checks meets Pub 1345 for a remote 8879; see “Step-up identity verification” above. FinishTax supports electronic signing of IRS Form 8879 and other documents with a step-up identity ladder (from emailed one-time codes up to government-ID + live-selfie verification, chosen per envelope), plus tamper-evident SHA-256 document hashing and a completion certificate with a full audit trail. Completed envelopes are digitally sealed with FinishTax's own certificate, so a later change to the PDF shows; see “PAdES sealing” above.
No. All card payments are handled by Stripe through its hosted checkout and billing portal. Full card numbers never touch — and are never stored on — FinishTax servers.
Yes. On team plans, access is governed by 30 permission keys and five customizable role templates, and client visibility can be scoped to all clients, only assigned clients, or none. Per-client activity is recorded in an activity timeline tied to the team member who took each action.
Yes to both. You can export a JSON backup of your clients, tasks, invoices, activity, messages, organizer answers and e-signature records at any time, or download everything in one zip: every document in a folder per client, your firm files and the backup. Downloads of client files in a full export are recorded in each client's activity log (one entry per client). Only the firm owner can choose to include full Social Security and bank numbers, after entering their password again. You can permanently delete your account from within the app, which removes your database records. See our Privacy Policy for details on retention.
FinishTax doesn't train any model. Documents are sent to Anthropic's Claude API only when you trigger classification — clicking Classify, running a batch, or via the optional triage agent — never automatically on upload. The firm owner or an admin can also turn AI features off for the whole firm in Settings, and then nothing from the firm is sent to Anthropic by anyone on the team, from any app. Whether Anthropic itself trains on API traffic is governed by Anthropic's own commercial terms, not ours — we won't make a promise on their behalf that we can't enforce. See AI document classification above for the full breakdown of what's sent and when.
No. Your firm never sees the photos. The ID image and selfie are captured and held by our verification provider, Stripe Identity, on its own page. FinishTax's server keeps only the result (a pass/fail status, a session reference and the first and last name printed on the ID) and never downloads or stores the images.
Start free and see the protections for yourself, or dig into the pricing that fits your firm. No credit card required to begin.
Open the app →