── ── Security & data handling
Client tax data, handled like the record it is.
deciqAI is an advisory engine for accounting firms, which means it holds what firms hold: books, statements, tax documents. The posture, in one paragraph: data is isolated by engagement, never used to train models, every outbound action waits in a human approval queue, and the audit trail is append-only. Traffic is TLS-encrypted, stored integration credentials use AES-256-GCM, and everything runs on AWS in the United States. And the part most vendor pages omit: deciqAI is not yet SOC 2 certified — this page states what is verified, what is scoped, and what is not yet true, in that order.
The due-diligence questions, answered directly
These are the questions a firm's security review actually asks. Where the honest answer is "not yet," the row says so — a security page that only lists strengths is marketing, not disclosure.
Is client data isolated between clients?
In placeYes — files and extracted facts are scoped to the engagement they were uploaded to and visible to the practice that opened it. One client's data is never exposed to another client.
Is customer data used to train AI models?
In placeNo. deciqAI does not train or fine-tune models on customer data. The shared knowledge base is built from public data, licensed datasets and our own annotations — customer workspace data never enters it.
Can the AI send something without a human seeing it?
In placeNo. Outbound actions — emails, documents, calendar changes — queue for explicit one-click approval before anything leaves. Routine document-chase reminders can be set to auto-send, and that is an explicit opt-in, not a default.
Is there an audit trail?
In placeYes — actions are logged and the audit trail is append-only, so a release or withdrawal is recorded as a new event rather than overwriting history.
Who signs the return?
In placeThe licensed professional, always. The system extracts, computes and drafts with source evidence attached; it does not make the filing decision, sign, or file.
Encryption?
Verified scopeTLS encrypts all traffic in transit. Stored integration credentials (OAuth tokens) are encrypted at the application level with AES-256-GCM. We publish here only what we have verified — see the infrastructure section for exactly what that covers.
Where is it hosted?
In placeOn AWS in the United States (us-east-1) — application and database both.
SOC 2?
Not yet — said plainlyNot yet. deciqAI does not currently hold a SOC 2 certification, and we would rather say that plainly than imply otherwise. The controls on this page are what we run today.
Third-party audit or penetration test report?
Not yet — said plainlyNone is available yet. When that changes, this page will say so.
Data deletion?
In placeDisconnecting an integration deletes its stored tokens from our database. Full deletion of remaining account data is available on request to [email protected].
Custody, by design
Isolation by engagement
Files and extracted facts are scoped to the engagement they were uploaded to and visible to the practice that opened it. Clients upload over signed, tokenized links — no account, no password, nothing to install — and the link lands the document in exactly one engagement.
Computation you can check
The engine computes exposure against statutory tables and attaches the source evidence to every field it fills. Anything the documents cannot support is flagged as needing confirmation rather than filled in — a blank you can see beats a guess you can't.
People hold the pen
Client-facing sends queue for one-click approval; the filing decision, the signature and the filing stay with the licensed professional. The CPA/EA workflow is built around §7216 client consent and the FTC Safeguards Rule (16 CFR Part 314) WISP requirement, with IRS Pub. 5708 as the template. Every action logs to an append-only trail.
Infrastructure, stated only as far as verified
deciqAI runs on AWS in the United States (us-east-1) — application servers and database both. All traffic is encrypted in transit with TLS. Stored integration credentials — the OAuth tokens behind connected accounts — are encrypted at the application level with AES-256-GCM, and disconnecting an integration deletes its tokens from our database.
A deliberate note on scope: this page claims encryption exactly where we have verified it and no further. Vendor security pages routinely assert blanket "encrypted at rest and in transit" lines that no one has checked; we think a page a CPA firm relies on for due diligence should be written to the same standard the firm's own workpapers are — every statement traceable to something that was actually inspected. Questions this page doesn't answer belong in your security questionnaire: [email protected].
FAQ
Does deciqAI train AI models on my clients' tax data?
No. deciqAI does not train or fine-tune models on customer data, and customer workspace data never enters the shared knowledge base, which is built from public data, licensed datasets and deciqAI's own annotations. Model inference requests are made to commercial API providers under their business API terms.
Is deciqAI SOC 2 certified?
Not yet, and this page says so directly rather than leaving it ambiguous. What deciqAI runs today: engagement-scoped data isolation, no training on customer data, human approval queues on outbound actions, an append-only audit log, TLS in transit, application-level AES-256-GCM encryption for stored credentials, and AWS hosting in the US. Firms doing vendor due diligence can send their security questionnaire to [email protected].
How does deciqAI handle IRC §7216 and the FTC Safeguards Rule?
The CPA/EA workflow is built around §7216 client consent — client data use in the engagement flow is gated on consent — and around the FTC Safeguards Rule (16 CFR Part 314) written information security plan requirement, for which IRS Pub. 5708 is the template. Every action is logged to an append-only trail.
Do my clients need accounts for document upload, and is the link secure?
Clients upload through a signed, tokenized link scoped to their engagement — no account, no password, nothing to install, and traffic is TLS-encrypted. Files land in the engagement they belong to and are visible only to the practice that opened it.
Can the AI file a return or send client communications on its own?
No. The system computes exposure, drafts documents and flags what the records cannot support — the filing decision, the signature and the filing stay with the licensed professional. Client-facing sends sit in an approval queue until a person releases them; only routine chase reminders can be opted in to auto-send.
What subprocessors does deciqAI use?
The core categories: AWS for hosting (US, us-east-1); Anthropic, OpenAI and Google for model inference under their business API terms; Stripe for payments; and Google APIs only for integrations a user explicitly connects, within the scopes granted. Disconnecting an integration deletes its stored tokens.
How do I report a security issue or request deletion?
Email [email protected]. Deletion requests cover all remaining data associated with the account; disconnecting an individual integration already deletes that integration's stored tokens.
This page describes deciqAI's practices as of August 22, 2026 and is updated when they change. It is a disclosure, not a contract; for engagement-specific terms, see Terms and Privacy.