Legal & trust register
Current website notices. Clear product boundaries.
These pages document what the public website does today. They do not fill in the contracts, consent choices, or data practices that must be approved for a live voice deployment.
- Published
- 3 current website documents
- Boundary
- No customer contract or live-call data policy
- Reviewed
Document register
What applies to this website now
Each page names its scope, status, and review date so a website statement is not mistaken for a product or customer commitment.
Website data notice
Current application behaviorLearn how the public HelloHinglish website, browser-only text demo, and email-draft contact form currently handle information.
Read documentAccessibility statement
Target and current implementationReview the accessibility target, interface provisions, testing approach, and feedback path for the HelloHinglish public website.
Read documentSecurity & disclosure
Current public-site scopeReview the current public-site security scope and safe guidance for reporting a suspected HelloHinglish website vulnerability.
Read document
Release boundary
Not published without the missing facts
Legal language cannot decide how a product operates. These documents need an approved entity, market, workflow, and owner before they can be credible.
- Website or service terms
The legal operator, contracting entity, market, and governing terms have not been supplied.
- Live-call data notice
Recording, consent, transcription, access, retention, deletion, providers, and model-training choices remain deployment-specific.
- Customer data agreement
Roles, subprocessors, locations, instructions, safeguards, and contractual commitments require an approved operating model.
- Support or service commitments
Availability, support hours, incident handling, service levels, and remedies have not been established.
Change control
Update behavior and notice together
A new tracker, contact form, account, voice provider, or call-data workflow changes the facts these pages describe.
- Website change
- Review the affected notice and consent controls before release.
- Voice rollout
- Approve call recording, consent, access, retention, deletion, providers, and human review for that deployment.
- Contract change
- Keep public notices separate from signed customer terms, data agreements, service levels, and deployment commitments.