Connecting GitHub, Slack, Jira, or any other integration means handing Clypp access to a tool that matters to your business. Here is what actually happens to the credentials behind that connection.
Encrypted at rest
Every credential behind a connected integration — OAuth tokens included — is encrypted at rest using AES-256-GCM before it is stored.
Scoped to your organization
Integrations are connected and stored per organization, not per user. A credential connected inside one organization is never accessible from another, even if the same person belongs to both.
Tip
Our setup guides walk through the exact OAuth scopes each integration requests, so you know what access you are granting before you connect.