Privacy
Plain-language privacy summary
How CallSnare stores and uses the call, message, booking, billing, and proof records needed to recover missed work.
Updated April 16, 2026. Plain-language product summary that stays tied to the operating records the product already keeps.
Short version
CallSnare stores the operating trail behind missed-call recovery.
That trail lets the office act, lets the product run, and lets results or guarantee questions be explained from records rather than memory.
Data we store
Operating records needed to recover missed HVAC work
- Account and workspace details such as owner name, email, organization name, role, and selected plan state.
- Tracked phone numbers, missed-call events, SMS conversations, lead notes, booking records, and proof timeline entries.
- Settings such as business hours, services, templates, booking preferences, job values, integrations, and opt-out state.
- Billing and guarantee records needed to keep plan state, credits, and guarantee outcomes auditable.
How we use it
The data runs the workflow and explains the result later
- Call and message records are used to trigger follow-up, route leads into the inbox, and keep office handoff context attached.
- Booking and lifecycle records are used for reminders, results, proof, and guarantee evaluation.
- Operational logs and provider records help diagnose delivery issues, webhook retries, and billing state.
- CallSnare is not positioned as a public lead resale marketplace or broad anonymous data broker.
Messaging
Text messaging privacy and consent records
- Missed-call and customer care text-back can be part of the service when account rules, business practices, and consent records support it.
- CallSnare may store mobile numbers, messaging consent records, opt-out state, message history, delivery metadata, and related workflow events as part of the operating record.
- Mobile numbers, consent records, opt-out state, and messaging metadata are used to run customer care workflows, honor STOP or START style replies, diagnose delivery issues, and maintain compliance records.
- Mobile opt-in data is not sold or shared with third parties for their own marketing purposes.
- Infrastructure providers such as Twilio may process messaging traffic and related metadata so texts can be sent, received, delivered, and reported.
- Customers using CallSnare are responsible for collecting consent appropriately before enabling text follow-up through their own forms, chat, phone, intake, and service-request practices.
Providers
Third-party providers handle narrow parts of the workflow
- Telephony and messaging may flow through providers such as Twilio.
- Billing may flow through Stripe when paid subscriptions are active.
- Email delivery may be used for account or alert messages such as password reset links.
- Approved integrations should only access data through scoped credentials and documented boundaries.
Access and retention
Access should stay scoped and records should remain explainable
- Only approved organization members and scoped integration credentials should access protected workspace data.
- Some records are retained so the business can reconstruct calls, messages, bookings, billing state, and guarantee decisions.
- Customers can request help with account access, data questions, or correction needs through the account owner path.