Governance is what your security team actually checks: who can do what, what gets logged, how long it stays, and how to get your data out. This page is the short version. The technical depth lives on /security/architecture.
Admin roles
Every workspace has an owner, admins, and members. Owners and admins can invite, remove, and change roles for teammates; members can use Cole and view their own data. Role changes are recorded in the audit log. We will be adding custom roles for the Enterprise plan later this year.
Audit log
Workspace admins can see and export the audit log from Settings → Security. Each entry records the actor, the action, the target, the timestamp, and where the request came from (channel, IP). We retain audit logs for one year on the Free and Starter plans, and for the contracted retention window on Enterprise.
Operational application logs (separate from the audit log) are retained for 30 days. PII fields are redacted at write-time using a fixed allow-list maintained in our codebase.
Data retention
We retain customer data for the duration of your contract. After deletion of your workspace, live data is destroyed cryptographically: we delete the per-workspace key that unlocks it, so even our backups become unreadable as they roll out of the 30-day backup window. You receive a signed deletion certificate by email. You can verify the certificate yourself at /security/verify-deletion.
Role-based access (Pocodot internal)
Internally, access to production systems and to customer data follows the principle of least privilege. Production access requires multi-factor authentication. Access reviews happen at least every six months. Access for any departing teammate is revoked within one business day; for involuntary departures, immediately.
Connected integrations
Every integration uses the upstream vendor's official login (OAuth) with the narrowest permission scopes possible. Tokens are encrypted at rest. You can see and revoke any integration from Settings → Connected integrations. The full list of scopes Pocodot requests from each platform is documented on each integration's setup page; for Slack specifically, see the "What Pocodot sees in your Slack" section on /security.
Data export
Click "Download my data" in your settings. You'll get a single zip file with everything Pocodot knows about you - conversations, tasks, memories, and integration metadata. The export is generated on demand and is available for 24 hours.
Bring-your-own-key (BYOK) - Enterprise roadmap
Enterprise customers will be able to bring their own KMS key (AWS, GCP, or Azure) to wrap their workspace's data-encryption key. Revoking the key in your KMS makes your workspace immediately unreadable, even to us. This is on our roadmap for the Enterprise plan; talk to security@pocodot.ai if you need it sequenced into a contract.
Regional data residency
Today, all customer data lives on secure servers in Singapore. Enterprise customers can choose the United States, Europe, or Asia-Pacific. See /security/dedicated for the full Enterprise data-residency options.
Sub-processor controls
You can see every company that helps us run Pocodot at /subprocessors. We give 30 days' notice - by in-product banner and direct email to your billing contact - before adding any new sub-processor. Enterprise customers can require explicit written approval before any new sub-processor is added to their workspace.