Encryption
Contact details customers enter on a booking page are encrypted at rest with AES-256-GCM, using keys kept separate from the database. Everything is served over HTTPS.

Security
The strongest protection is data that isn't there.
Contact details customers enter on a booking page are encrypted at rest with AES-256-GCM, using keys kept separate from the database. Everything is served over HTTPS.
Customer contact details expire automatically after a period each business sets — 30 days by default, never more than a year. The job record itself, what was booked and paid, stays so the business can run its books.
Every request is tied to the signed-in operator's own business and checked in the application on each read and write, so one business can't see another's customers.
Customers enter card details in Square's own secure fields, and the payment goes straight to the business's own Square account. RelayLeads never stores card numbers and never holds the money.
Our message delivery records have no field for a phone number or the message text. Lead alerts on operators' phones are encrypted end to end and carry a pointer to the job, not the customer's details. Text and email providers keep their own delivery records.
Photos customers upload are encrypted in private storage with their location data stripped, and only the business they booked can open them.
RelayLeads is hosted on Cloudflare. Customer payments run through Square, sign-in and calendar sync through Google, and text messages through Twilio. Each does one job, and none of them buy data from us.
Found a vulnerability, or have a security question? Email hello@relayleads.io — security reports go to the top of the queue.
Enter your business. We build the rest.
Free, takes about two minutes, no credit card. Your page, booking flow, and dashboard — built from a few quick questions.
Start here We'll find your business on Google and build your booking page.