Most CRM breaches don’t hit the CRM, they hit a third-party app that mishandled its access tokens. Here is exactly how the Zaags assistant connects to your Salesforce, and what keeps your data safe.
The assistant signs in through your own Connected App that you create in Salesforce, using OAuth 2.0 with PKCE. We never hold an admin password, and you can revoke the connection from Salesforce at any time.
We request the minimum scopes only (api refresh_token offline_access openid), never “Full access”, “View All Data” or “Modify All Data”. The assistant can read only a short allowlist of objects and fields, and can only create Cases, Case Comments, Leads and Tasks, it can never edit or delete your data.
Access keys are stored encrypted (AES-256), never in plain text, never in our database in clear, and never shared with anyone. The Consumer Secret is optional: use a public (PKCE) Connected App and Zaags stores no secret at all. If you use a confidential app, the secret is encrypted at rest and never leaves our server.
When you disconnect, we call Salesforce to invalidate the tokens, a copied token cannot be reused later.
Before revealing anything personal, a customer is verified with a one-time passcode matched against your Salesforce contacts. No verification, no personal data.
We use the standard API, no managed package, no code deployed into your Salesforce org. Setup takes about ten minutes and every action is written to an audit log.
Every call from the assistant comes from a single IP. Lock your connection to it so only we can use it:
Security is shared. These settings live in Salesforce, we recommend them all, and our setup guide walks you through each:
209.16.158.237 so only we can use the connection.Your keys are yours, encrypted, least-privilege, revocable in one click, and only ever used from one address, with a customer identity check before any personal data is shared. If a vendor can’t explain that simply, they shouldn’t hold your keys.