Data we collect and how we use it

Data we collect

Your account

• Email address, name and profile picture. From sign-up, or from the service you sign in with, such as Google or GitHub. Used to sign you in, show who did what and send you account email.
• Password. If you sign up with one. Stored only as a scrypt hash and used to check your sign-in.
• Sign-in records. The sign-in methods your account uses, when you last signed in and were last active, and each successful or failed sign-in. Used to lock sign-in after repeated failures and to show activity.

Your organization

• Workspace name, web address and email domain. Set at sign-up. The domain lets colleagues with the same business email ask to join; a workspace created from a personal address is invitation only.
• Members, roles, invitations and join requests. Managed by owners and admins, and used to decide who can see and change what. An invitation stores the invited email address and role.

What your team adds

• Documents. PDF, DOCX, PPTX, Markdown and text files. Split into sections and indexed, so answers can cite the exact passage.
• Knowledge pages. Pages your team writes, with their earlier versions. Used for answers and shown to the people allowed to read them.
• Work. Issues, boards, comments and attachments in Workspaces. Used to track delivery and to suggest what to do about delays.
• People records. Names, titles, managers, teams, start and end dates and onboarding steps in People. Used for the directory, the org chart and onboarding checklists.

What you ask

• Questions and answers. Your chats with AgOS, with the sources each answer cites. Used to answer follow-ups and to keep your chat history.
• Question log. Each question asked in the workspace and whether it got a cited answer. Used to show new teammates what the team has been asking, limited to questions a check has marked safe to show, and to point out topics your documents do not cover yet.
• Personal memory. A short summary AgOS keeps for each person, rewritten from their chats. Used only in that person’s answers.
• Team memory. A project’s glossary, conventions and recurring decisions, distilled from its comments. Used in suggestions for that project. It holds team-level facts only, nothing about individual people.

Connected tools

• Messages, emails, calendar events, files and repository activity. From the tools your workspace connects: Slack, Gmail, Google Calendar, Google Drive, GitHub and MCP servers. AgOS records the people, events and open commitments in this activity, so it can answer questions such as what is due and who promised it, and forecast.
• Connection credentials. Created when someone connects a tool. Encrypted, and used only to reach that tool for your workspace.

Feedback

• Ratings. A thumbs up or down on an answer or a suggestion, with an optional reason and comment. Used to train and improve AgOS, as described in Training and improving AgOS.
• Feedback reports. A bug, feature request or design issue sent with the feedback button: a title, a description, an optional screenshot, and the page address, app, window size, screen density, browser, language, time zone and time. Used to reproduce and fix what you report. Screenshots are never added to what AgOS searches.

Usage and billing

• Model usage. Tokens and requests on the bundled model, per workspace and per person, by hour and by month. Used for the 5-hour, 7-day and monthly allowances and to show each person their share. A workspace’s own model key is never metered.
• Plan and payments. Your plan, subscription status and trial end date, and the references a payment processor gives your account and subscription. Payment details go to the payment processor; AgOS does not store card numbers.

Activity records

• Changes and actions. Who changed what and when, what agents did and what waited for approval. Used for the audit trail, the Activity page and Approvals.
• Decision records. Only if the decision layer is switched on: which choice was made and how confident it was. The task data it judged is not stored.

Cookies

• Sign-in cookies. The AgOS apps use cookies only to sign you in, and this website sets none. The details are in Cookies and this website.

How we use data

Answering with citations

When you add a document, AgOS splits it into sections and sends their text to an embedding provider, which returns a numeric fingerprint of each section’s meaning. When you ask a question, AgOS fingerprints it the same way, finds the closest sections, adds related records from your connected tools, and sends them with your question to the language model. The answer lists the sections it used. If they do not hold the answer, AgOS says so instead of guessing.

Agents and approvals

Agents use the same data to research, draft, schedule, track tasks and forecast. An agent that researches the web sends its search queries to a web search provider. Sending an email, booking something or calling an outside tool can wait in Approvals, where a person sees what AgOS will do and why, then approves or declines.

Memory

AgOS keeps the recent turns of a conversation so follow-ups work, a short private memory for each person, and a shared memory for each project. A project’s memory is shown on its summary page, where the team can read and correct it.

Training and improving AgOS

We use the data collected through AgOS to train and improve AgOS. Today that happens without retraining a model: a rating is kept as a lesson, and when AgOS meets a similar situation it looks those lessons up and shows the model what worked and what did not. Lessons from your chats stay in your chats, and lessons from a project stay in that project. Conversations are stored with their ratings so they can also be used as training data. The policy is in Training and improving AgOS.

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 by removing names, email addresses and other details that identify a person or an organization. The policy is in Anonymized data and third-party vendors.

Usage, limits and billing

Usage records set the bundled model’s allowances and show each person their share. When an allowance runs out, requests on the bundled model pause until its window resets. A payment processor handles checkout and payment.

Security

Sign-in records lock sign-in after repeated failed passwords, and activity records show who did what and when. The safeguards are listed in How we protect it.

Email

AgOS sends sign-up verification, password resets and invitations. When your workspace sets it up, it also sends onboarding reminders and emails that agents prepare.

Who else receives data

The services AgOS runs on, and what each one receives, are listed in Who else receives data.