What Collet can see, and how we protect it.
Read, don't touch.
Collet reads from your systems to see how they're set up. It never changes them: no revoking access, no editing settings, no surprises. Where a vendor has no read-only permission, we tell you exactly what we ask for and why.
What we access
Collet only reads. This is every permission it asks for, the vendor's name for it, and why Collet needs it.
| Source | Permission | Why |
|---|---|---|
| Google Workspace | View users admin.directory.user.readonly | Your employee directory, and who has been suspended |
| Google Workspace | User security settings admin.directory.user.security | Lists the third-party apps people have authorized. Google has no read-only version of this permission. Collet never changes or revokes anything |
| Google Workspace | View audit reports admin.reports.audit.readonly | Sign-in and app authorization activity |
| Slack | Read users users:readusers:read.email | Members and deactivated accounts |
| Slack | Admin admin | Seat data and app install history, which Slack only gives to admins. Requires a workspace admin to install |
| Claude | None | Member list is a file you upload |
How we protect it
- Connection credentials are encrypted with a dedicated key, used only by the background sync process, and never written to logs.
- Each customer's data is kept separate from every other customer's at the storage layer.
- Collet runs on AWS, with production in its own account that holds no other company's or product's systems.
This website
This site runs no scripts, sets no cookies, and loads nothing from anyone else. Every page, font, and image comes from meetcollet.io. The only record of your visit is the standard access log our hosting keeps, which we delete after 90 days. The privacy policy has the details.
Report a vulnerability
Email security@meetcollet.io. Tell us what you found and how to reproduce it.