What stays private to you, what your company can see, and what company owners and admins can and cannot see in Gryz.

Company workspaces are rolling out. Some of this may not be on for your company yet.

Answer first

Your own Gryz stays yours. Your company sees only what you put into the company. Company owners and admins can see company content and what company agents and connected apps did. They cannot see your private space.

Private to you

Your private space: your documents, notes, memory, tasks, skills and collections
Your own agents and their keys
Your own tools cannot read company documents, unless your company turns on connected apps and you add the company to an app yourself
Anything you publish publicly is public, the same as before

Visible to your company

Company documents. Who can open one depends on its project.
A project open to everyone: every member can open its documents and read its memory.
A restricted project: only people who were given access, plus owners and admins.
A document that is in a restricted project: only that project's people, plus its author and owners and admins, even if it is also in an open project.
A document in no project: every member can read and edit it.
Memory saved in a project: shows who, or which agent, saved it, to everyone who can open that project.
The company Memory page: lists memory from the projects you can open. Owners and admins, and managers and editors of a project, can edit or remove any memory in it. An edit keeps the person or agent who first saved it and shows who edited it. Removing a memory wipes its text and the text of every earlier version, and cannot be undone. In a project open to everyone, every member can edit and remove its memories. Activity records who removed one, never its text.
Memory waiting for approval: when a project is set to hold agent memories, a waiting memory is visible only to the people who can decide it: company owners and admins, and managers and editors of that project. Other members, agents and other companies do not see it. The text is wiped when a memory is decided, and an expired memory's text is wiped within a day.
Company tasks: everyone who can open a project sees its tasks: the title, the details, who they are assigned to, the status and the history of changes. Only editors and managers of the project, and owners and admins, can create or change one. A task given to an agent shows that agent's name to everyone who can open the project. The person named to review a task can approve it or send it back, even if they can only view the project. Only the reviewer, or a project manager, can change or remove a named reviewer. If the reviewer's account is deleted, the task still needs a reviewer, and only a project manager can close it. A done or cancelled task that names a reviewer can be reopened only by the reviewer or a project manager.
Company skills: every member can read a skill once it is published: its name, what it is for, its text, its version and which projects it applies to. Only owners and admins write, publish and change them. Drafts and older versions are seen by owners and admins only.
A skill you tag to the company: tagging saves a copy of the skill's current text in the company's workspace for owners and admins to read. The skill stays yours, and later changes to it do not change the copy. Other members cannot see the copy while it waits. If an owner or admin publishes it, everyone in the company and their agents can read it, and the published copy stays if you delete yours. If it is rejected, taken back or expires, the text of the copy is removed.
People: everyone sees each other's names, roles and join dates.

What owners and admins can see

Every project and every document in the company, restricted ones too.
Every task in every project.
Every company skill, including drafts, older versions and archived ones.
Every skill a member tagged for the company, while it waits, with who tagged it.
Every memory in every project, and the earlier versions of a memory that was edited, until it is removed.
Every memory an agent saved that is waiting for approval, in every project, and the Review inbox of what is waiting.
Each member's name, role, sign-in email address, when they last signed in to Gryz, and whether second-step sign-in is on. Also open invitations and the email addresses they went to.
Every company agent: who owns it, what it can do and which projects it has. A plain member sees only their own agents.
Connected apps: which apps members added to the company, for whom, whether each may write, and when each was last used. Owners decide whether apps can reach the company at all, and owners and admins can block an app or remove it for one member or the whole company. They never see a member's private space through it.
The Activity page (see below).
Owners and admins can pause or remove an agent. Only owners change roles and company settings. Admins can invite and remove members, manage projects and see Activity.

What the Activity page shows

Invites, joins, role changes, removals and settings changes
Projects, and who can open them
Documents moved into the company, one line for each (and one for each link into a project), when someone starts or finishes bringing documents in (counts only), password links and Explore listings
Memory saved, edited or deleted in a project, and memory held, approved or rejected (without the text)
Tasks created, given to someone, given a reviewer, or had a reviewer removed or replaced, and who did it (never the title or the text)
Company skills created, published, unpublished, archived or assigned to projects, who did it, and when the company turned skills on or off for agents (never the name or the text)
A skill being tagged, approved, rejected or taken back, and who did it (never the name or the text)
Every status change a company agent makes on a task: the agent, the old and new status, the project and when (never the title or the text)
Whether the approval setting was turned on or off for a project
For each company agent: the agent, the tool it used, the project, whether it worked, and when
For a connected app: which app it was, by the id it registered with Gryz, never the name the app chose for itself
Only if your company turns on "Record which items apps members connect open or list" (on by default in Enterprise; an owner can turn it on in Team too): which items (documents, memories, tasks, skills and projects) one of those apps opened or listed, by its id or short address, never what is in it. Every member is emailed when it is turned on, and records start 7 days later. Company agents people set up with keys are not part of it. A member's app that reads a lot of different items in one day can be paused, and owners are told. To count that daily limit, Gryz keeps which items each member's app read that day and deletes them the next day.
When a company agent reads a skill: which skill and which version. Owners and admins see the skill's name next to it. The text of the skill is never recorded.
For owners and admins, "Guidance fetched by X of Y agents this week": how many active agents fetched their guidance, and the names of those that did not. It does not say the agent acted on it.

Some of these lines show a document's short address, for example when a document is moved in or shared outside the company. None shows a title or the text.

Nobody using Gryz, and no part of the Gryz app, can change or delete these records. The agent lines (which tool an agent or connected app used) are kept for 365 days. The other lines are kept for as long as the company exists. Deleting a whole company removes its history, and deleting a person's account removes their name from it. Each such deletion is itself recorded, with counts only.

While a company has a legal hold, its records are kept past 365 days, nobody can remove company memories, and the company cannot be deleted. A person in it who deletes their account stays in the records as an anonymous former member, and their own data is deleted as usual. Nobody can delete company documents, their earlier versions or comments on them during a hold. People can still edit the documents, and every earlier version is kept. Owners and admins can download these records as a spreadsheet file.

What the Activity page does not record

Which document an agent opened, unless your company records which items apps members connect open or list (see above). Otherwise it records that the agent read a document in a project.
What an agent searched for, or the text of what it saved. It records that a memory was saved.
When a person opens a document.
To keep a document away from an agent, put it in a restricted project and do not give the agent that project.

What nobody in the company can see

Your private space and your own keys.
An agent's key. It is shown once, when it is made, and cannot be looked up later, not even by an owner or admin.
Your chats with your AI tool. Nobody in your company sees them. The company only sees what gets saved.

Agents

A company agent can open only the projects it was given, and never more than its owner can. If its owner loses access to a project, so does the agent, on its next request.
It sees tasks only if a person turned on "Can read tasks" for it, and only in the projects it was given. It creates tasks and updates the ones it created or was given only if a person also turned on "Can read and edit tasks". It can also take a task nobody has, within a limit of 50 open tasks.
It reads company skills only if your company turned on "Agents can use company skills" and a person turned on "Can read company skills" for it. It gets only published skills that apply to a project it was given. It cannot write or change a skill. Turning the company switch off stops its very next request.
An agent never closes a task. When it finishes one, the task goes to "Needs review" and a person decides. Activity records every status change an agent makes.
A company agent never reaches your private space.
Connected apps: if your company turns them on, an app you connect to your own Gryz can also reach the companies you add to it, one company at a time. It starts read only. It can write in a company only if the company allows writing and you tick "Allow writing" for that company yourself, and only when it names that company. In the company it shows as the app and your name, for example "Claude, via Ann", with the projects you can open, minus any project marked "no connected apps". While it can see a company, that app cannot publish public documents, cannot call your other connected tools, and can only change, comment on or suggest changes to your own private documents that are not shared. If a company keeps its data separate, the app can only read your private space and your other companies while it can see that company. A company you join later is not added for you. Where Gryz shows the single Allow screen, it lists your companies when you connect an app, and the app reaches only the ones you leave ticked there. When you connect it again, only the companies it already had start ticked, so a company you joined since starts unticked. The others stay paused for that app. If the company turns connected apps off or stops approving the app, or you sign the app out, the company is paused for that app until you add it again. A company can also end an app's access after a set number of days, or ask you to sign in to Gryz again.
A company agent's key stops working 365 days after it was made. With the Enterprise policy it stops after 90 days, but never sooner than 14 days after the company switched. Its owner gets an email first.

If someone leaves

Their company access ends right away.
Open invitations addressed to them are cancelled.
Their company agents and keys are shut off, their connected apps lose the company, and their project access is removed.
Documents they wrote stay in the company. They can no longer open them, except a document that has an open public link, which anyone can still read. Memory they saved stays too.
Their personal account and everything in it are not touched.

When you move a document in

The document becomes the company's. It cannot be moved back out.
People you shared it with outside the company lose access. It leaves any collections, and its comments and likes are deleted.
Pictures from other websites do not load in company documents.
A document with a PIN cannot be moved in. A public document can be moved in only if the company allows public links.

When you bring your work in

Before anything moves, Gryz shows a plain summary, for example "42 documents, 3 projects, 0 agents", and every link that would end: shared links, public links, password links (documents with a PIN) and collection pages. It lists up to 10 of your own titles for each. It never shows document text.
When a new project is made from one of your personal projects, up to 5 of its links are copied into it, and the summary says how many.
Nothing moves until you confirm. If the numbers change before you confirm, Gryz shows them again and moves nothing.
Only documents you wrote can move. Moved documents cannot be moved back out, not by you and not by an owner or admin.
A moved document goes where you choose: a project you can edit, or no project, which means everyone in the company can read and edit it.
Memory is copied only if you tick each memory and choose a project. You see how many will be copied first. Your original stays with you, the copy shows you as the person who saved it, and private memory of your personal agents is never copied.
An agent you bring in is a new company agent with its own key, shown once. It can read project memory and see projects, and nothing else until you give it more. Your personal agent and its key are not touched.
Your answer to the card that offers this is private to you. Owners and admins cannot see it.
Activity records when you start and finish and when you copy memory (counts only, never the text), and also one line for each document moved and each link into a project, showing the document's short address and never its title.
Steps and limits are in Bring your work into a company.

Password link: a document can be shared with a password link that expires within 30 days, if your company allows password links.
Open public link: anyone with the address can read a public document, only if your company turned on public links. They are off by default.
Only the author, owners and admins make a password link. Only owners and admins list a public document on Explore.

Gryz support

When you ask Gryz for help, Gryz support can act on company data, for example adding or removing members, and those actions appear in Activity as "Gryz support".

Gryz itself

Gryz measures how the product is used, for example which pages are viewed. Document content is never sent. Your company does not see this data. Read the privacy policy for the details.

Daily seals (Enterprise)

With "Seal the record each day" on, Gryz seals each finished day (UTC) of the company's agent lines and item records with a fingerprint chained to the day before, and checks the last 7 days every day. If a sealed day no longer matches, owners and admins see it on the Connected apps page. A seal shows a change made after the day was sealed. It cannot prove anything against someone with full access to the database, who could also rewrite the seals.

How a day is sealed, so you can check an export: for each agent line of the day, ordered by its id, the fields id, agent, connection, tool, outcome, project, origin, skill id, skill version, app id and verified app, and the time in microseconds since 1970, joined by | (an empty field stays empty), one line each, joined by a line break and hashed with SHA-256. The item records are hashed the same way (id, call, agent, tool, kind, item, time). The seal is the SHA-256 of the previous seal (or start), the company id, the day, the number of agent lines, their hash, the number of item records and their hash, joined by |.

Which tools count as opening or listing items: get_document, list_documents, fetch, search, recall, list_memories, get_task, list_tasks, get_skill, list_skills, get_project (the project and the documents it lists), list_projects and the agent's own start-of-session read (the projects they list). Writing tools are not counted.

What is private in a company workspace