Privacy Policy
Effective October 8, 2026
This policy explains how RingGather handles information when providing a supervised AI receptionist and lead-management service to participating home-service businesses.
Website walkthrough requests
When you request a walkthrough, we collect the name, business, email address, optional phone number, trade, and any calculator estimates you choose to include. We use these details to respond to your request and may send them to our email delivery provider to notify the RingGather owner. Calculator estimates are scenarios, not actual call or revenue records. Website requests are stored in our separate website database and are not placed into a client call workspace.
Information we handle
Depending on the approved pilot configuration, RingGather may process caller names, callback numbers, service addresses, service requests, language preferences, consent responses, appointment details, call transcripts, call status, transfer results, and technical usage or cost information. Audio recording is disabled in the current pilot unless a separate approved recording and consent process is implemented.
How information is used
We use this information to answer inbound calls, follow the participating business’s approved rules, check appointment availability, create approved calendar events, route calls to staff, show the business its call records, investigate failures, and operate or improve the service.
Service providers
RingGather uses service providers for voice automation, language transcription, hosting, telecommunications, and calendar access. These providers process information only as needed for the configured service and under their own applicable terms and privacy commitments.
Google user data
When an authorized business owner connects a Google Calendar, RingGather requests calendar.freebusy to check whether an approved appointment window is open and calendar.events to create an appointment on the selected calendar. It sends the requested time window to Google for the availability check; if booking is approved, it sends the appointment time, service details, and caller details needed to create the event. RingGather does not read the contents of unrelated calendar events for this workflow. It does not tell a caller an appointment is confirmed until Google has created the event.
RingGather stores the selected calendar reference, encrypted authorization token, and the resulting appointment record and Google event ID for the connected business. Availability results are used to make the booking decision, not to build a separate copy of the calendar. Access is limited to the authorized client workspace and the service providers needed to host and secure RingGather. Authorized business users can see the resulting appointment in their workspace. We do not sell Google user data, use it for advertising, or transfer it to other clients. Our use and transfer of Google user data are limited to providing these user-facing Calendar features, maintaining security, and complying with applicable law, consistent with the Google API Services User Data Policy, including its Limited Use requirements.
A business can revoke RingGather’s access in its Google Account and request removal of the stored connection and related RingGather records using the contact address below. Revoking access stops new Calendar checks and bookings; it does not by itself remove events already saved in that business’s Google Calendar. RingGather’s appointment records follow the client retention and deletion rules described below.
Retention and security
Client call data in the current pilot uses a configurable retention period, with 30 days as the starter setting. Active leads, future appointments, and unresolved follow-ups may be retained while they remain operationally necessary. Provider-side retention may differ and is reviewed with each pilot business. Walkthrough requests remain in RingGather’s owner inbox while open; closed request records are deleted from that inbox 180 days after they are marked closed, or sooner if deletion is requested. Reopening a request pauses that clock. Notification emails containing request details may remain in the recipient mailbox until separately deleted. We use access controls, client-separated records, encrypted credentials, and limited provider permissions to reduce unauthorized access.
Choices and requests
Walkthrough requesters can ask us to correct or delete their submitted details. Participating businesses can request access, correction, export, deletion, connection removal, or pilot shutdown. Callers may decline transcription during the approved consent flow and receive the business’s configured alternative.
Contact
Questions or privacy requests can be sent to support@ringgather.com.
Changes
We may update this policy as the pilot, providers, or legal requirements change. The effective date above identifies the current version.