Permissions we ask for
Minimum necessary access. Every capability explained.
Anthouse discovers applications from evidence your platforms already keep. Read permissions collect bounded activity evidence; the only management permission is used for an explicit administrator-requested revocation. Every connection remains revocable from the source platform.
Least privilegeNo browser extensionExplicit admin actionsRevocable at sourceFrankfurt control plane
Google Workspaceadmin.reports.audit.readonly
Why we need itReads the OAuth audit log: which third-party apps your people authorised, with what permissions, and when. This is how apps are discovered. The same report lists documents shared outside the company.
What it readsApp names, client IDs, permission scopes, the authorising user's email, timestamps; document titles, owners and sharing changes.
What it never readsMail bodies, Drive file contents, calendar details, documents.
Google Workspaceadmin.directory.user.security
Why we need itLets an administrator revoke a third-party app's token for a user — the Revoke access button. Used only on an explicit click, never automatically.
What it readsNothing beyond the token being revoked.
What it never readsUser passwords, 2-step settings, or any content.
Google Workspacechrome.management.reports.readonly
Why we need itReads Chrome Enterprise usage reports: which SaaS and AI apps managed browsers reached, how often, and by whom — the only way to see an AI tool used with a personal account on a company browser.
What it readsApp name, domain, visit counts, first/last use, the employee's email for managed profiles.
What it never readsPage contents, form data, prompts, downloads — usage counts only. Unmanaged browsers report nothing.
Google Workspaceopenid · email
Why we need itConfirms which Workspace domain is connecting so your data lands in your own workspace.
What it readsThe connecting admin's email address and domain.
What it never readsProfile data beyond the address.
GitHub (App install)contents:read · metadata:read · deployments:read
Why we need itLists repositories, reads the files that fingerprint AI tools (CLAUDE.md, .cursorrules, generator markers) and deployment records. Read-only by GitHub's own permission model.
What it readsRepository names, file paths and marker files, deployment events, committer names.
What it never readsIt cannot write, open pull requests, or change settings. Private source stays private — we read markers, we do not store your code.
Vercel · Netlify · CloudflareRead-only API token
Why we need itLists projects and deployments with the deployer's identity, framework and domains — the hosted apps a grant-based scan cannot see.
What it readsProject names, URLs, deployer, framework, timestamps.
What it never readsEnvironment variables, secrets, or build output. Where a platform offers no read-only token, the interface says so.
Slacklinks:read (one event: link_shared)
Why we need itSlack tells us when someone posts a link to an AI builder or artifact domain we registered — the poster, the channel and the link.
What it readsOnly links to the registered AI domains, who posted them and where.
What it never readsMessage text, channel history, files. Slack does not send us anything else.
Microsoft EntraDirectory.Read.All (admin consent)
Why we need itReads the directory's enterprise-application grants — the Microsoft equivalent of the Google audit log.
What it readsApplication registrations, granted permissions, assigned users.
What it never readsMail, files, Teams messages, or any content.
The one thing we can change
Revoking a third-party app's access to your Google Workspace. It happens only when an administrator presses Revoke access, confirms who is affected, and it is recorded — with their name — in the evidence trail. Nothing revokes automatically.
Data handling
Connector tokens use AES-256-GCM envelope encryption; their data keys are wrapped by a dedicated AWS KMS key in Frankfurt and are never displayed after connection. Evidence is isolated by organization membership and role—not inferred from an email domain. Disconnecting a source revokes the Anthouse connection, while the source administrator retains independent control from the provider console.