Privacy Policy
Last updated: 4 November 2026
HipiMind is a voice-first travel assistant operated by DUOCODE TECHNOLOGY (business registration no. LA0087244-A, Malaysia) (“we”, “us”). We are the data user in respect of the personal data described here, within the meaning of the Personal Data Protection Act 2010 (Act 709). This policy explains what we collect and why. Questions: contact@hipimind.com.
Notis Privasi ini juga tersedia dalam Bahasa Malaysia.
What we collect
- Account — your email address and authentication identifiers, managed through Supabase Auth (including Google sign-in if you use it).
- Your content — the conversations, trip itineraries, and preferences you create while using HipiMind, so they are available across your sessions.
- Voice — audio you speak is processed to provide real-time replies and audio guides. We store the resulting transcript as part of your conversation, not the raw audio stream. The one exception is a problem you report on a reply: the recording of what you said in that exchange is attached to the report so we can hear what went wrong.
- Photos, files, camera and location — photos and files you attach are stored with the conversation. Frames from the live camera, and your location when you allow it, are used to answer the question you asked and are not stored.
- Accessibility settings — only if you set them: how much you can see and since when, whether you travel with a cane, guide dog or wheelchair, and how you want answers spoken and described. This is information about your health. It is kept on your device and sent with each voice session so that replies and camera descriptions fit you. It is stored on your account only if you turn on “Keep these settings on my account” in the accessibility settings, and turning that off removes it from your account.
Apple Watch heart rate
The Apple Watch app has one page that reads Apple Health — Heart Rate — and only while you have it measuring. The iPhone app reads one thing from Apple Health too, and only with its own switch on, described under Noise around you below.
What it asks for. The first time you tap Start on that page, the watch asks Apple Health for permission to read your heart rate, and for permission to save a workout. Both are Apple’s own permission sheets, and either can be refused. It also asks for your location, which the compass on that page needs to say which way you are facing: we never read, keep or send your position.
Why a workout. Apple lets an app on the watch read heart rate frequently only during a workout, so measuring starts one. It is the generic kind, with no training programme behind it and no score at the end.
Where the reading goes. It stays on your watch. The reading is shown on that page and held in memory while you measure; it is not sent to your iPhone, not to our servers, and not to any AI model: the watch app has no network code of its own, and the iPhone app ignores the sensor readings the watch sends it. Heart rate never reaches your conversations, your trips or your account. The only thing that leaves that page is the workout the watch saves into Health when you stop, described next — a record we cannot read. The heading and stability figures stay on the watch in the same way.
What is stored, and for how long. We store nothing. The one thing written down is the workout itself, saved into Apple Health by the watch when you stop, together with the heart-rate samples Apple collected during it and whatever else Apple records for a workout on the watch, such as distance (the session asks for an outdoor one). That is Apple’s record on your own devices, and it stays there until you delete it in the Health app. We cannot read that workout back — the iPhone app’s only access to Apple Health is the noise level described under Noise around you.
How to turn it off. Tap Stop on the watch page and measuring ends immediately. To withdraw the permission itself, use the iPhone: Settings → Health → Data Access & Devices → HipiMind, or the Health app under your profile → Privacy → Apps → HipiMind. Deleting the watch app removes its access as well. Without that permission the page shows no reading.
Noise around you
With Shorter answers when it is loud turned on, a loud place makes the next answer a little shorter. The switch is off until you turn it on, and an answer length you chose yourself always wins.
What is read. On an iPhone, the environmental noise level your Apple Watch saved in Apple Health in the last few minutes. The first time you turn the switch on, Apple’s own permission sheet asks to read it, and you can refuse. Headphone audio levels are not read: they say how loud your own audio plays, not how loud it is around you. The number is read on the phone and forgotten there. What leaves the phone is one of three words — quiet, moderate or loud — and only while a conversation is open. No recording, no decibel figure, and nothing is written back into Apple Health.
Where the word goes. To our server, which uses it only to choose how long the next answer is. It is kept in memory for that conversation and is gone when the conversation ends; it is not stored or logged. The AI model that writes the answer never sees it: it is only told how long the answer should be.
When there is no such reading. A browser cannot read Apple Health or Health Connect, and neither can an iPhone you have not allowed. There the level is estimated from the microphone that is already open while you hold the talk key or have hands-free on. That estimate never opens the microphone on its own and never asks for a permission of its own, and again only the word leaves the device. Android has no noise reading in Health Connect, so the Android app, which is the website, uses this estimate too.
How to turn it off. Turn the switch off and the word stops at once. To withdraw the Apple Health permission itself, on the iPhone: Settings → Health → Data Access & Devices → HipiMind.
Payments
HipiMind Plus is billed by Stripe. Stripe handles the card details — they never reach our servers. What we keep is the record of the subscription itself: the Stripe customer and subscription identifiers, which plan you are on, whether it is active, and when the current period ends. That is what the app reads to decide whether Plus is switched on for you.
When you start a checkout, our analytics records that the checkout started and that the payment went through, with the plan and the checkout session's identifier, which our payment records link to your account, so that we can count how many checkouts are finished.
Analytics
Our own analytics is a self-hosted Umami instance. It is cookie-less — it stores no identifier in your browser. It groups visits from the same network and browser within a calendar month and starts afresh each month; it never learns who you are. What it records is which pages and features are used and an approximate region derived from your IP address. We do not load Google Analytics or an advertising network’s tag. We also load Cloudflare Web Analytics, a cookie-less beacon that counts page views and measures page performance; it stores no identifier in your browser and sends aggregated measurements to Cloudflare. It does not load on shared-trip links, debug links or the account-deletion page. Three third-party scripts load on this site: the Cloudflare beacon just described, the Travelpayouts affiliate script, described next, which records how the site is used and which you can switch off, and the feedback widget, described after it, which sends nothing until you use it.
Travelpayouts affiliate script
What it is and why. HipiMind earns commission through Travelpayouts (operated by Go Travel Un Limited, Hong Kong), an affiliate network for flight, hotel and activity providers. Its script proves to Travelpayouts that we own this site, counts clicks on links to travel providers, can turn such a link into an affiliate link, and, depending on its settings, can open a partner’s offer. A booking made through such a link costs you the same; we may receive a commission.
Where it runs. Only on the product pages — the planner, pricing, about and the feature pages. It does not run on the travel guides, these legal pages, contact, shared-trip or debug links, or inside the Android app.
What it collects. The address of the page, a copy of the page’s text, the links on it and your clicks, and technical details of your browser and device including your IP address. It is sent to Travelpayouts’ servers (emrld.ltd). We see aggregated click and booking statistics in our partner account, not individual records.
What it stores in your browser, and for how long. Cookies am_user_session (a session identifier, expiring about 30 minutes after your last activity), and bb-session and bb-session-2 (set for all of hipimind.com, kept for about 30 days, used to limit how often an offer is shown); and local-storage entries named mn: followed by a page address. Travelpayouts keeps what it receives under its own privacy policy.
How to turn it off. Use the switch below: the script then no longer loads in this browser, and switching it off also deletes the cookies and storage it left on this site. The choice is kept in a cookie of ours, hipimind_affiliate_optout, for a year, so clearing your cookies resets it. If your browser sends Global Privacy Control, the script is not loaded at all. Blocking emrld.ltd in your browser has the same effect.
Feedback widget
What it is and why. The small Feedback button in the corner of the page opens a short form for telling us what is broken or what you wish existed. It runs on our own feedback service, Agentic CS (agenticcs.net) — not an outside company.
Where it runs. On this website’s product pages and its marketing and guide pages. It does not run on shared-trip or debug links or the account-deletion page, which load no third-party script at all.
What it collects. Nothing until you press send. Then it sends what you typed, the screenshots you chose to attach (at most three), and — if you are signed in — your account identifier, email and name, so we can reply. Signed out, it sends a random id generated in your browser instead.
What it stores in your browser, and for how long. When you are not signed in, one local-storage entry, agentic-feedback-anonymous-id, holding that random id; it stays until you clear this site’s storage. No cookies.
How to turn it off. The script sends nothing on its own, so leaving the button unpressed is enough; blocking agenticcs.net in your browser removes the button too.
Service providers
We use third-party services to run HipiMind. Each receives only what the feature you are using needs.
- Accounts, database and file storage — Supabase. Hosting — Vercel (this website) and Render (our API).
- Answers and camera descriptions — what you type or say, the photos and camera frames you share, the place you are asking about and your accessibility settings are sent, directly or through our own model gateway and the Neon AI Gateway it uses, to the AI model that answers: OpenAI, Anthropic, Google, xAI or Amazon Web Services, depending on the model.
- Speech — your voice is streamed to Deepgram to be turned into text. Replies and audio guides are read aloud by Deepgram, ElevenLabs, MiniMax or Cartesia, which receive the reply text, never your audio.
- Places, maps, routes and weather — place names, search terms and coordinates go to Google Maps Platform, Geoapify, OpenStreetMap routing services and OpenWeather. The map itself is loaded by your browser from OpenFreeMap, which therefore sees your IP address and the area you view. Pictures and facts about places come from Wikimedia Commons and Wikidata.
- Web search — search terms drawn from your question go to Exa, TinyFish, AnySearch and AgentKey.
- Travel prices — destinations and dates go to Travelpayouts (flights) and LiteAPI (hotels).
- Product feedback and contact messages — what you submit through the Feedback button, and the name, email address and message you send through the contact form, go to Agentic CS (agenticcs.net), our own feedback and support service, so we can track and answer them. The feedback button is described above.
- Payments and analytics — Stripe, our self-hosted Umami and Cloudflare Web Analytics, all described above. Travelpayouts’ affiliate script is described above too.
How we use your data
We use your data to provide and improve the service: authenticating you, remembering your trips and preferences, and generating itineraries and audio guides. We do not sell your personal data. The affiliate script above sends Travelpayouts the data listed there so that bookings can be attributed to us, and you can switch it off.
Deleting your account and data
You can delete your account yourself, at any time. On the web or in the Android app, sign in, open the account menu and choose Delete account, or go straight to hipimind.com/account/delete. In the iPhone app, open Account and choose Delete account. The deletion happens at once and cannot be undone. If you can no longer sign in, email contact@hipimind.com from the address you signed up with and we will delete it for you.
What gets deleted. Your account and its authentication identifiers; the conversations, itineraries and preferences you created; the transcripts kept from voice sessions; the photos and files you attached and any recordings attached to problem reports; every share link you made; and your accessibility settings if they were kept on your account. If you subscribed to Plus, the subscription is cancelled at Stripe at the same moment, so you are not charged again, and our record of it goes too; Stripe keeps its own billing records, which we cannot delete on your behalf. To remove a single conversation or itinerary instead, email us and we will do that without touching the rest.
Your other choices
Email the same address to see or correct what we hold. Signing out ends your session on this device at any time.
Under the Personal Data Protection Act 2010 you may also ask us to limit how we process your data, and withdraw a consent you previously gave — write to the address above and we will act on it. Withdrawing consent for something the service depends on may mean we can no longer provide that feature. If you are not satisfied with how we have handled a request, you may complain to the Personal Data Protection Department (Jabatan Perlindungan Data Peribadi), Malaysia.
Language
This notice is published in English and in Bahasa Malaysia (Notis Privasi). If there is any conflict or inconsistency between the two versions, the English version prevails.
Notis ini diterbitkan dalam bahasa Inggeris dan Bahasa Malaysia. Sekiranya terdapat sebarang percanggahan antara kedua-dua versi, versi bahasa Inggeris yang akan digunapakai.
This policy may be updated as the product evolves; material changes will be reflected by the date above.