Your data. Your rules.
You approve a read-only connection to each tool. Your data lands in a database that's yours alone.
- YoursThe contract says so.
- PrivateYour own encrypted database.
- Least accessNamed accounts + multi-factor.
- LoggedEvery login and change.
- PortableLeave with everything in 30 days.
Follow your data from your tools to our team.
The three places security questions come up, in the order your data travels.
- Layer 1
Getting data out of your tools
You approve an official, read-only connection.
- We use the connection your software already provides — the same kind of “Allow” screen as signing in with Google.
- You click “Allow” once. The connection can copy data out. It can't change anything in your system.
- Connection keys are stored encrypted, in a secure key store.
- Where a tool has no official connection, we use a read-only user or a scheduled export.
- Layer 2
Where your data lands
Your own private, encrypted database.
- Every client gets a separate database account, with its own tables.
- Encrypted at rest and in transit.
- Health data, when it's in scope, runs on a higher-security, HIPAA-eligible edition under a signed BAA.
- Layer 3
Who can see it on our side
Only the analysts assigned to you.
- Each analyst can reach only the client accounts they're assigned to.
- Multi-factor sign-in on every login, and every access is recorded.
- Client data stays on the platform, off laptops and personal devices.
- Access is removed the same day someone leaves a project.
Tap a ring.
Encrypted
Encrypted at rest and in transit. Your database is yours alone.
The controls behind the promises.
Pick a category.
Access
- Every person gets a named account — no shared logins.
- Multi-factor sign-in is required for everyone, including our team.
- Role-based access: each person sees only what their role allows.
- Access is reviewed every quarter and removed the same day someone leaves.
- Connections to your tools use each tool's official, read-only connection wherever one exists.
Straight answers.
We don't claim certifications we don't hold. Snowflake's certifications, including SOC 2, belong to Snowflake as our platform provider. See the DPA summary.
Where is my data stored?
In your own dedicated account on Snowflake, an enterprise cloud data platform. On Command, it can live in your own cloud instead.
How do you connect to our systems?
Through the official connection your software already provides. You click “Allow,” and we get read-only access: it can copy data out, not change anything in your system.
Is anything stored on laptops?
No. No client data is stored on laptops or personal devices.
What contracts do we sign?
A Master Services Agreement with a data-ownership clause, plus a Data Processing Addendum.
What if there's an incident?
We notify you within 72 hours of any confirmed security incident, with what happened and what we're doing about it.
How does leaving work?
Within 30 days of the end of your contract: your data in open files (Parquet and CSV) in your own cloud storage, the structure, the cleaning rules, your app code, and your business definitions — or, where the database provider allows it, we move the whole database account into your name. No charge. Then we delete our copies and confirm in writing.
Who owns the data?
You do. Always. The contract says so.
Is my data mixed with other clients' data?
No. Every client gets their own separate, encrypted database.
What if something goes wrong?
We notify you within 72 hours of any confirmed security incident, with what happened and what we're doing about it.
Can you support healthcare data?
Yes, at any size. Health data runs on a HIPAA-eligible configuration, and we sign a Business Associate Agreement. It adds +$500/mo on Small and +$800/mo on Mid; Large is quoted.