Roles
The Controller decides what tenant data Guvern analyses and why. The Processor processes that data only on the Controller's behalf. Each party complies with the data protection laws that apply to it, including the EU and UK GDPR and US state privacy laws where relevant. Where the CCPA applies, the Processor acts as a "service provider" and does not sell or share the data.
Scope, nature and purpose
- Purpose: to assess, monitor and, when approved, remediate the governance of the Controller's Microsoft 365 tenant, and to report the results.
- Nature: reading metadata through Microsoft APIs under the Controller's admin consent; storing, analyzing (including with AI) and reporting it; and, only for approved remediation jobs, changing settings or permissions.
- Duration: for as long as the Controller uses the service, then as set out under deletion and return.
Data and data subjects
Categories of personal data
- user and guest identifiers, names and email addresses
- group and team memberships
- permission and sharing metadata, including sharing links
- site, library, file and folder names and paths
- account status and activity dates
- Copilot license assignment and usage data
- Conversation Analysis only: Copilot prompts and responses
The free scan and standard analyses do not read the content of files. Conversation Analysis runs only when the Controller buys it and grants the extra permission.
Data subjects
The Controller's employees, contractors and guest users who have accounts in, or content shared through, the tenant.
Instructions
The Processor processes personal data only on the Controller's documented instructions. The Terms of Service, the packages the Controller buys, its admin consent and any approved remediation plan are those instructions. The Processor will tell the Controller if it believes an instruction breaks data protection law.
Confidentiality
Everyone at the Processor who can access the data is bound by confidentiality and has access only as needed for their role.
Security
The Processor keeps the technical and organisational measures in Annex 1, and may improve them over time without lowering the overall level of protection.
Subprocessors
The Controller authorizes the subprocessors in Annex 2. The Processor binds each one to data protection terms at least as protective as this agreement and remains responsible for them. It will give reasonable advance notice of a new subprocessor. The Controller may object on reasonable data protection grounds; if the parties cannot resolve the objection, the Controller may end the affected service.
Assistance
The Processor helps the Controller, as far as it reasonably can, to answer data subject requests, carry out data protection impact assessments and consult regulators. It passes on any request it receives directly from a data subject about tenant data.
Personal data breaches
The Processor notifies the Controller promptly, and in any case without undue delay, after becoming aware of a personal data breach affecting tenant data. The notice describes what happened, the data and people affected, likely consequences and the steps taken. The Processor keeps the Controller updated as it learns more.
Deletion and return
- Raw scan data is purged promptly after report delivery, and each deletion is logged.
- Reports and findings are deleted promptly after the service ends, unless the Controller asks for a copy first.
- The Controller can ask for earlier deletion at any time. The Processor confirms deletion in writing on request.
- Where the Controller keeps data in its own Azure subscription, that data stays under the Controller's control.
Audits
The Processor makes available the information reasonably needed to show compliance with this agreement. The Controller may audit once a year, with reasonable advance notice, at its own cost, during business hours and under confidentiality.
International transfers
The Processor processes data in the United States, in the Microsoft Azure region we use, which the Processor will tell the Controller on request. For transfers of personal data from the EU, UK or Switzerland, the parties rely on the European Commission's Standard Contractual Clauses (Module 2, controller to processor) and the UK Addendum, which are incorporated by reference.
Order of precedence
If this agreement conflicts with the Terms of Service on data protection, this agreement wins. If the Standard Contractual Clauses apply and conflict with this agreement, the Clauses win.
Annex 1: Security measures
- Identity: multi-tenant Microsoft Entra ID app; access to the Controller's tenant only through the permissions the Controller's administrator consented to; removable by the Controller at any time.
- Least privilege: the free scan requests read-only permissions; extra permissions only for packages that need them.
- Encryption: TLS in transit; encryption at rest in Microsoft Azure.
- Secrets: credentials held in managed secret stores, never in code.
- Access control: staff access limited by role, with sign-in through Microsoft Entra ID and multi-factor authentication.
- Data minimisation: metadata only, no file content (except Conversation Analysis); raw data purged after delivery with a deletion log.
- Change control: no change to the Controller's tenant without a simulated change plan approved in writing.
- Logging and incident response: activity and deletion logs; a documented incident response process.
Annex 2: Subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Microsoft Corporation | Azure hosting and database, Dataverse, Microsoft 365 email | Provided on request |
| Stripe, Inc. | Payments and billing (billing contacts only) | Provided on request |
| Anthropic PBC | AI analysis of findings and, for Conversation Analysis, of Copilot interactions | Provided on request |
| Website analytics provider | Cookie-free website analytics (site visitors only) | Provided on request |