Plain-English privacy summary
The short version of how BookerMove handles call and quote data. A counsel-reviewed long-form policy ships with the billing launch; this page is the operator-grade summary in the meantime.
What we store
- • Caller phone number (E.164).
- • What the caller said about the move: origin / destination addresses, approximate size, target date, optional name and email.
- • The quote we generated (low / high range, crew, truck, deposit).
- • The dispatcher action taken on that quote (approve / reject / paid).
What we don’t store
- • Credit card numbers. Deposits go through Stripe payment links; card data never touches BookerMove servers.
- • Government IDs, social security numbers, or any other regulated identifier.
- • Sales of customer data to third parties — we don’t. Ever.
- • Training of external models on your customers’ calls.
How long we keep it
- • Call transcripts: 90 days, then deleted unless explicitly archived for a booked job.
- • Booked-job records: kept indefinitely for the operator, until the operator requests deletion.
- • Aggregate, non-identifying analytics (e.g. number of calls per week per tenant): kept indefinitely.
Subprocessors
BookerMove relies on Supabase (database), Twilio (telephony + SMS), Vapi / ElevenLabs (voice agent), Clerk (operator authentication), and Stripe (deposits). Each handles its own slice and only its slice; none of them get more data than the function requires.
Deletion + access requests
Operators can export or delete any record from the dashboard. End-customers (the caller) can email support@bookermove.com with their phone number to request deletion of any record tied to that number. We respond within one business day.
Status of this document
This is an operator-grade plain-English summary. It is written to be true, but it is not a substitute for the counsel-reviewed long-form privacy policy that will ship alongside the billing launch. If anything on this page disagrees with the long-form policy when it lands, the long-form policy wins.