Data & Security
Built so a person approves everything before it goes out.
Most AI tools route your client data through servers you don't control, under terms you didn't negotiate. W&S is built differently. AI drafting runs through a disclosed provider we name in your engagement, and we show you exactly where your data flows before you sign. On-premise inference is on our roadmap; we will tell you where your deployment runs today. And nothing goes out on its own: a person on your team approves every outbound action before it sends, enforced by the system, not by policy.
How we handle your data
Seven commitments, plainly stated.
We show you exactly where your data flows.
AI drafting runs through a disclosed provider we name in your engagement, never silently. We map and document the data path before you sign, and W&S is built so inference can move on-premise as that becomes part of your engagement.
A person approves every outbound action.
Paige drafts; she never sends on her own. A reviewer on your team reads, edits, or rejects every draft before it goes out. That approval gate is enforced by the system, not by a policy we ask you to remember.
Your data is stored encrypted, per client.
Paige keeps your data in an encrypted database, separated per client at the application layer, so the system only ever works within your own data. We retain it for the engagement so Paige can reference prior context, and we delete it on request. When we log in remotely to update your system, we connect to the automation configuration, not to your inbox. Content is sent to our disclosed AI provider only to complete the task.
The data path is mapped and documented.
At setup we map and document the exact data path, including where your data is stored and our disclosed AI provider, and show your team how to verify it. Our management connection monitors system health, software versions, and queue depth.
You own the credentials.
Every OAuth token, API key, and access credential we configure is issued to you, not to us. If you cancel, you retain access to everything. We don't hold credentials you can't revoke.
Remote access is scoped and logged.
When we connect remotely to update or improve your automation, we use a minimal permission connection limited to the automation system. We document every remote session in a shared log you can review.
You get a written audit runbook.
Every install ships with a client owned audit runbook: what is logged and where, who has access, patch cadence, encryption, and the incident process. It answers the questions an IT or compliance reviewer will ask, and it shows your team how to re-verify the setup any time.
What we can honestly say
We don't make compliance claims we can't back up. Here is the plain-English status of every security posture a prospective client has asked us about.
| Claim | Status | What it means |
|---|---|---|
| Disclosed AI provider | Live | AI drafting routes through OpenRouter (a disclosed subprocessor). We can sign a data processing agreement that fixes retention terms for your engagement. We map and document the data path in your runbook before you sign. On-premise inference is a roadmap item; we will tell you where your deployment runs today. |
| Encrypted per-client storage | Live | Paige keeps your data in an encrypted database, separated per client at the application layer, for the engagement, and deletes it on request. Content is sent to our disclosed provider only to complete the task. |
| Credential ownership | Live | You hold all API keys and OAuth tokens. Fully revocable if you cancel. |
| Remote access logging | Live | Every remote session documented in a log shared with the client. |
| E&O insurance | In progress | W&S Consulting LLC is a registered Georgia LLC, effective May 2026. E&O coverage is being procured. |
| AICPA SOC 2 | Not applicable | SOC 2 certifies a cloud provider's controls. Our disclosed AI provider (OpenRouter) is a named subprocessor whose own terms we share with you, rather than W&S operated infrastructure your IT team would audit directly. |
| HIPAA | Scoped per engagement | Paige stores the data it processes in an encrypted, per-client database, so a PHI workload would place PHI in that path. For PHI workloads we scope the data path explicitly with your compliance reviewer before onboarding. Contact us before onboarding if your practice handles PHI. |
Why disclosure changes the security calculus
Cloud AI tools have one vendor controlling your data. You read their privacy policy, accept their terms, and hope for the best when there is a breach. Your data is part of a shared infrastructure someone else manages, and you often cannot say exactly where it goes.
We name our provider in writing, document the data path, and put a person on your team in front of every send. On-premise inference is on our roadmap, and we will tell you exactly where your deployment runs today, before you sign anything.
The tradeoff: you need us to come in person to set it up and maintain it. That is a feature, not a bug. It means we know exactly what we shipped, and so do you.
Security questions we get
Can Paige send an email without a human approving it?
What happens to my data if I cancel?
Can W&S read my clients' emails?
What happens when something breaks?
Do you use any third-party AI services?
Is this appropriate for CPA firms with client PII?
Still have questions about data handling?