Security and data
How we handle estate documents
The short answers to what firms ask first, then every control and the providers we use. We launch early next year, so each control shows whether it is already built and tested or will be running before launch.
Where does our clients’ data go?
Into private, encrypted storage in the United States, visible only to the firm or executor who uploaded it. It is used only to provide the service ordered: never sold, never used for marketing.
Does AI touch our clients’ data?
AI reads the statements: Microsoft Azure Document Intelligence turns each page into text and numbers, and Microsoft doesn’t use that data to train its models. No document or figure is ever sent to a chatbot-style AI (a large language model). Every balance and total is calculated by fixed rules and must reconcile to the cent. Anything that doesn’t match is flagged for you to check, with the original statement page and the line highlighted.
How long do you keep it?
Statements and figures are deleted 7 days after the package is delivered or 30 days after the first upload, whichever comes first. Billing and audit records are kept as business records.
Do you have a SOC 2 report?
Not yet. Our hosting, database, storage and document-reading providers hold their own SOC 2 or ISO 27001 reports. An independent penetration test comes first after launch, then a SOC 2 audit.
What about the preview?
The preview uses a fictional estate. It stores nothing except the feedback you choose to send.
Can we get a data processing agreement?
Yes. A data processing agreement will be available to firms before launch. Ask at firms@theaiexecutor.com.
Controls
| Control | What we do | Status |
|---|---|---|
| Encryption in transit | Every connection uses TLS (HTTPS). The app forces HTTPS with HSTS. | Built |
| Encryption at rest | Uploaded files are stored in private Amazon S3 storage, encrypted at rest by AWS. The database (Supabase Postgres) is encrypted at rest. | Built |
| Who can see a file | Each firm and each executor can see only their own estates. This is enforced inside the database (row-level security), not just in the screens, and it is covered by automated tests. | Built |
| Sign-in | Accounts are managed by Clerk. Two-step sign-in (MFA) is required for every user, who chooses the method: a passkey (face, fingerprint or PIN), an authenticator app or a text message. Sessions end after 1 hour of inactivity and after 12 hours at most. | Before launch |
| Uploads | Every file is virus-scanned and its type checked on arrival. Upload links are private and expire shortly after they are issued. | Built |
| Bot protection | Public forms are protected by Cloudflare Turnstile. | Built |
| Card payments | Card details go straight to Stripe and never touch our servers. | Built |
| Error monitoring | Errors are reported to Sentry with personal data switched off and scrubbed before sending. | Built |
| Audit trail | Key actions (uploads, corrections, approvals, payments, deliveries) are written to an audit log with who and when. | Built |
| Retention | Statements, figures and other documents are deleted 7 days after the package is delivered or 30 days after the first upload, whichever comes first. The customer keeps a signed copy of their own file to continue later. Receipts are kept until sent with the Account, then deleted 30 days after that Account is delivered. Billing and audit records are kept as business records. | Before launch |
| AI models | AI reads the statements: Microsoft Azure Document Intelligence, a document-reading service, turns each page into text and numbers; Microsoft does not use this data to train its models. No customer document or figure is ever sent to a large language model (chatbot-style AI). Every balance and total is calculated by fixed rules and must reconcile to the cent; anything that does not match is flagged for the customer to check against the original page. | Built |
| Secrets | Passwords and keys are kept in the hosting provider's secret store and a password manager, never in code or email. | Built |
| Security checks | An automated security review of the code runs every day. Independent penetration testing follows launch. | |
| Insurance | Cyber and errors-and-omissions insurance, starting on launch day. | Before launch |
| Breach notice | If personal information is exposed, affected customers are told without undue delay, and regulators as the law requires. | Before launch |
| Data use | Customer data is used only to provide the service the customer ordered. It is never sold, never used for marketing, and never shared except with the sub-processors listed below to run the service. | Built |
Providers we use
These providers process data only to run the service.
| Provider | Purpose | Location |
|---|---|---|
| Render | Hosting for the website and application | United States |
| Supabase | Database | United States |
| Amazon Web Services (S3) | Encrypted file storage | United States |
| Microsoft Azure Document Intelligence | Reading statement pages | United States |
| Clerk | Sign-in and accounts | United States |
| Stripe | Card payments | United States |
| Resend | Transactional email | United States |
| Sentry | Error monitoring (personal data scrubbed) | United States |
| Better Stack | Uptime monitoring (no customer data) | Being confirmed |
| Cloudflare (Turnstile) | Bot protection on forms | Global |
| Microsoft 365 | Company email | United States |
Found a security problem? Email security@theaiexecutor.com. Updated 8 October 2026.