LEGAL
Privacy Policy
How UNTH.AI collects, uses, and protects data across our site, chat, and voice agents.
Last updated: 2026-07-03. English version — Thai and French versions follow with our locale rollout.
Who we are
UNTHAI ("UNTH.AI", "we", "us") operates the website at unth.ai and its AI chat and voice assistants. We are based in Thailand and act as the data controller for the personal data described in this policy.
For any privacy question, or to exercise the rights described below, contact us at [email protected].
What we collect and why
Contact form: when you send a message, we collect the name, email, and message content you provide so we can reply and follow up on your enquiry.
Chat assistant: messages you send to the on-site chat assistant, so it can answer and so we can follow up if you ask us to.
Voice assistant: your live audio is streamed to Google’s Gemini API to power the conversation. We do not keep audio recordings. If you explicitly enable voice memory, we store an opaque random browser identifier, factual conversation summaries, and details you choose to share so future conversations can continue naturally. Voice memory is optional and can be deleted from the voice interface.
Analytics: with your consent, Google Analytics 4 collects standard usage data (pages viewed, approximate location, device and browser), and Microsoft Clarity records anonymised session replays and heatmaps (clicks, scrolls, and interaction patterns, with input text masked by default), to help us understand how the site is used.
Leads: enquiries from any of the above channels may be stored as leads in our CRM so a human can respond and continue the conversation.
Who processes your data
We rely on a small set of processors to run the site and its assistants: Google (Gemini API for voice, Google Analytics 4 for consented analytics), Microsoft (Clarity, for consented session-replay and heatmap analytics), a self-hosted n8n automation instance (routing enquiries and leads), our CRM (storing and managing leads), Cloudflare (content delivery and security), and OVH (server hosting).
Each processor only handles the data needed for its function, under our instructions.
Legal bases and purposes
We process contact, chat, voice, and lead data to respond to your enquiry and pursue our legitimate interest in following up on business opportunities you initiate.
We process analytics data only on the basis of the consent you give through the cookie banner. You can withdraw that consent at any time.
How long we keep it
Leads and enquiry records: up to 24 months after our last contact, then deleted or anonymised.
Chat and webhook processing logs: up to 14 days, for troubleshooting and delivery, then deleted.
Voice: we keep no audio recordings. When optional voice memory is enabled, raw transcribed turns expire after 30 days and extracted factual memory expires after 90 days unless reconfirmed or deleted earlier by you.
Your rights
You can ask us to access, correct, or delete your personal data, and to withdraw a consent you previously gave. To do any of these, email [email protected].
Under Thailand’s PDPA you may also lodge a complaint with the Personal Data Protection Committee (PDPC). If you are in the EU/EEA, the GDPR gives you equivalent rights and the ability to complain to your local supervisory authority.
Cookies and local storage
We use Google Analytics 4 and Microsoft Clarity cookies only after you accept analytics in the cookie banner — both run behind the same single consent choice. Until then, no analytics cookies are set and no session replay is recorded.
We store your cookie choice in your browser’s local storage (the analytics_consent key) so we remember your decision. You can reopen the banner and change your choice at any time from the "Cookie preferences" link in the footer.
Voice personalization uses a separate, optional first-party identifier (unthai_voice_id) only after you select “Remember useful details”. It is not based on your IP address and is not enabled by analytics consent. You can use “Forget my saved voice memory” to remove the identifier and request deletion of the associated memory.