Everything on this page is taken from our Privacy Policy, mostly word for word. If this page and the policy ever differ, the policy wins.
Google and Microsoft sign-in and calendar
You choose which accounts to connect, and we request only the permissions needed for the features you turn on.
| Provider | What Worker accesses | What Worker writes back |
|---|---|---|
| Google: sign in with Google | Your name, email address, and profile picture, used to create your account and sign you in | Nothing |
| Google: Google Calendar | Events on your Google Calendar, including title, start and end time, attendees, description, and meeting link. Calendar access only: we do not request access to Gmail, Google Drive, or any other Google service | A link to the Worker meeting page, added to the description of your calendar events. Worker does not change the time, attendees or any other content of an event, and attendees are not notified. |
| Microsoft: sign in with Microsoft | Your name, email address, and profile picture from your work or school Microsoft account, used to create your account and sign you in | Nothing |
| Microsoft: Microsoft 365 Calendar | Events on your Microsoft 365 (Outlook) calendar, including title, start and end time, attendees, description, and meeting link. Calendar access only: we do not request access to your Outlook mail, OneDrive, SharePoint, Teams chats, or any other Microsoft 365 service. Depending on your organization’s settings, your Microsoft administrator may need to approve Worker before you can connect | Nothing. Worker does not create, change, or delete events on your Microsoft 365 calendar |
We use this data “only to provide the features you turn on: today, signing you in, preparing pre-meeting briefs, linking meetings to your weekly meeting agendas, and showing your upcoming meetings inside Worker. We use it for nothing else.” (Section 4.1)
What Worker does not do
- Worker does not join meetings, does not deploy a bot or a recorder, and does not itself create an audio or video recording of any conversation. (Section 4)
- Data from your Google and Microsoft connections is never used to develop, train, evaluate, or improve generalized or non-personalized artificial intelligence or machine learning models, whether ours or a third party’s, on any plan and regardless of your account settings. We do not sell it, do not use it for advertising, and do not disclose it other than to the sub-processors that process it on our behalf. (Section 4.1)
- Worker does not make decisions about you based solely on automated processing or profiling that produce a legal or similarly significant effect on you. Our models propose owners, deadlines, and follow-ups; a person decides. (Section 7)
- Commitment records are not a performance-management instrument. Worker does not use them to evaluate, score, rank, or rate any individual. (Section 7)
Your content and AI
We state this in full, because the answer differs by plan and by whose data it is. (Section 6.1)
- Free and self-serve plans. We use your content to train, evaluate, and improve our own models by default. This includes Meeting and Commitment Data and the outputs our models generate from it. You can turn this off at any time in your account settings, and turning it off applies from that point onwards.
- Paid plans. We do not use your identifiable content to train or improve any model unless you opt in in writing. We do use de-identified and aggregate data derived from your content, as described in Section 6.2 of the policy.
- People who are not Worker users. We never use identifiable content about an individual who is not a Worker user to train a model.
- Model providers. We do not permit our third-party model providers to train on your content. Our contracts with them prohibit it.
- Connected accounts. None of the above applies to data from Google and Microsoft. It is never used to train, evaluate, or improve any model, on any plan, regardless of your account settings.
Turn it off any time
You can disconnect any account at any time in Worker at My Connections, then Disconnect, or revoke Worker’s access directly with the provider: Google account permissions or Microsoft My Apps. Where your organization approved Worker centrally, your Microsoft administrator can remove its access for your whole organization.
Disconnecting an account stops all further access, and the events and invitations we hold from that account are deleted within 30 days. Briefs and commitment records already created remain available to you and can be deleted by you or your account administrator at any time. Deleting your Worker account deletes all of them. (Section 4.1)
How long we keep data
| Data class | Retention | Deletion trigger |
|---|---|---|
| Meeting audio | Not retained. Worker does not create or store audio recordings | Not applicable |
| Transcripts and meeting artefacts as ingested | 30 days | Automatic; immediately on customer deletion |
| Calendar events and invitations as ingested from a connected account | 30 days, rolling | Automatic; no new data is received after the account is disconnected |
| Extracted commitment records | Life of the account plus 30 days | Customer deletion; account termination |
| Reconciliation artefacts from email, chat, calendar, and CRM | 30 days, rolling | Automatic |
| Pre-meeting briefs and weekly receipts | 12 months | Customer deletion |
| Account, billing, and support records | 7 years | Statutory retention periods |
| Security and access logs | 12 months | Automatic |
| Content retained in connection with a suspected breach of our Terms | Up to 2 years | Automatic |
| De-identified and aggregate data | Retained indefinitely | Not applicable. See Section 6.2 |
From Section 10 of our Privacy Policy, which also explains what deleting a commitment record removes.
How we protect your data
We maintain administrative, technical, and physical safeguards designed to protect personal data. Our security program covers:
- Security policies and governance
- Access controls
- Personnel screening and training
- Encryption in transit and at rest
- Endpoint protection
- Vulnerability management
- Data management
- Logging, monitoring and incident response
- Third-party vendor management
We will share current details, including the status of any certification, on request at privacy@worker.ai. (Section 11)
The full details
- Sub-processors: every third party that processes data for us, with what it does.
- Privacy Policy, Terms & conditions and Cookie policy.
- Privacy questions and requests: privacy@worker.ai.