Trust and security
Only controls that run in the product today are on this page.
Tenant isolation
Every workspace's data is separated by row-level security in the database. Static tests fail if a workspace page or action could read data before checking access.
Approval before anything goes out
Posts, pages, ad changes, emails and plans wait in an approval inbox. The approved version is locked by a content hash, so what goes out is what was approved.
Second-check read-back
After a write to an ad, social or website platform, the platform's own record is read back and compared with the approved change. A mismatch is reported, not hidden.
Append-only audit log
Audit events, consents, lead events, send attempts and sync verifications cannot be edited or deleted, by any database role.
Consent records and STOP
Each form submission stores the exact consent wording, its hash, the page, time, IP and browser. STOP, UNSUBSCRIBE and other opt-out keywords are honored, and quiet hours apply.
Encrypted secrets
Platform tokens and API keys are stored in Supabase Vault and read only on the server.
Sign-in
Sign-in runs through Clerk. Access to each workspace is checked again on every request.
Private share links
Report and approval links use hashed tokens, expire, are rate limited and are marked noindex, so search engines do not list them.
Retention purges
An hourly job clears call recordings and transcripts in PHI mode after 90 days, removes lead-history uploads past their purge date, and deletes expired share links after 90 days.
We do not hold SOC 2 / ISO certification today.
How we talk about results
- No customer logos, testimonials or result numbers on this site.
- Product cards on this site are illustrations with sample data.
- Forecasts are ranges, and the product never promises an outcome.
Security questions or a questionnaire to fill in? Email us. hello@xark.io