This page exists to set the public baseline honestly: what the site states about security controls, what kinds of data the product touches, and how deeper diligence should happen.
How it works
The public site should only claim controls and workflows that are true today. It should not imply certifications, integrations, or guarantees that are not formally published.
The product can monitor public business information and first-party website behavior without blurring those categories together.
If a buyer needs a questionnaire, security review, or clarification about controls, the site should direct them into a real diligence path instead of making unsupported trust claims.
FAQ
No. The public site should only state the controls and compliance language that are currently published and defensible. If you need deeper diligence materials, contact the team directly.
The public site states encryption in transit and at rest, role-based access controls, and regular security review.
Use the contact path so the team can handle the questionnaire or diligence request directly instead of relying on thin marketing copy.
Use the contact path for questionnaire, diligence, or trust review requests rather than relying on thin marketing language.