Website privacy
This page explains how the public Hearing Onsite website works. It is written in plain language so patients, families, caregivers, and referring organizations know what not to send through general website tools.
The website FAQ assistant uses a fixed library of general business answers. Questions typed into that assistant are processed on the device in the browser. They are not sent to an AI service, saved by the assistant, or added to a patient record.
Keep questions general. Do not enter a patient name, diagnosis, symptoms, insurance information, medical record, medication list, or other private health information.
If you request a callback, the embedded Google form accepts your name, phone number, optional email, city or ZIP code, contact preference, and consent to be contacted. It does not provide fields for symptoms, diagnoses, service selection, care setting, insurance, device details, or free text.
Google Forms stores each request in a private form response and a private Google Workspace response sheet controlled by Hearing Onsite. An Apps Script trigger sends a notification to the fixed Hearing Onsite business inbox. Authorized staff may use the contact details to respond and will move any later patient-specific intake to an approved secure workflow. Submitted contact values are not sent to Cloudflare Analytics, application logs, cookies created by Hearing Onsite, KV, D1, or R2.
The separate Google organization form accepts facility and business-contact details, service area, and one approved partnership-interest selection. It has no patient field and no free-text message field. Responses are stored in a private Google Workspace response sheet, and an Apps Script trigger notifies the fixed Hearing Onsite business inbox.
Do not enter a resident or patient name, diagnosis, referral, insurance information, medical record, or other private health information.
The Hearing Onsite site records limited aggregate events such as a landing-page view and call or text click. Those events use an allowlisted page path, a small set of source and medium categories, and a one-way campaign fingerprint.
Cloudflare conversion events do not include form responses, names, phone numbers, email addresses, city or ZIP values, health details, full URLs, IP addresses, user-agent strings, raw campaign labels, or free text. Network and browser signals are used only to derive a short-lived, one-way rate-limit key and are not written to the analytics dataset.
The embedded forms and homepage map are provided by Google. Google may process technical information needed to display and protect those services under Google’s own privacy practices. Phone, text, and email links open the corresponding service on your device.
The public FAQ assistant and website content provide general business information only. They do not diagnose, treat, or evaluate symptoms. For an emergency, call 911. For sudden or urgent hearing changes, dizziness, pain, drainage, or other health concerns, contact an appropriate physician or urgent medical service.
For general website or privacy questions, contact Hearing Onsite at contact@hearingonsite.com or call (310) 431-9649. Do not include patient records or private health details in the first message.
Last updated August 31, 2026.Safe next step
Call, text, or request a callback with your name, callback number, and city or ZIP code. The team can explain an appropriate secure next step if more information is required.