Privacy Policy

5. work.studio Browser Extension

The work.studio browser extension, for Chrome, Microsoft Edge, Firefox and Safari, lets you work with your work.studio projects on the web page in front of you. This section describes what it accesses, what it sends, and what it stores.

What the extension accesses

The extension reads nothing before you sign in, and reads a website only after you bind that site to one of your projects. When you bind a site, your browser asks you to grant access to it; removing the binding gives that access back.

When you ask about a bound page, run an action on it, or the assistant reads it while carrying out something you asked, the extension collects from that page:

• its address and title;
• its visible content and structure, its form fields with their current values, and its buttons, tabs and links;
• any text you have selected on the page, and any files you choose to attach;
• your question.

For Google Docs, Sheets and Slides, whose content cannot be read from the page itself, the extension reads the text of the document you have open through Google's own export of that document, using your existing Google session.

What it sends, and to whom

• The information above is sent only to work.studio, when you ask about a page or an action runs on it.
• When you sign in, your email address and organization are received in your sign-in token and used to authorize your requests.
• While your browser is open, the extension contacts work.studio about once a minute to keep your assistant session active and to check for approvals assigned to you. These requests contain no page content.
• To answer a request, work.studio sends the page content and your question to the AI model provider configured for the assistant, which processes them to produce the response.

The extension contains no analytics, advertising or tracking code, and does not run code downloaded from a server.

What it stores

• In your browser: your settings and the sites you have bound, until you remove them or uninstall the extension. Your sign-in tokens and the conversation shown in the panel are kept in session storage, which your browser clears when it closes.
• At work.studio: conversations started from the extension are saved with the project they belong to, so they appear in that project's history like conversations started in work.studio itself. To have them deleted, see our Data Deletion page.

How this information is used

Information collected by the extension is used only to provide its features: answering your questions, comparing and capturing pages, proposing form values for you to review, and showing your approvals. We do not sell it, use it for advertising, or use it to determine creditworthiness or for lending purposes, and we do not transfer it to third parties except as described above to provide those features.

The use of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

6. Google Workspace data

If you connect your Google account, work.studio works with your Gmail on your behalf. This section describes what we access, how it is used, how long it is kept, and how to take that access back. It applies in addition to the rest of this policy.

What we access

Nothing until you connect Google and grant permission, and then only when you ask for something. Specifically, work.studio:

• reads the messages and threads you ask about, or that match a search you type, so the assistant can answer, summarise or draft a reply;
• creates drafts for you to review and edit, and sends a message only when you send it;
• applies or removes your own labels and archives messages, at your instruction.

We do not permanently delete your mail, and we do not change your Gmail settings.

How it is used, and who else sees it

• Message content is used only to provide the feature you asked for.
• To produce a summary or a draft, the content of the messages concerned and your request are sent to the AI model provider configured for your workspace, which processes them to return the response.
• Your Google data is not used to develop, improve or train generalised artificial intelligence or machine learning models.
• We do not sell it, use it for advertising, or use it to determine creditworthiness or for lending purposes.
• No person at work.studio reads your Google data, except where you have given specific consent (for example, when you ask us to look at a problem), where it is necessary for security purposes such as investigating abuse, where the law requires it, or where the data has been aggregated and made anonymous.

How long it is kept

• Message content is processed to fulfil your request and is not retained afterwards.
• Conversations you start are saved with the project they belong to, so you can find them again. A summary or draft you asked for may therefore quote the message it was based on. To have these deleted, see our Data Deletion page.
• Your Google credentials are stored encrypted, isolated to your account, and are used only to make the calls described above.

Taking access back

Disconnect Google in work.studio, or remove work.studio at myaccount.google.com/permissions. Either revokes our access immediately; we delete the stored credentials, and features that depend on Gmail stop working until you connect again.

Limited Use

work.studio's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.