The security questions your regulated clients ask, answered by architecture.
Your clients’ data stays separated from every other agency’s, protected the same way banks protect account information. We’re pre-launch, so where an attestation isn’t done yet, we say so, and we tell you when it publishes.
Claims a skeptical engineer on your client’s side can check.
Tenant isolation by construction
Two isolation strategies, each where it fits. Control-plane data lives in a shared database where every tenant-owned row carries an agency identifier and every client-owned row carries a client identifier, and a repository layer guarantees no query runs unscoped. The sensitive retrieval path is stronger still: each client’s knowledge base is its own instance, so a query can only ever read inside the instance opened from validated context. Isolation is a property of the architecture, not a rule someone has to remember.
A knowledge base per client
The material the AI answers from is never pooled. Each client gets its own retrieval instance; only non-sensitive template and vertical IP is shared, and everything is reached through a tenant-scoped service. One client’s data cannot surface in another client’s answers.
Credentials are never stored in plaintext
Provider keys and every connected credential live in Cloudflare Secrets Store, envelope-encrypted: the ciphertext and a wrapped data key sit in the database, the key that unwraps them stays in the secret store, and decryption happens only inside the gateway that needs it. Nothing sensitive is written to the database in the clear, including an agency’s own bring-your-own keys.
A white-label boundary that survives inspection
On a partner’s custom hostname, the app and the API are same-origin, the session cookie is same-origin, and no Konvy-owned domain or asset is reachable from the client’s browser. The white label holds when someone opens dev tools and inspects the DNS, not just when they glance at the logo.
Access control and two-factor
Agency permissions run through a role-and-permission system with custom roles; platform entitlements and per-client limits are enforced at the gateway and the credit ledger, not only in the UI. Two-factor is available to agency owners and enforced for platform administrators. Programmatic API keys are agency-owned, scoped, and rate-limited.
Audit logging on privileged actions
Sensitive control-plane actions (rate-card edits, provider and model changes, template publishes, plan assignments, member changes) are written to an audit log. Platform support access is grant-based, flagged in the session, time-boxed, and recorded with the administrator, the reason, and the duration. Support cannot silently act as you.
Payment isolation
Agency-to-client billing runs on Stripe Connect. The agency connects its own Stripe account through Stripe-hosted onboarding, so Konvy never touches the agency’s Stripe credentials and Stripe owns the card-data compliance surface. Konvy stores no cardholder data.
Per-tenant model budgets
Every model call carries tenant metadata and runs through a gateway that attributes cost per tenant and enforces per-tenant budgets. Usage is metered, attributable, and cannot run away unbounded on one tenant’s behalf.
What’s built in today, and what publishes at GA.
Compliance tooling, built in
Consent capture, recording disclosures, opt-out and STOP/HELP handling, jurisdiction warnings, and the registration US carriers require before a business can send texts at scale are built in, not an add-on. The tooling makes compliance practical; operational responsibility stays with the partner and the client.
HIPAA & data protection
A BAA is available to founding partners serving covered entities, and a Data Processing Addendum is available for partners with GDPR or Australian Privacy Principles obligations. Provided during onboarding, described here, not dressed up as a certification we don't yet hold.
Attestations, honestly
We're pre-launch, so there is no formal audit or independent security review to cite yet, and we don't pretend otherwise. Security assessments and certifications publish as we reach general availability, alongside the status page and SLA.
A global network and a defined set of launch regions.
Launch regions
Number provisioning and campaign sends launch in the United States, Canada, the United Kingdom, Australia, and New Zealand. A region outside that set cannot provision numbers or send campaigns.
Built on Cloudflare
The platform runs on Cloudflare’s global network (Workers, D1, R2, and the AI Gateway) rather than a single cloud region. Model routing, budgets, and per-tenant cost attribution happen at that gateway.
Residency at GA
Formal data-residency commitments and the subprocessor list are documented as the platform reaches general availability. Where we can’t yet commit in writing, we say so rather than imply a guarantee.
Want to go through it in detail?
The isolation model, the architecture diagram, the DPA and BAA templates, and the subprocessor list. Walk through them with the team building it. No sales layer between you and the person who built it.