Security & Data Protection

WireBot is built for an industry where customer data is sensitive and dealer trust is everything. Security isn't a feature we added — it's how the platform was architected from day one.

Data Ownership — A Clear Split

WireBot uses a split ownership model. There's no ambiguity about who owns what.

When a rep leaves, customer data stays with the dealer. The rep's personal performance history follows them to their next WireBot-using store — like a career portfolio, not a data transfer.

Multi-Tenant Isolation

Every dealer's data is completely isolated at the database level. This isn't application-layer filtering — it's enforced by PostgreSQL Row-Level Security (RLS) policies that the application cannot bypass.

• Every table has a tenant_id. Every query is scoped to the authenticated dealer's tenant. There is no "SELECT * FROM customers" without a tenant boundary.
• Even if our code has a bug, your customers cannot appear in another dealer's query. The database itself enforces the boundary, not our application logic.
• Separate database roles: The application connects with a restricted role that cannot bypass RLS. Administrative operations use a separate, audited role.

Encryption

Device & Access Security

WireBot is designed for store-issued iPads — not personal phones. This is a deliberate architectural decision, not a limitation.

• Store-device only. No customer data on personal devices. What happens in the store stays in the store.
• Shift-based sessions. Reps log in at the start of their shift and are automatically logged out when the session ends. No persistent access.
• Zero local caching. Customer data is never stored on the device. Everything lives server-side behind authentication.
• Role-based access. Reps see their customers. Managers see their store. Owners see all stores. Nobody sees more than they should.

AI & Data Processing

WireBot uses AI for voice transcription and data extraction. Here's exactly what AI sees and doesn't see:

Data Type	AI Access	Status
Voice note audio (for transcription)	Processed, not stored by AI provider	Processed & Discarded
Transcript text (for extraction)	Processed to extract customer details	Processed & Discarded
SSN, credit card numbers	Regex redaction pass live; voice-flow integration in progress	In progress
Customer phone numbers	Extracted and stored in dealer's tenant	Dealer-Owned
Sales and commission data	Never sent to AI providers	Blocked

Redaction status. The regex redaction pass is live. Voice-flow integration is in progress — until end-to-end redaction is running in production, treat raw transcripts as sensitive.

Our AI providers (Anthropic and OpenAI) do not train on customer inputs. Voice data is processed and discarded — not retained, not learned from, not shared.

SMS Compliance

• Built for TCPA compliance. Every outbound message requires a documented consent record before it can send. Compliance also depends on how your team collects consent — we give you the controls and the record.
• Opt-in confirmation. Customers receive an initial text confirming their consent with clear opt-out instructions.
• Quiet hours enforced. No messages before 8 AM or after 9 PM in the customer's local timezone.
• STOP always works. Customers can opt out at any time by replying STOP. Opt-outs are processed immediately and permanently.
• 10DLC registered. WireBot uses registered Application-to-Person (A2P) messaging for maximum deliverability and carrier compliance.

Audit Trail

WireBot keeps an append-only event log of rep actions — follow-ups sent, blocked, edited and converted; consent collected and withdrawn; voice notes logged; deals closed — each stamped with the rep, the dealer and the time it occurred. SMS consent and opt-outs are held in a separate ledger alongside a per-dealer do-not-contact list. This is an operational event history rather than a full system audit log: record views and administrative actions are not yet captured in it. If your review requires audit coverage of admin activity, ask us for the current scope in writing rather than assuming it.

Infrastructure

Roadmap

• SOC 2 Type II: Not yet certified. Compliance work begins with the pilot.
• Data Processing Addendum (DPA): Available for dealers who require one. Standard template with wireless-specific terms.
• Zero Data Retention (ZDR): Available for enterprise dealers who want to eliminate the standard AI provider retention window entirely.
• Self-hosted transcription: For dealers who want voice data to never leave their network. Runs on consumer hardware.
• Per-rep phone numbers: Each rep gets a dedicated number so customers reply to a person, not a brand. Planned; not provisioned today.

Questions?

If you have security questions or need documentation for your compliance team, reach out at security@wirebot.app.