Compliance & Security

Compliance That Doesn't
Compromise the Experience

HIPAA-ready with signed BAA. PCI scope reduction via certified card injector. SOC 2 controls, with our own Type II readiness assessment underway. GDPR data processing agreement. WCAG 2.2 AA accessible widget. Every compliance requirement covered without a separate vendor.

🮵
HIPAA
Signed BAA available • 7yr audit log
Available
💳
PCI DSS
Scope reduction • card data never stored
Available
📄
SOC 2 Type II
Readiness assessment • we complete your SIG directly
Evidence Gathering
🌍
GDPR / SCC
DPA signed • EU / UK / Canada residency
Available
♿
WCAG 2.2 AA
Screen reader tested • keyboard nav
Business+
0
Card data stored in Velaro
7yr
Audit log retention for HIPAA
5
Compliance frameworks supported
< 24hr
BAA turnaround time

One platform, five compliance postures

Velaro handles regulated industries without compromising the conversation experience. Compliance is enforced server-side, not bolted on after the fact.

🮵
HIPAA + BAA
End-to-end encryption at rest (AES-256) and in transit (TLS 1.3). Signed Business Associate Agreement. PII scrubbing on conversation records. Audit log configured to 7-year retention. Required for healthcare, behavioral health, and dental workflows touching PHI.
💳
PCI Scope Reduction
Certified third-party card injector captures card data before it ever enters the Velaro data path. Velaro never sees, stores, or transmits raw card numbers. Velaro's infrastructure is removed from PCI DSS scope entirely. Supports Stripe, Clover, and Square injectors.
📄
SOC 2 Controls
We are in the evidence-gathering phase of our SOC 2 Type II audit as we complete our move to Velaro's next-generation platform. Our control environment already runs on Microsoft Azure and inherits its SOC 1/2/3 and ISO 27001 attestations for the hosting layer, and we operate to SOC 2 Trust Service Criteria for security, availability, and confidentiality today.
Rather than pointing you to a static report, our security team completes your Security Information Gathering (SIG) questionnaire directly - line by line - so your procurement team gets exact, current answers about our real controls instead of a document written for someone else.
🌍
GDPR / Data Transfer Agreement
Standard Contractual Clauses executed for EU/EEA data transfers. Data Processing Addendum signed. Data residency option locks all data to your required Azure region. Covers EU, UK, Canada, and US-only configurations independently.
♿
WCAG 2.2 AA Accessibility
Chat widget passes WCAG 2.2 Level AA. Screen reader tested with NVDA and JAWS. Keyboard-navigable without a mouse. High contrast mode available. Required for government, education, and financial services in many jurisdictions. Available on Business and Enterprise.
🏠
Multi-Region Data Residency
Conversations, contacts, and bot data stay in your jurisdiction. EU, UK, Canada, and US-only residency available. Each region is an isolated Azure deployment with its own storage, encryption keys, and audit boundary. Required for multi-national organizations with conflicting residency obligations.
🔐
Vault Fields
Mark any Contact field as encrypted. AES-256 at rest, encryption key held in Azure Key Vault, never in application code. Unlocking requires both a role you choose and a live code from an authenticator app. Structurally excluded from AI prompts, workflows, and routing rules. Part of Compliance Mode.
🛡️
AI Output Guardrails
An independent check that reads every AI response before it reaches a visitor, on top of the system-prompt instruction layer. Admin-defined restricted categories, blocks and substitutes a fallback message rather than risking an unverified answer. See how it works →
🚨
Threat Detection (Government & Public Safety)
Monitors every visitor message for credible threats against officials, with instant SMS alerts, automatic IP blocking, and conversation shutdown. Built for government agencies, law enforcement, and public-sector contact centers. See how it works →

The one field your agents need, that nothing else should ever read

Every support team eventually has to hold onto something sensitive against a customer record: a password, a PIN, an account-recovery detail the customer gave you so you could help them next time. Vault Fields lets you mark that one Contact field as encrypted, without moving it to a separate system and without losing it from the record your agents already work in.

👨‍💻
IT & Managed Services
A client's router or admin password needs to be on file so a tech can remote in and fix something next month without calling to ask for it again. Store it in a Vault field. Only the roles you choose can ever unlock it, and only with a live authenticator code.
🏨
Property Management & Hospitality
A guest's smart-lock code or portal credential sits on the reservation record so the front desk can help at any hour, but it is never plaintext next to the guest's name and unit number for anyone with contact access to see.
🛒
E-Commerce & Subscription
An account-recovery detail a customer gave support so they could be verified later stays encrypted on the contact record. Readable only by the agents authorized to handle account recovery. Never by the bot answering a routine order-status question.
🔑
Role-Gated Unlock
You choose exactly which staff roles can ever unlock a given Vault field. Everyone else, including staff outside that role, never sees it.
📱
TOTP, Not Just a Password
Unlocking a Vault field requires a live 6-digit code from an authenticator app: Google Authenticator, Microsoft Authenticator, or Authy. A stolen login password alone cannot open one.
📋
Every Unlock Logged
Every unlock attempt is durably audit logged, successful or denied. Built as part of Velaro's SOC 2 compliance program.
🚫
Never Reaches AI or Automation
A Vault field's value is never accessible to an AI prompt, a workflow, or a routing rule. This is architectural, not a setting that can be toggled off.

Vault Fields is available to any Velaro Contacts customer on Compliance Mode, not limited to accounts that also run ticketing. Every account starts with 3 Vault fields.

PII redaction for live chat, built in — not a separate DLP vendor

Customers type sensitive data into chat whether you ask them to or not — a Social Security number, a card number, a bank account. Velaro automatically detects and masks it in real time, across every channel, before it's ever stored.

🔒
Built-in Pattern Detection
Social Security numbers, Canadian SIN, credit card numbers, CVV codes, and bank account numbers are detected and redacted automatically, on every plan that includes Compliance. No setup required for the baseline patterns.
📡
Every Channel, Not Just Web Chat
Redaction runs across live chat, email, SMS, tickets, and social channels (Facebook, Instagram, Twitter, TikTok) — a true DLP layer for live chat and every other conversational channel your team supports, not a single-surface bolt-on.
⚖
Custom Patterns + Per-Group Control
Add your own regex patterns for internal ID formats, policy numbers, or account codes. Turn redaction on or off per channel and per routing group instead of one blunt account-wide switch.
🤖
Optional AI-Assisted Pass, BYOK-Ready
Regex catches known formats reliably and for free. An optional AI-assisted pass catches PII phrased in less predictable ways — off by default, opt-in only, and routes through your own AI endpoint if you've configured Bring Your Own Key rather than sending text through Velaro's provider.
📋
Audit Log as Compliance Proof
Every real redaction is logged: which pattern fired, which conversation, which direction — never the sensitive value itself. Hand this to your own auditor as evidence redaction is actually running, not just configured.
🮵
Supports HIPAA Chat Compliance
PII redaction is part of what makes Velaro's HIPAA posture work for healthcare, behavioral health, and dental workflows touching PHI in chat — paired with the signed BAA, encryption, and 7-year audit retention described above.

PII redaction pairs with Vault Fields and SecureForms rather than replacing either: use SecureForms for data that must never touch Velaro's database at all (card numbers), Vault Fields for one sensitive field your agents genuinely need to reference later, and Redaction for freeform text where PII shows up unexpectedly.

What Velaro provides for each framework

Compliance documentation available from your account manager or at sales@velaro.com.

Framework What Velaro Provides Plan
HIPAA Signed BAA, AES-256 encryption at rest, TLS 1.3 in transit, 7-year audit log retention, PII scrubbing, optional US-only data residency Enterprise
PCI DSS Certified card injector integration (Stripe, Clover, Square), card data never stored in Velaro, Velaro removed from PCI DSS scope, scope reduction letter available Enterprise
SOC 2 Controls operating to SOC 2 Trust Service Criteria, Azure SOC 1/2/3 inherited for the hosting layer, your SIG or CAIQ questionnaire completed directly by our security team, pen test summary, security review document. Our own Type II readiness assessment is underway - no report is claimed until it exists. Enterprise
GDPR Standard Contractual Clauses (SCC), Data Processing Addendum, EU / UK / Canada data residency options, GDPR-compliant data deletion on request Enterprise
WCAG 2.2 AA Accessible chat widget, NVDA and JAWS screen reader support, keyboard navigation, high contrast mode, focus management Business+
PII Redaction / DLP Automatic detection and masking of SSN, SIN, credit card, CVV, and bank account numbers across chat, email, SMS, tickets, and social; custom regex patterns, per-channel and per-group control, optional AI-assisted pass with BYOK, and an audit log of every redaction Compliance Starter+

Data Residency by Jurisdiction

Select the Azure region that satisfies your regulatory requirement. Each residency option is an isolated deployment, not a configuration flag.

🎉
United States
US East + West Azure regions. Default for all accounts. Satisfies US federal and state data requirements.
🇪🇺
European Union
EU West (Netherlands) + EU North (Ireland). Satisfies GDPR Article 46 transfer requirements.
🇬🇧
United Kingdom
UK South (London) Azure region. Covers UK GDPR and ICO requirements post-Brexit.
🇨🇦
Canada
Canada Central (Toronto) Azure region. Satisfies PIPEDA and provincial privacy law requirements.

Identity Provider Integrations

Enterprise SSO with SAML 2.0 or OIDC. Works with every major identity provider. SCIM provisioning automates user creation and deprovisioning. MFA is enforced at the IdP level — Velaro inherits your organization's authentication policy.

  • SAML 2.0 and OIDC both supported
  • SCIM provisioning and deprovisioning
  • Just-in-time user creation on first login
  • MFA enforced at the IdP — no Velaro-specific MFA config required
  • Multiple IdPs per account for multi-brand organizations
Contact Sales for SSO Setup
🔒
Okta
SAML 2.0 + SCIM
🪞
Azure AD / Entra ID
SAML 2.0 + OIDC + SCIM
🆕
Google Workspace
SAML 2.0 + OIDC
👥
OneLogin
SAML 2.0 + SCIM

Compliance documentation available on request.

BAA, security review document, pen test summary - and your own SIG or CAIQ questionnaire completed by our security team. Contact sales to request any of it.

Email sales@velaro.com Book a Demo