In tax and accounting, data security is table stakes.

Customer data, isolated and encrypted end to end.

1. 1 Customer data is stored in a PostgreSQL database hosted in Neon; additional data is stored in Google Cloud Storage.
2. 2 Each customer instance is tied to a unique database identifier for logical data separation and to ensure no commingling of data.
3. 3 In our Neon environments, data resides in the AWS US West 2 (Oregon) region with 99.999%+ durability and 30-day point-in-time-restore support.
4. 4 In GCP, data is replicated across multiple U.S. regions for redundancy and disaster recovery.
5. 5 All data is encrypted in transit using TLS v1.3 with modern cipher suites (AES-256, SHA2). At rest, data is encrypted with AES-256, with backups encrypted via KMS-managed keys and access restricted through GCP IAM policies.
6. 6 Routine backups are regularly tested to confirm restoration reliability. RTO is 48 hours; RPO is zero for the most recent 30 days (point-in-time recovery to any moment in that window).
7. 7 Customers may request a dedicated tenant: a separate Google Cloud project and Neon project provisioned for that customer alone.

Secure by default, audited by independents.

1. 1 Neo.Tax adheres to OWASP Secure Coding Guidelines and follows a secure development lifecycle: peer-reviewed code changes, static application security testing (SAST), dynamic application security testing (DAST), and automated regression testing.
2. 2 Annual third-party penetration tests across application and network layers, performed by an independent CREST-certified security firm.
3. 3 Continuous vulnerability scanning and timely patch management; critical updates applied within 48 hours.
4. 4 Deployments protected via a Web Application Firewall (WAF) with IP whitelisting.
5. 5 Employee workstations are protected by enterprise-grade antivirus with auto-updates and scheduled scans enforced.
6. 6 Remote access is gated by VPN, application-layer proxy, and IP whitelisting.

Role-based, MFA-enforced, session-bounded.

1. 1 Internal access to systems and data is restricted by RBAC, IP whitelisting, and MFA (all access encrypted end-to-end and monitored).
2. 2 Permissions are granted by least-privilege; access is revoked within 72 hours of role changes or termination. Quarterly access reviews are conducted and logs retained for at least one year.
3. 3 Customers sign in via email/password, magic link, or SSO. SAML 2.0 and OIDC supported with Identity Providers including Okta, OneLogin, Microsoft Entra, and Ping Identity.
4. 4 Passwords meet complexity requirements and are securely hashed; sessions are encrypted via TLS v1.3 and idle-logout after 20 minutes.
5. 5 User scopes: ADMIN, MEMBER, or NON-FINANCIAL MEMBER (cannot view financial data such as payroll or accounting transactions).
6. 6 Account-level PII redaction: review financial information without identifying individuals.

Privacy and auditability at the core of the model.

1. 1 Customer-specific data is strictly anonymized and masked before any AI training or fine-tuning takes place.
2. 2 Use of customer data for training is optional: clients may opt out entirely with a configuration setting.
3. 3 Models operate on metadata (ticket statuses, timestamps, hierarchies, assignees) and ticket names/descriptions.
4. 4 Neo.Tax does not access sensitive content such as source code, birth dates, social-security numbers, or employee addresses.
5. 5 Audit-ready, transparent AI: trains on labeled compliance-domain datasets, applies IRS-defined tests to classify engineering work, and generates literal narratives that are traceable, replicable, and reviewable by tax professionals.
6. 6 By design, no black-box outputs: every decision includes a reasoning trace, supporting internal oversight and audit confidence.

Critical vendors meet our standards or don't onboard.

1. 1 Vendors evaluated prior to onboarding against security, privacy, and compliance criteria.
2. 2 Documented list of approved third parties maintained and reviewed.
3. 3 Contractual obligations require breach reporting and protect against unauthorized disclosures.
4. 4 Ongoing monitoring and annual reassessments of vendor agreements and compliance reports.

Single-tenant VPC for enterprises with heightened requirements.

Each environment is instantiated as a single-tenant Virtual Private Cloud: complete segregation of data, compute, and services. No infrastructure shared across tenants. Fully isolated at the network, application, and storage layers.

1. 1 Isolated infrastructure. All Neo.Tax services (application, databases, storage) run in a dedicated environment instantiated per customer. No shared resources.
2. 2 Custom security extensions. Approved security representatives can install network controls (custom firewall rules, IDS, outbound egress filtering) against the underlying cloud resources.
3. 3 Customer-controlled encryption. Support for customer-managed encryption keys (CMKs), including BYOK and other cloud-native KMS. Available upon request.
4. 4 Advanced auditability. Full visibility into system-level activity via isolated logging, with optional export to your SIEM. Available upon request.
5. 5 Private connectivity. Optional private network connections (AWS Direct Connect, site-to-site VPN) and/or IP whitelisting, eliminating public-internet exposure.
6. 6 Operational governance. Define your own backup schedules, maintenance windows, retention policies, and data-residency requirements at the infrastructure level.

On-premise control without sacrificing the elasticity, uptime, or automation of a modern cloud-native SaaS platform.