How we protect your data and your customers' data.
LEADARO processes sensitive data — lead conversations, bookings, marketing-channel integrations. This page is a short explanation of how we protect that data at every layer of the platform.
Six layers of protection, integrated by design.
AES-256-GCM token encryption
All refresh tokens and channel credentials (Google Ads, Meta, WhatsApp, Vapi, MedSoft, etc.) are encrypted with AES-256-GCM before being written to the database. The per-environment encryption key is isolated in a secret manager separate from application code. Decrypted tokens never leave the server tier.
Row-Level Security on every workspace-scoped table
Every workspace-scoped Postgres table has RLS policies that only allow access to members of that workspace. Policies are enforced by the database on every query, regardless of the application — even if a route handler forgot to check membership, the database would refuse the request.
3-layer multi-tenant isolation
Layer 1: route handlers verify user membership via requireMembership() before any operation. Layer 2: RLS at the database enforces workspace_id on every row. Layer 3: integration credentials are never shared across workspaces — each workspace has its own set of encrypted tokens.
EU data residency
The primary database runs on Supabase EU-West-1 (Ireland). The application runs on Vercel Edge with request routing biased toward EU regions. US-based subprocessors (Anthropic, OpenAI) operate under Standard Contractual Clauses (SCC) with signed DPAs.
Continuous audit logging
All administrative actions, inbound webhooks, data mutations and outbound third-party API calls are logged with correlation context (request_id + workspace_id + lead_id) into Better Stack. 90-day retention for investigations. Webhooks have fail-closed signature verification.
Incident response
The LEADARO team monitors Better Stack alerts 24/7. For incident reports, responsible disclosure or security questions, email office@thebrandoers.com.
Aligned with European data standards.
GDPR by design
Data-subject rights (access, deletion, portability, restriction) are supported through dedicated administrative operations. The workspace is the controller; LEADARO is the processor, with DPA available on request.
Google API Services User Data Policy
Use of data received from Google APIs adheres to the Limited Use requirements. See the Google API disclosure page for full scope-by-scope detail.
Security questions? We're listening.
For DPAs, vendor assessments or technical questions, email office@thebrandoers.com.