How SiteHelp protects your data and your customers' conversations. Everything below is enforced in the product today.
Every record is scoped to its account by a global query boundary, so one customer can never read or write another's data — enforced at the model layer, not just the UI.
All traffic is served over HTTPS. Third-party credentials (CRM tokens, channel secrets, WhatsApp keys) are encrypted at rest, never stored in plain text.
Outbound events carry an HMAC-SHA256 signature over a timestamp and the body, so your receivers can verify authenticity and reject replays.
Every server-side fetch — the KB crawler and every webhook — is validated against private, loopback and reserved address ranges before a request is made.
WhatsApp, Messenger and SMS webhooks verify provider signatures (Meta app secret, Twilio signature); email inbound is token-authenticated.
Console access is gated by role (owner / admin / agent). Brand-scoped admins only see the websites assigned to them; agents never reach the admin console.
Sensitive actions — account provisioning, suspensions, impersonation, password resets, logins — are recorded with actor, time and IP for review.
Google OAuth / OpenID Connect sign-in with CSRF-protected state and verified-email matching, for teams that require single sign-on.
SiteHelp is a managed cloud service — but your data remains yours: bring your own AI keys, set your own retention windows, and export or erase everything on demand. We process conversations solely on your instructions, under a signable DPA with a public sub-processor register.
Found a vulnerability? We want to hear from you. Email security{{ parse_url(config('app.url'), PHP_URL_HOST) ?: 'sitehelp.local' }} with details and we'll respond promptly. Please give us reasonable time to remediate before public disclosure.