Security is the whole premise of this product — here's how we approach it, both in Integration Lens itself and on this website.
Last updated: July 18, 2026
Integration Lens is a managed package that runs entirely inside your Salesforce org. There's no middleware to deploy, no external server processing your data, and no copy of your records held outside Salesforce. Every Integration Log, Inspection Result, and Integration Config lives as a standard custom object in your own org.
The one exception to "nothing leaves Salesforce" is alerting: if you configure a Slack or Microsoft Teams webhook URL, Integration Lens posts a short status message — job/endpoint/limit name, status, and a short error message where relevant — to that channel when an alert fires. It never sends full request or response payloads. Both channels are off by default, are configured per org from the Job Alerts tab, and can be turned off at any time. Salesforce in-app notifications never leave the platform at all.
If you believe you've found a security issue in Integration Lens or on this website, please email security@integrationlens.com with details. We ask that you give us a reasonable opportunity to investigate and address the issue before any public disclosure, and we won't take legal action against good-faith, non-destructive security research.
Separately from the Integration Lens product, this marketing website collects demo request submissions (name, email, company, and message) and stores them in a managed Postgres database with restricted access. See our Privacy Policy for details on what's collected and why.
For anything else security-related — questions about our practices, a concern about how your information was handled, or general inquiries — reach out to security@integrationlens.com and we'll follow up promptly.
Integration Lens