Live-chat privacy
Last reviewed 2026-10-25
Chat records and identity. When you use live chat, HiringCoachAI stores your messages, team replies, contact details you provide, chat status, ratings and call details. Authorized team members can view these records and add internal support notes. We use a first-party browser cookie to recognize your chat on return visits; it can last up to one year. Chat is not anonymous: we may link it to your signed-in account, contact history, subscription and payment attribution to provide support and measure its effectiveness. Signing out prevents access to account-linked chats through that cookie. An anonymous chat may still be accessible to another person using the same browser profile.
Your tracking choice. Starting or receiving a chat does not turn on analytics tracking. Recording passive page visits and time on site requires your analytics consent, including during an open chat. You can change that choice through cookie settings and still use chat. A message you send can include page context, such as the page and title where you started the chat. With analytics consent, we also record page paths and titles, session activity, referring pages and campaign tags, browser/device categories and approximate country, region and city. Location comes from IP-derived Vercel request headers, not GPS. Team members may see retained activity from earlier visits on the same visitor profile. Withdrawing consent stops new passive tracking; it does not erase previously collected records. Visitor profiles do not store raw IP addresses, but our hosting and security systems process IP addresses, and calls use network addresses as described below.
Optional AI replies. AI replies are disabled by default. If enabled, eligible messages can be processed automatically when the team is unavailable: the message, a limited recent chat history, page context and selected help content are sent to OpenAI to generate a reply. Our API requests disable optional completion storage. This does not mean zero retention: OpenAI says its abuse-monitoring logs may contain prompts and responses and are normally retained for up to 30 days; longer retention can apply when required by law or reasonably necessary to protect its services or others from harm. We do not promise Zero Data Retention. See OpenAI's data controls. Avoid including passwords, payment-card details or other sensitive information in chat.
Voice and video. Calls use WebRTC. This feature does not record or store call audio or video, but the other participant may be able to record using their own tools. We store call state, duration and connection-signaling records. For the planned STUN-only release, calls use Google's stun.l.google.com:19302 endpoint, also shown in the WebRTC project's connection guide. The STUN server receives network information and lets the browser learn its public IP address and port (IETF STUN standard). Connection information can reveal IP addresses to the other participant (W3C WebRTC privacy considerations). STUN does not relay call media; relaying is a separate TURN function (IETF TURN standard). We have not selected a TURN relay for this feature. Any future relay and its data handling will be disclosed before activation. Calls may fail on networks that require a relay.
Retention. Our cleanup schedule makes visitor profiles and their page-view history eligible for removal after 395 days without recorded visitor activity; contacts after 730 days without recorded contact activity; conversations, messages and signaling records after 730 days from the conversation's last non-system text message; and conversion-attribution records after 730 days from the event. For conversations without a text message, the conversation creation time is used. New activity can restart the applicable period; some chat activity does not extend every retention period. A voice or video call alone does not restart the conversation's text-message period. Cleanup runs periodically, so eligibility is not a promise of immediate deletion. Closing the chat or call does not delete its records. When another call is requested, we attempt limited cleanup of earlier signaling records, but some may remain until conversation cleanup or account deletion.
Access and deletion. Account deletion removes live-chat records linked to that account from active storage, including linked messages, signals and conversion-attribution records. Daily aggregate reporting counters remain. This does not immediately remove older copies from backups; those roll off under the backup windows described in our data retention policy. Provider-held records follow separate retention controls. OpenAI's controls are described above. We have not verified a retention period specific to Google's STUN endpoint; Google's general privacy policy does not establish a fixed period for this feature. If you chatted without an account, used another browser or email, or need records not included in your account export, contact [email protected] so we can verify and locate the relevant records. Account deletion cannot automatically locate records that were never linked to the account.