Skip to content

Privacy

Privacy policy.

What we collect, why, where it lives, and what you can ask us to do with it.

Last updated 24 October 2026

The short version

We collect the data you give us to run your workspace and the technical data needed to keep it secure. We do not sell your data. We do not train AI models on your data.

We hold no third party privacy certification or audit yet. If a specific regime applies to you, ask us what we do about it before you sign up rather than after: the answer will be what is written on this page.

If you want a deep read, the full policy is below. If you have a question, email privacy@workwrk.com.

1. Information we collect

Account data. Name, email, role, organization. Voluntarily provided when you sign up or are invited.

Workspace data. Everything you put into workwrk: people, KPIs, OKRs, SOPs, tasks, kudos. Scoped to your workspace, and reachable only by people you have given access to it.

Technical data. IP, user agent, device type, session timestamps. Used for security, auth, and incident response.

Consent records. When you dismiss the cookie notice we keep a record that it was shown, under the random id the wwrk_consent cookie holds, with the time, your IP address and your user agent, and your country and region when the request carries them. It is kept whether or not you have an account.

Demo and contact requests. When you ask for a demo or write to us, we receive what you send: for a demo, your name, work email, company, team size, industry and what you want to see. It goes by email to our sales mailbox and is used only to answer you; it is not stored in the product. Email privacy@workwrk.com and we delete it.

2. How we use it

We use your data only to (a) run your workspace, (b) keep it secure and (c) bill you. We do not use your workspace content for advertising or generic-purpose AI training, and we run no product analytics over it.

3. AI features and your data

workwrk uses AI for search, triage, and summarization, through a third party model provider. Your workspace content is sent to that provider when someone in your workspace triggers an AI action, and on a schedule only for AI features your workspace sets up to run on one, such as scheduled agents, the routines people set up for their AI teammates, and scheduled AI updates in Talk. We do not send it for training, and we do not use your workspace content to train anything of our own. An Owner or Admin can turn AI features off for the whole workspace.

AI teammates work as the person using them and can see and change only what that person can. What a teammate is asked to remember is kept for that person, who can see and delete it in the teammate's Memory tab, and a routine runs only on the schedule its person set. Anything other people would see, such as a post in Talk or a comment on a shared task, waits for that person's approval unless they chose otherwise.

If an Owner or Admin turns it on for your workspace, you can connect your own Google account to your AI teammates, for Gmail, Google Calendar or both. Only you can connect it, and it is used only in your own chats and routines with the teammates you allow, never when a teammate answers in Talk, for an automation or for another teammate. A teammate reads your email or calendar only when it uses one of those tools in an answer, and again when you approve what it asked, to check that the email conversation is still there or that the event has not changed since it asked. It never opens attachments. To find a time to meet, it can also read, through your account, when up to five colleagues in your workspace are busy, never what they are doing. Nobody else in your workspace can use your connection or read what a teammate read for you. Sending an email, replying, answering an invitation or inviting anyone always waits for your approval. What a teammate reads in your email or calendar is sent to our model provider to answer you; we do not send it for training, and we do not use it to train any model.

We keep your Google tokens encrypted, with the address of the Google account you connected, which only you are shown. Of what a teammate reads, we keep only a count of what it found, and what it wrote back to you, which stays in your chat with it and in your run history, as every teammate answer does. A request it asks you to approve keeps what it would send or change, such as who an email goes to and every word of it, as every teammate request does. When you disconnect, when you leave or are deactivated in the workspace, and when the workspace is deleted, we delete the tokens and, unless the same Google account is still connected elsewhere in WorkwrK, ask Google to remove WorkwrK's access. You can disconnect at any time in your settings, under Calendar & connections.

WorkwrK'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. We do not use data from Google Workspace APIs to develop, improve or train generalized AI or machine learning models.

If an Owner or Admin turns it on for your workspace, which needs the Growth plan or above, an AI teammate can use a web browser for you, in your own chats with it. The browser runs on a server WorkwrK runs for these browsers alone, apart from the servers that hold your workspace, for that one chat and is never shared: nobody else, an Owner or Admin included, can watch it, use it or reach what you sign in to in it, and it is closed and deleted when the teammate finishes, after a few idle minutes, or at its time limit. A teammate opens only the sites your workspace and that teammate allow, and never private or internal addresses. It opens and reads pages at once; every click, every word it types and every choice waits for your approval on a card that shows the page. The words a page shows are sent to our model provider to answer you, never a picture of the page; we do not send them for training, and we do not use them to train any model. A teammate never types into a field it recognises as one for a password, a one-time code or a card number, and never sees what you type in a page's fields: to sign in or pay, you take over the browser yourself while the teammate sees nothing, and it is told only whether you finished, then may read the page as you left it. It cannot download or upload files, and no sign-in you make in it is kept after the browser closes.

For you alone, we keep a list of the steps a teammate took in the browser, the kind of step, the site, how it went and when, for 30 days. Pictures of pages shown on its cards and in your chat are kept encrypted for 24 hours, for you alone, and are not in our backups. We never keep the text of the pages it read; what it wrote back to you, and which sites it used, stay in your chat with it and in your run history, as every teammate answer does. A request it asks you to approve keeps what it would do, such as the words it would type, as every teammate request does. Once the browser closes, that server keeps no copy of the pages it opened, the picture of it you watched or what you typed when you took it over. While the browser runs, its own cache, cookies and site storage sit on a disk kept only in memory, for that browser alone, and are gone when it closes. About the browsers and the people who use them, the server keeps only these: counts, such as how many browsers are running; the codes that name each browser and when it ran, until an hour after it closes; a system log of events, such as a browser starting or closing or a view of one opening, which holds none of those codes, no network address and nothing from a page, for at most 15 days; and, in its memory alone, the network addresses of the people who watch or use a browser, to limit how often each may try. Owners and Admins see in the audit log which sites a teammate opened for you and what kind of steps it took, never what it read or typed.

If an Owner or Admin also turns on teaching by showing, you can show an AI teammate how to do a job by doing it once in its browser. While you do it, we keep which pages you visit, by their site and the start of their address, the words on the buttons, links and other controls you click, and which fields and lists you use. The steps never keep what you type in a field or which option you choose while you do it, nothing about a field we recognise as a password, code or card field, and nothing inside a box from another site, such as most card forms: those become steps you do yourself each time. The words on a button or link can name a person or a record; you see every one when you review the steps, and can remove it. A picture of each page you visit, which can show what is on it, what you typed or chose included, is kept for you alone for 24 hours. Your teammate sees nothing while you record. You then review the steps and choose for each field whether it asks you each time or types the same words you give it; only once you save them can it use the skill. It follows a skill as a guide, reading each page as it is at the time, and still asks before every click, every word it types and every choice; some sites save or send what is in a field as soon as it is filled in, and a request that fills in fields for a skill says so. The names of your skills and what each is for, and a skill's steps while it follows one, are sent to our model provider to answer you, as pages are, and never for training. A skill is yours alone, for that one teammate: nobody else, an Owner or Admin included, can see it, use it or copy it, and a teammate uses it only when you ask in your own chat with it, never by itself, since a skill's routine only reminds you. Owners and Admins see in the audit log when you recorded, saved, changed or deleted a skill or made a routine from one, with its number of steps and its sites, never its name or its steps, and how many skills the workspace keeps and by how many people; they can delete every skill in the workspace without seeing any.

You can connect an AI app that you use, such as Claude, ChatGPT, Cursor or VS Code, to WorkwrK when an Owner or Admin of your workspace allows it. You choose the workspace, and whether the app may only read or may also make changes. It works as you: it sees and changes only what you can, it can never delete anything, and every change it makes is recorded with its name. What it reads, and what you send through it, goes to the company that makes that app and to the AI model the app uses, which another company may run, under their own terms; we do not control what they keep. We send nothing until you choose Allow, and you can disconnect it at any time in My settings, Calendar & connections, which ends its access at once. Logging out everywhere, or changing your password, disconnects it too; logging out of one browser does not. We keep the app's name and the addresses it returns to, and when you connected it and last used it, until 90 days after the connection ends, and how many requests it made and how many things it made or changed each day for 90 days. The audit log records when each app was connected and when it was disconnected, and each change it made, with the app's name, the network address the change came from and the app's user agent, the line each request carries to say which program sent it, and keeps them for as long as the rest of the log. Owners and Admins of the workspace you chose can see that log, and how many apps are connected there and how many requests they made and things they made or changed today. Your Security activity, in My settings, lists when your apps were connected and disconnected, and a task's activity, which anyone who can open the task sees, names the app with each change it made there. We also send you a notice in your Inbox when an app is connected, and when one is disconnected for safety, and keep it until you delete it. If you delete your account, your connections and their daily counts are deleted at once, and the audit log keeps its rows about your apps under Deleted User, without the network address or the user agent.

Which providers we use, and what their own retention terms say, is a question we will answer in writing before you sign up.

4. Who we share with

We use a small number of sub-processors to run the service: hosting providers for our servers, among them the one where AI teammates' browsers run when a workspace turns them on, a payment processor, a transactional email provider and a model provider for the AI features. We will give you the current list, by name, in writing, before you sign up or at any point after.

An AI app you connect yourself is not one of our sub-processors: you choose it, and its company, and the company that runs the AI model it uses, receive what you let it read under their own terms.

When a workspace turns them on, AI teammates' browsers also reach three other companies, from WorkwrK's browser server and never from your device. To find each site it opens, a browser asks Cloudflare (1.1.1.1) and Quad9 (9.9.9.9), which see the names of those sites. Chrome, the browser they run, checks the pages it opens with Google Safe Browsing and fetches its own updates and settings from Google. We turn off Chrome's password leak checks, autofill, sync, usage reports and sign-in.

Email privacy@workwrk.com and ask for the sub-processor list. We will also tell you when it changes.

5. Your rights

You can ask us to give you a copy of your personal data, correct it, delete it, or stop a particular use of it. Email privacy@workwrk.com and say which. We will not ask you to justify the request.

Two of these you do not need us for: a workspace administrator can export the workspace's people, tasks, Docs, SOPs, Tables, Goals and review cycles, and can delete the workspace, from inside the product, without contacting anyone. Files and attachments, images inside Docs, canvases, forms, chat, Doc comments and review answers are not in the export yet; ask us for a copy of those.

6. Retention

Account data is retained for the life of your subscription. After termination, when you delete the workspace, or when we close it (from 7 October 2026), we retain workspace data for 30 days (in case you reactivate), then permanently delete it, with the files it stored. Some files uploaded before 6 October 2026 were not recorded against the workspace they were for, so the deletion cannot tell them apart and keeps them: email privacy@workwrk.com and we delete them by hand. Backups keep a copy for at most 90 days, so a deleted workspace is gone from them within 90 days of its deletion.

Google connection tokens are deleted when you disconnect or leave, as above; if Google has not yet confirmed that WorkwrK's access is removed, one encrypted token is kept until it does, for at most seven days. Our encrypted backups hold the encrypted tokens too, for at most 90 days, as above. What a teammate wrote back to you stays in your chat with it and in your run history, and its requests stay as every teammate request does, until you delete your account, which erases their words at once for most histories, or within a few days for a very long one.

A teammate's browser steps are deleted 30 days after they were taken, and pictures of pages 24 hours after they were taken. Our encrypted backups hold the steps, as they hold every other record, for at most 90 days, and never the pictures.

A skill is kept until you delete it, an Owner or Admin deletes every skill in the workspace, or your account or the workspace is erased. If you leave the workspace or are deactivated, or its teammate is removed, the skill is deleted 30 days later, unless you or the teammate come back before then; until then a removed teammate's skills stay listed for you to delete, in its settings and in your account. Our encrypted backups hold a skill, as they hold every other record, for at most 90 days after it is deleted. Pictures taken while you record are deleted after 24 hours, as other pictures of pages, and are never in our backups.

Billing data is retained for 7 years per accounting requirements.

7. Where your data lives

There is one deployment, and you do not choose a region for it. If where your data is stored is a requirement for you, ask us before you sign up rather than after.

An AI teammate's browser runs on WorkwrK's own server, in one region for this deployment, which Owners and Admins see in Settings, Apps & modules. The names of the sites it looks up, and Chrome's checks and updates with Google, go to the companies section 4 names, which may answer from outside that region.

8. Contact

Privacy questions: privacy@workwrk.com

Mailing address: WorkwrK Technologies, WeWork ETV, Bellandur, Bengaluru 560103, India.