Privacy policy

Voice demo conversation transcripts. When you use the voice demo at /voice-demo, the text of your conversation is saved to our server. This lets us review demo conversations to improve the AI's behavior and follow up if you expressed interest. No audio is ever stored. Transcripts are not shared with third parties outside the operational purposes described in the third-party section below.

Inbound phone call transcripts and caller phone number. When someone calls an AI receptionist number connected to this system, the conversation transcript is saved along with the caller's phone number, which Twilio provides automatically. The phone number is retained so Josh can follow up on missed-call inquiries. No audio recording is retained.

Contact form submissions. Name, email address, and message text submitted through any contact form. Used to respond to inquiries.

Voice demo lead form submissions. Name, phone number, and optional business name submitted through the demo lead form. Used to follow up with interested visitors.

Booking widget submissions. Name, email address, phone number, and the topic you'd like to discuss, submitted when booking a discovery call. Used to schedule the call and send a calendar invitation.

Google Calendar refresh tokens. When a customer connects their Google Calendar to the AI receptionist through the OAuth flow, we store an encrypted refresh token representing permission to read free/busy information and create appointment events on their behalf. This token is encrypted at rest and never transmitted to any third party other than Google's own APIs during normal operation.

Server logs. Standard web server logs including request paths, timestamps, IP addresses, and user agents. Used for operational monitoring and debugging.

Telemetry events. Anonymised funnel events (page views, demo interactions, booking steps) collected through our own telemetry system. Used for conversion tracking and understanding how the site is used.

Twilio — inbound phone call routing and real-time audio streaming. When someone calls an AI receptionist number, Twilio routes the call and provides the caller's phone number. Twilio's audio streams are piped in real time to Deepgram for transcription; Twilio does not retain audio after the call ends on our behalf. Twilio privacy policy.

Deepgram — speech-to-text and text-to-speech. During voice demo sessions and inbound phone calls, audio is streamed to Deepgram in real time for transcription. The resulting transcript is used for the AI response. Response text is also streamed back to Deepgram for text-to-speech synthesis. Hunter Dev does not retain audio; Deepgram processes it transiently per their terms. Deepgram privacy policy.

Groq — large language model hosting. Conversation transcripts are sent to Groq's API for response generation. Groq does not train its models on Hunter Dev traffic per their terms of service. Groq privacy policy.

Google — OAuth authentication and Google Calendar API. When a customer connects their Google Calendar, their refresh token is stored encrypted and used only to read free/busy times and create appointment events on the connected calendar. Google privacy policy.

Cloudflare Turnstile — bot protection on public forms. Turnstile verifies that a form submission is from a real person, not an automated script. It operates without placing advertising cookies. Cloudflare privacy policy.

Loki — log aggregation. Application logs are shipped to a self-hosted Loki instance on Josh's own infrastructure. Logs are not transmitted to external commercial log services.

Hunter AI's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Information from connected Google accounts — including calendar event data, free/busy times, and the account's email address — is used only to schedule and read appointment events on behalf of the user who connected the account. The scope requested is calendar.events, which limits access to individual calendar events and does not grant access to calendar settings or other Google services.

Hunter AI does not transfer Google user data to any third party except as strictly necessary to provide the calendar scheduling feature to the user who connected the account, in compliance with Google's Limited Use requirements.

Hunter AI does not use Google user data for serving advertisements.

Hunter AI does not allow humans to read Google user data except as the user gave express permission, as necessary for security purposes, to comply with applicable law, or where data has been aggregated and fully de-identified.

Hunter AI does not use Google user data to develop, improve, or train generalized AI or ML models.

Conversation transcripts and contact submissions — kept for as long as the underlying relationship is active or until you request deletion.

Booking submissions and Google Calendar refresh tokens — kept while the customer's connection is active; deleted when the customer disconnects their Google account or asks for deletion by email.

Server logs — 30 days, then automatically purged.

Telemetry events — 90 days.