Privacy policy
What AgOS collects, what it does with it, who else receives it and how long it is kept.
Last updated
In short
- Anyone who uses AgOS is subject to this policy.
- AgOS collects your account details, what your team adds and asks, activity from the tools you connect, feedback and usage.
- We use that data to run AgOS and to train and improve it.
- We may sell data to third-party vendors. Before any data is sold, we anonymize it.
- Parts of your data go to the services AgOS runs on, such as AI model providers, to do the work you ask for.
Who this policy applies to
This policy covers AgOS (“we”, “us”): the AgOS apps, AgOS Cloud, Isolated Cloud and this website.
Anyone who uses AgOS is subject to this policy. That includes people who create an account, people invited into a workspace and people who visit this website. By using AgOS, you agree to how it collects and uses data as this policy describes.
What we collect
- Account details: your email address, name and profile picture, how you sign in, and when you last signed in and were active. A password is stored only as a hash.
- Your organization: the workspace name, its email domain, members and their roles, invitations and requests to join.
- What your team adds: documents, Knowledge pages and their history, issues, comments, attachments and people records.
- What you ask: your questions, the answers and the sources they cite.
- Connected tools: messages, emails, calendar events, files and repository activity from the tools your workspace connects.
- Feedback: ratings on answers and suggestions, and reports sent with the feedback button, which can include a screenshot.
- Usage and billing: how many model tokens your workspace and each person use, and your plan and subscription status.
- Activity records: sign-ins, changes and agent actions, with who did them and when.
Each item, where it comes from and what it is used for is listed on Data we collect.
How we use it
- To run AgOS: index your documents, answer questions with citations, and run agents, which can hold emails, bookings and outside tool calls until a person approves them.
- To keep context: your recent conversation, a private memory for each person and a shared memory for each project.
- To train and improve AgOS, as described below.
- To meter usage against your plan’s allowances and to bill for it.
- To keep accounts safe: lock sign-in after repeated failed passwords and record who did what.
- To send service email: sign-up verification, password resets, invitations and workspace notices.
How each of these works is on How we use data.
Training and improving AgOS
We use the data collected through AgOS to train and improve AgOS.
Today, AgOS improves without retraining a model. When you rate an answer or a suggestion, the rating is kept as a lesson, together with the situation it judged. When AgOS meets a similar situation later, it looks those lessons up and shows the model what worked and what did not. Lessons from your chats are used only in your chats, and lessons from a project only in that project.
Ratings are also stored with the conversations they belong to, so that conversations and their ratings can be used as training data. Reports sent with the feedback button are read to find and fix problems.
Anonymized data and third-party vendors
We may sell data collected through AgOS to third-party vendors.
Before any data is sold, we anonymize it. We remove names, email addresses and other details that identify a person or an organization, so that the data a vendor receives no longer identifies you, your colleagues or your organization.
How we protect it
- Every row of workspace data carries its organization’s ID, and row-level security in the database enforces it on every query. On Isolated Cloud, your data also sits in a database of its own.
- Stored connection credentials and keys are encrypted with AES-256-GCM.
- Passwords are stored as scrypt hashes, and sign-in locks for 15 minutes after 10 failed attempts.
- Password reset, email verification and invitation links are stored only as hashes. Verification links expire after a day and invitations after a week.
- Uploaded files are kept in private storage and open through signed links that expire.
- Application logs mask email addresses and some phone and ID number formats, and hide fields that hold secrets.
- Emails, bookings and outside tool calls that agents prepare can wait in Approvals for a person.
How long we keep it
- Workspace data is kept for as long as the workspace exists.
- Ending a trial or canceling a plan deletes nothing. The workspace stays readable and can be exported, and new changes pause until a plan is active.
- Deleting a workspace closes it to everyone at once. Its data is kept, so the deletion can be undone; removing the data for good is a separate step. To ask for it, email support@agos.digital.
- Removing a person from a workspace ends their access to it. Their AgOS account stays, because one account can belong to several workspaces.
- Some records outlast what they describe. Usage records, ratings kept as lessons, feedback reports and activity records stay after the message, account or item they refer to is deleted.
- Hourly usage records are deleted after 8 days.
Your choices
- Use your own model key. A workspace can send its model requests to its own Anthropic, OpenAI or Ollama account instead of the bundled model.
- Choose what to connect. Your workspace decides which tools AgOS connects to.
- Keep actions for a person. Emails, bookings and outside tool calls can wait in Approvals.
- Keep pages private. Nothing in Knowledge is public until someone with edit rights publishes it, and publishing can be turned off at any time.
- Export pages. Knowledge pages you can read can be exported.
- Ask us. To see, correct or delete data about you, or to delete your account, email support@agos.digital.
Changes to this policy
When this policy changes, we update this page and the date at the top of it.
Contact
Questions about this policy or about your data go to support@agos.digital.