Trust & security
Built for trust before scale
ResponseOS is designed to handle the calls, leads, and revenue at the center of your business. Here are the key controls, each labeled by what is actually built — and an honest read on where the build is today.
- Implemented
- Built, in use, and covered by tests.
- Partial
- Some of it is built; the rest is named below.
- Planned
- Designed, not built. Don't rely on it yet.
- Not claimed
- We don't hold it and don't imply we do.
Security
Tenant isolation
ImplementedEvery read and write your team makes is scoped to your account, derived from the authenticated session — never from client input. It's enforced in the data layer and covered by cross-tenant tests. One tenant can't reach another's data.
Webhook signature verification
PartialEnforced today on the call-event and identity webhooks: an event that fails verification changes nothing. The other provider endpoints accept nothing until their integration ships with verification.
Audit trail
PartialSome security and workflow actions — removing a user, reviewing an assessment request, setting up a demo — are written once to an audit log, and every verified call-event and identity webhook is recorded on receipt. Covering every account-access change, call, lead, booking, quote, and admin action, and locking the trail at the database level, is planned.
Data
Retention
PartialAssessment requests, demo calls (personalized and general), and raw call-event and identity webhook payloads now carry an expiry. Expired data is removed by a purge we run by hand: it previews what it would delete, changes nothing without an explicit flag, and records what it removed in the audit log. Per-tenant retention settings, scheduled enforcement, and enforcing each transcript's retention lane are planned.
Export and deletion
PlannedTenant-scoped export and deletion, so you can take your data with you or have it removed. Not built yet.
Payments
Payment boundary
PlannedBilling is designed to run through Stripe hosted pages and Payment Intents only, so card data never touches our systems. Billing isn't live, and no payment details are collected today.
Privacy
Fictional demo data
ImplementedThe demo walkthrough, operator console, and client dashboard run on fictional records, and each of those screens says so.
Privacy policy and terms
ImplementedBoth are published, at /privacy and /terms, and each describes what the current build actually does.
What we don't claim
Mature vendors show certification badges. We don't have them yet, so we list them here instead of implying them.
HIPAA compliance
Not claimedResponseOS is not HIPAA-certified or HIPAA-compliant. Healthcare and other regulated workflows are excluded from first pilots.
SOC 2, ISO 27001, PCI DSS
Not claimedWe hold none of these certifications and don't display their badges.
Uptime commitment
Not claimedResponseOS doesn't yet run a live customer service, so there's no uptime figure or service-level agreement to offer.
Where the build is today
This is an internal-first product in active development. The public site and demo walkthrough run on mock adapters and fictional records. A separate, supervised prospect-demo lane can take calls on a designated demo number: those calls arrive signature-verified and are stored, but it isn't a live customer service and isn't approved for customer data. Other provider integrations activate in a later release. We'd rather tell you that than imply otherwise.