GARAGENT / TRUST

How Garagent protects your data

Last updated November 3, 2026. Garagent is in invite-only beta.

You are letting AI employees read your files and, if you choose, act in your mail, drive and social accounts. You should know exactly what happens to that information. This page says what we do, who else is involved, and what we do not promise.

Where your information goesYou work in Garagent. Garagent keeps your files and chats in your account. For a task it sends only what is needed to an AI provider. Connected apps such as Gmail go through Composio, which holds the access token. Sending, posting and deleting wait for your approval.Yousign in withGoogleGaragentwhat we run and protectYour files and chats (own folder)Secrets encrypted (AES-256)Approval gatesend · post · delete ask youAI providertheir own termsand policiesComposioholds your appaccess tokensGmail, Drive, …only whata task needsrun and protected by Garagentthird parties, with their own rules
Green is what Garagent runs and protects. Dashed boxes are third parties; we choose them carefully but they follow their own terms.
  1. 1You askGive a task in chat or assign it.
  2. 2It readsOutside text is cleaned and marked as information.
  3. 3You approveChanges, sending, posting and deleting wait for you.
  4. 4It actsOnly the approved action runs, and it is recorded.

Your employees ask before they act

  • Reading runs. Changes ask you first by default, and you can make any employee stricter.
  • Sending, posting and deleting always ask, whatever the setting. You see the exact message or post before it goes.
  • After an employee has read your private files and something written by someone else (a web page, an email), it asks before opening more websites.
  • If what would be saved or sent contains a card number, a password, a secret key or an ID number, the approval card warns you.

Content from the outside is treated as information, not orders

A web page or email can contain hidden text that tries to give an AI instructions. Before an employee reads outside content, Garagent removes hidden characters, marks the text as information to read, and keeps the approval steps above in place. No filter stops every attempt, which is why the approval steps matter most.

Your accounts and connections

  • You sign in with Google. Garagent never holds a Garagent password for you.
  • Connections to services such as Gmail and Google Drive go through Composio, a connection service. You approve access on the provider's own screen, and Composio holds the access token, not Garagent.
  • The few secrets Garagent stores itself (for example a shared mailbox password or a custom tool token) are encrypted with AES-256-GCM, with the key kept outside the database.
  • Secrets, card numbers and ID numbers are masked in our logs and admin screens.
  • You can disconnect an app at any time in Garagent. To cancel access completely, also remove Garagent in that provider's own security settings.

Your files stay in your account

Each account has its own folder, and every download and file action checks that the file belongs to the person asking. We test this across accounts. It is application-level separation, not a separate server for each customer.

Who can see what

Our team and your conversations

Garagent staff use admin tools that hide the content of your chats and tasks. We see your words only when you send them with Report an issue. Staff sign-in is separate from customer sign-in, limited to a short session, and the list of staff is set on our server, not in the database. Suspicious activity is recorded as a security alert for us to review.

AI providers

To do a task, Garagent sends the instructions and the information the task needs to an AI provider (for example Anthropic, OpenAI or Google, sometimes through OpenRouter). Garagent does not train AI models. The providers publish their own terms for paid business use, including that they do not train on API content by default; they may keep requests for a limited time for abuse monitoring. Read their current terms for details, and see our Privacy Policy for the list we maintain.

What we do not claim

  • We do not hold SOC 2, ISO 27001 or HIPAA certification, and have not yet had an independent penetration test.
  • Garagent is not end-to-end encrypted: the server and the AI provider must read the text of a task to do it.
  • Please do not put passwords, payment card numbers or ID numbers into chats or files, and do not use the beta for regulated or safety-critical data.
  • We do not guarantee uptime or recovery during the beta. Keep your own copy of important files.

Your control

To delete your account and files, or to receive a copy of your data, email hello@getgaragent.com. We are building self-service tools for both. To report a vulnerability or something that looks wrong, write to hello@getgaragent.com. Our full Security, Privacy and Terms pages set out the formal terms.