Security at Easy Client Docs
Last Updated: November 6, 2026
1. Overview
Tax professionals use Easy Client Docs to collect documents, intake forms, photo IDs and e-signatures from their clients. This page describes, plainly, the security controls we have in place today, what we do not yet offer, and the third parties that process data on our behalf.
2. Encryption
- In transit: All traffic to the Service uses HTTPS (TLS). HTTP Strict Transport Security (HSTS) is enabled, so browsers only connect over HTTPS.
- At rest: Our hosting providers encrypt stored data at rest with provider-managed keys: Neon for the database and Google Cloud Storage for files.
We do not currently offer application-layer or end-to-end encryption, customer-managed keys, or hardware security modules operated by us.
3. Staff Accounts and Access Control
- Multi-factor authentication: Required for every staff account. Team members can use an email code, an SMS code, an authenticator app, or a passkey.
- Role-based access: Each firm assigns roles (owner, manager, user, viewer) that control what each team member can see and do.
- Tenant isolation: Each firm's data is kept separate from every other firm's data.
- Passwords: Stored only as bcrypt hashes, never in plain text.
- Sessions: Sessions expire after a period of inactivity and have a maximum lifetime.
- Rate limiting: Sign-in attempts and one-time code entry are rate limited to slow down guessing attacks.
- Security headers: The Service sends standard browser security headers, including HSTS and protections against framing.
4. Client Access
- One-time codes and expiring links: Clients open document requests, forms and signing requests through links that expire and, where required, a one-time code sent to them.
- Client portal (launching): Each firm can offer its clients a portal under its own account. Two-factor authentication is mandatory for every client portal account.
- Secure delivery instead of email attachments: Documents are exchanged through the Service rather than sent as email attachments.
5. Audit Logging
The Service records sign-ins, document access and changes in an audit log. Firm owners and managers can review their firm's audit log in the app, filter it by date, person, action and item, and export it as a CSV file. Actions taken by our support staff in a firm's account appear in that firm's log as "Platform support".
6. Deletion and Export
- Deletion: Deleting a document, client or account deletes the related database records and stored files. There is no trash folder, so deleted items cannot be recovered. Copies may remain for a limited period in our hosting providers' backup systems until they expire.
- Export: A firm owner can download documents per client, or as a zip file of selected documents. There is no one-click export of a whole account yet; on request, our support team will provide an export.
7. Compliance Status
- SOC 2: Easy Client Docs does not yet have a SOC 2 report. SOC 2 readiness is in progress, and we are targeting a report in 2027. Our infrastructure and service providers (Google Cloud, Neon, Replit, Stripe and SendGrid) hold their own SOC 2 reports.
- IRS Publication 4557 and the FTC Safeguards Rule: The Service is designed to help tax professionals meet their obligations, for example through secure delivery instead of email attachments, required MFA, access controls and an audit trail. Each firm remains responsible for its own compliance, including its Written Information Security Plan (WISP).
8. Security Incidents
If we confirm a security incident affecting a firm's data, we will notify the affected firms without undue delay, and in any case within 72 hours of confirming the incident, as set out in our Terms of Service.
9. Responsible Disclosure
If you believe you have found a security vulnerability in Easy Client Docs, please email security@easyclientdocs.com with a description and the steps to reproduce it. Please do not access or change other people's data, and give us reasonable time to fix the issue before disclosing it publicly. We will acknowledge your report and keep you informed of our progress.
10. Subprocessors
We use the following third parties to provide the Service. Each processes only the data needed for its purpose.
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Replit | Application hosting (Replit Deployments, running on Google Cloud) | All data processed by the Service while it runs | US |
| Neon | Database (PostgreSQL) | Firm accounts, team members, client records, form responses, e-signature records, audit log | US |
| Google Cloud Storage | File storage (via Replit Object Storage) | Uploaded documents, signed PDFs, photo IDs and other files | US |
| SendGrid (Twilio) | Email delivery | Recipient names and email addresses, email content such as notifications, secure links and sign-in codes | US |
| Message Central | SMS delivery of one-time sign-in codes | Mobile phone numbers and one-time codes | US |
| Stripe | Subscription payments and billing | Firm billing contact and payment details | US |
| OpenAI | AI form-field extraction, only when a firm uses AI form import | The uploaded form template being imported | US |
| Google Document AI | AI form-field extraction, only when a firm uses AI form import | The uploaded form template being imported | US |
| HighLevel | CRM for firm sign-ups and billing contacts | Firm contact name, email, phone and plan. No end-client data | US |
See also our Privacy Policy and Cookie Policy.