Security & trust

A dedicated machine. Your data kept separate.

Built like infrastructure, not a feature. You’re handing an operator the keys to your business, so keeping your data separate, data ownership and a record of what Andy does were designed in from day one rather than patched on after launch.

How one Andy is wiredYour systems, on the left, connect to a dedicated machine we run for you. That machine holds the AI, supplied the way you choose, the memory of your business, and the credentials you grant, with access restricted to our systems. It reads from and acts inside your systems directly. By default, sending, paying and deleting stop at an approval gate and only go ahead after you sign off, and you set those rules. Other customers run on their own machines, and your data is kept separate from theirs.ANOTHER CUSTOMER · SEPARATE MACHINEANOTHER CUSTOMER · SEPARATE MACHINEYOUR SYSTEMSreads and actsYour AndyA dedicated machine we run for you.Your choice of AIyour Claude plan, your own key, or oursMemory of your businesspeople, decisions, how you like things doneProtected credentialsaccess restricted to our systemsTHE GATEYour approval rulesSend, pay or delete waitsfor you by default.Sent, posted, paidin your name, under your rules
The rule that matters most

The human approval gate.

By default, nothing is sent, published, paid or deleted without a person saying go. Andy drafts, stages and proposes. A human approves. The approval rules are yours to set, and out of the box the gate sits in front of:

Routine housekeeping runs on its own: labeling, sorting and archiving email, and adding, moving or updating calendar entries, including the automatic updates your calendar sends to attendees. Reading, summarizing and drafting need no sign-off either. You can tighten or loosen these rules any time, by asking Andy or in its settings, and every change to them is logged. We recommend keeping approval for payments and for anything sent outside your organization. You can see what the default looks like in practice on the how it works page: every send, payment and deletion waits for your approval before it runs.

The architecture

Eight controls, built in.

Separation

A dedicated machine, your data kept separate

Every customer runs on a dedicated cloud machine that we operate for them, and your data is kept separate from other customers’ data. Your memory, files and prompts are not pooled with anyone else’s, and customers are separated by machine, not by a checkbox in a database.

That machine is where everything about your deployment lives: the memory, the files, the credentials, the rules. Keeping your data separate isn’t a security add-on. It is how the whole product is built.

See what runs on that machine
Secrets

Restricted credentials

The access credentials you grant are stored with access restricted to Andy Labs’ systems and kept separate from every other customer’s. Data moves encrypted over TLS 1.2 or higher.

Ownership

Your data and memory are yours

You own your data, the memory built from it, your customizations, and everything Andy produces for you. You also choose how the AI is supplied: your own Claude subscription (the default), your own Anthropic API key, or AI we supply, and you can switch any time.

Access control

Least privilege by default

Andy only gets the integrations you grant, with the scopes you approve. By default, sending, posting, paying and deleting wait for explicit confirmation, and you set those rules.

Auditability

A record of what Andy did

Andy keeps a record of what it did, and every change to your approval rules is logged. Not a black box.

Data residency

Hosted in the region you choose

Memory, files and history live on the dedicated machine we run for you, in the region you choose from the ones we offer, including your own country. Data held there stays in that region. Content sent to the AI model for each task is processed where the AI provider operates, currently the United States.

Resilience

Updates without the drama

Improvements roll out with nothing for you to do. If an update affects one of your customizations, we tell you in advance where we can and help you adjust it.

No lock-in

Portable by design

Your data and memory are yours, and there is no minimum term. Ask for an export any time, not just when you leave, and you get it in common, usable formats. You can also buy out your Andy and have us move it to infrastructure in your own name. The relationship is built on the work it does, not on trapping your data.

In plain language

What that means day to day.

Built by people who handle sensitive data. Andy Labs grew out of running a real business under strict privacy law, where careless data handling isn’t an option. You can see that company running on Andy today on the proof page. Health information, payment card data and other special-category data stay out of Andy unless we have both signed an addendum for it.
The paperwork

A real entity, and a real contract.

Architecture is only half of trust. The other half is who you are actually signing with, and what that document says about your data.

Andy Labs LLC

A registered Wyoming company. You contract with a real legal entity, not a handshake and a Stripe link. More on who is behind it on the about page.

One Customer Agreement

One plain-English Customer Agreement, in writing before anything is set up: what we run for you, what happens if you stop, and who owns what. You read it before you sign it.

Your data, in writing

How your data is handled, where it lives, which providers touch it, and what happens to it when the relationship ends are all in the agreement. If you need a GDPR data processing addendum, it is available on request.

You get the full agreement before you sign anything. If your counsel wants changes, that conversation happens first.

Security FAQ

The hard questions, answered.

How is my data separated from other customers?

Every customer runs on a dedicated machine we run for them, with its own memory, files and credentials, and your data is kept separate from other customers’ data. Their data is not on the machine we run for you, and yours is not on theirs.

Can Andy send or delete things on its own?

You set the boundaries. By default, sending an email or message, posting or sharing anything outside your organization, making a payment and deleting data all wait for your approval, so Andy drafts and proposes but you decide. Routine housekeeping, like sorting and archiving email and keeping your calendar up to date, runs on its own. Andy won’t touch systems you haven’t granted. The approval rules are yours to set. You can tighten or loosen them any time, by asking Andy or in its settings, and every change to them is logged.

Am I locked into one AI vendor?

No. You choose how the AI is supplied: your own Claude subscription (the default), your own Anthropic API key, or AI we supply, and you can switch any time. The rest has no lock-in either. Your data and memory are yours, you can export them any time, or you can buy out your Andy and we move it to infrastructure in your own name.

More questions? The full FAQ lives on the get started page, and every one of them is fair game on the demo call.

Ask us the hard security questions on the demo call.

Book a demo