Scope
This notice covers the public marketing pages, the browser-side call-flow demo, and the email-draft contact form. It does not cover call audio, transcripts, customer systems, or a future deployed receptionist.
Website behavior
The current application code does not add:
- accounts, sign-in, or a customer dashboard;
- a server-side contact submission endpoint or external form provider;
- analytics, advertising pixels, or marketing trackers;
- cookies, local storage, or session storage.
If those behaviors change, this notice and any required consent controls must be reviewed before the change is published.
Browser demo input
The sample call-flow demo processes text in browser memory. Application code does not send the text to a server, save it in browser storage, record audio, run production ASR, or place a call. Reloading the page clears the input.
Do not enter names, phone numbers, medical details, credentials, or confidential information. The demo is designed for short reception questions.
Server and hosting requests
A browser and the selected hosting or CDN provider exchange the request data needed to serve a page or asset. Operational logs may include an IP address, timestamp, requested URL, user agent, and error information.
This repository does not add a separate logging or analytics pipeline. The final host, access permissions, storage location, and retention period must be confirmed in the owner's hosting configuration; this notice does not invent them.
Email contact
The contact page validates a short call-flow brief in browser memory and uses it to prepare an email draft when an approved public address is configured. Your email application sends that message directly; the website does not receive, submit, or store the form answers. The receiving mail provider and organization apply their own handling after you choose to send the email.
Avoid sending credentials, regulated records, customer or patient information, or confidential documents in an initial message.
Product calls need a separate data notice
A live voice deployment must separately define recording and consent, transcription, storage location, access, retention, deletion, subprocessors, model-training use, and human review. This website notice makes no claim about those choices.
Changes and questions
The review date at the top records when this notice was last checked against the application. A material change to website collection, storage, contact, or hosting behavior should be reflected here before release.
Use the contact route for a question about this notice. It does not promise a response time or create a contractual request process.