Security approach
OutreachAI is built to separate public pages from authenticated workspace features and to keep sensitive workflow actions behind application access controls. Security work is treated as an ongoing operational responsibility.
Security
Security
A plain-language overview of OutreachAI security boundaries, authenticated access, human approval, data handling, and responsible reporting.
Last updated
July 31, 2026
These pages describe the public website and application terms at a product level. They do not add certifications, guarantees, or company details that are not represented elsewhere in the product.
Authentication and access
Protected product areas require authentication. Users should keep account credentials, connected provider accounts, and workspace access limited to people who need them.
Human approval boundaries
AI-assisted sales work is intended to remain reviewable before sensitive actions. Users should verify generated content, recipients, CRM changes, and campaign details before approval.
Generated emails are drafts first. Sending requires an approved email and a verified recipient path in the application.
Data handling
Application data may be processed by the systems required to run OutreachAI, including hosting, authentication, payments, observability, connected integrations, and AI functionality. Access should be limited to operational need.
Reporting concerns
If you believe you have found a security issue, report it through the confirmed support email listed on this site. Please avoid accessing, changing, deleting, or sharing data that does not belong to you.
No absolute guarantee
No internet service can promise perfect security. OutreachAI aims to use reasonable safeguards and improve them as the product changes.