Security & privacy
How Plugsight protects your logins, what it stores and never keeps, what it asks Google and Microsoft for, and how to report an issue.
Your connected accounts hold your business. This section explains exactly how Plugsight treats them.
In short
- Your logins are encrypted. Connection credentials (sign-in tokens, app passwords, API tokens) are encrypted with AES-256-GCM before they're saved. They never reach your AI.
- Your data is read live, not stored. Emails, tickets and reports are fetched when you or your AI ask, passed to your AI app, and not kept.
- Your AI reads until you allow more. Changes are off for every account until you switch them on, and each one needs your approval in the chat.
- You see everything. Activity records every sign-in, settings change and AI request, without email bodies or report contents, for one year.
- Each account is isolated. One customer's AI apps can never reach another customer's accounts.
- You can cut access at any time, in Plugsight or at the provider.
In this section
- How credentials are stored: encryption, password hashing, keys and sessions.
- What Plugsight stores and logs: what's kept, what isn't, and for how long.
- Permissions Plugsight asks Google and Microsoft for: each permission, and why.
- Remove Plugsight's access: in Plugsight, in your AI apps and at Google, Microsoft and other providers.
- Security issues and the privacy policy: how to tell us, and where to find the privacy policy.
Was this page helpful?