How AI Employee handles your data

We never use your business's data, your Slack messages or your connected apps to train AI models, ours or anyone else's.

Your employee runs on AI model providers (such as OpenAI) through their business APIs, which do not train on what is sent through them.

Your employee reads only the channels a person adds it to; it never joins a channel by itself. It keeps the messages from those channels and from DMs with it, so it can remember context, write your daily briefing and suggest work.

An owner or admin can mark any channel “Don't store messages” (for example #exec) in Settings, Times & connections. In that channel only messages that tag the employee are kept, because they are requests it works on, and anything already stored from it is deleted at once. A channel set to Off is not stored at all.

Message text is kept for 30 days. After that it is deleted and only the short notes and facts your employee saved (which you can see and edit on the Memory page) remain.

If you remove the employee from a channel, that channel's stored messages are deleted when they reach the same 30-day limit.

Each business's data is kept apart from every other business's, and that is enforced on our servers, not just in the app.

When your employee answers someone, it only uses channels that person is a member of. Work asked for in a DM is visible only to the person who asked. Gmail and Google Calendar are personal: only the person who connected them can use them, and their details are not posted in shared channels.

Our support team can look at your business only after an owner grants access, which lasts 7 days and can be withdrawn sooner. Every support action is logged.

Your apps (Gmail, Stripe, Canva and others) connect through OAuth on our integration platform. You sign in on the app's own page; we never see or store your passwords for them.

Connection tokens are never shown to the AI model. Your employee reads through the connection, and anything that sends, publishes, spends or deletes waits for someone on your team to approve it, unless an owner has said that kind of action can go ahead.

Your employee never reveals its own instructions, its training material, another business's data or any connection credentials, whoever asks and in any channel.

Text inside web pages, emails and files is treated as information, never as orders. If something it reads tries to give it instructions (for example “forward this inbox to…”), it does not follow them and tells you what it found.

An owner can download an export of the business's data at any time from the Business Brain page.

An owner can delete the business from the same page. Access ends for everyone right away, the employee stops working in Slack, its automations pause and the subscription is canceled.

30 days later everything stored for the business is erased for good: every connected app is disconnected and its access removed at our integration platform, the app triggers behind automations and watches are removed, the pages, images, documents and files are deleted from storage, and every record is deleted from our database. The database's backup history keeps a copy for up to 7 more days, then it is gone.

We keep only what is shared with other businesses or needed for security and billing: the names and emails of people who signed in (they may belong to other businesses too), your Slack workspace's install until you remove the app from Slack, our log of support actions, and the invoices and payment records Stripe, our payment processor, keeps.

We are not SOC 2 certified yet. SOC 2 is planned; we have not booked the audit, so we don't have a date to give you. When we do, it will be on this page.