Michika — Privacy Policy

Last updated 18 November 2026 · Terms of Service
本頁以英文版本為準,中文版本日後提供。 · 本ページは英語版を正文とします。日本語版は今後提供します。

1. Overview

This policy explains what the Michika service collects, why, and what your choices are. It covers the Michika app on your phone (iPhone or Android) and on your car's screen (Apple CarPlay, or a car display running Michika), and the servers behind them; where something differs by platform, it says so. Michika is operated by Jen Hao Yeh, an individual established in Taiwan (R.O.C.), who is the data controller for the purposes of this policy; contact support@michika.app. A postal address for formal notices is available on request; we answer within 30 days.

The short version: we collect what the product needs to work and to be run well — your sign-in identifier (Apple's on iPhone, Google's on Android), the places you ask to navigate to, where you are while guidance is running (kept only while that drive is live), a limited history of your drives, and information about how you use the app. We do not sell your data, there are no ads inside the app, and we do not track you across other companies' apps and websites — the app never asks for permission to track and never reads your device's advertising identifier. Our website, michika.app, uses Meta's pixel to measure our ads, with your consent where the law requires it (section 8).

2. What we collect and why

DataDetailsWhy
AccountOn iPhone: your Sign in with Apple identifier and, if you choose to share it, your email address (which may be an Apple private-relay address). On Android: you sign in with your Google account; we keep Google's identifier for it and your email address when Google says it is verified, and nothing else from your Google profile. A Google sign-in is its own Michika account, separate from an account you have through Apple: plans and trials do not carry over between them. We do not send marketing email.Creating and securing your account, and answering you if you write to us.
Location and navigationLocation information your device sends when you plan a route, search for a place or use a location-aware feature, and the destinations you choose. Your recent destinations are kept on your phone.Providing navigation, search and guidance.
Live position while navigatingWhile guidance is running, the app sends your current position, speed, heading and the distance and time left on your route about every 10 seconds. Our operators can see it live, with the path of that drive so far. It is deleted 10 minutes after the last position the app sends, so it does not become a history of where you have driven.Supporting you during a drive, and checking that navigation and guidance work.
Route and search historyFor routes and searches handled by our servers: an approximate start and end point, the route, its distance and estimated time, when it was requested, and what you searched for.Diagnosing navigation problems, improving the Service, and helping you when you contact support.
Usage and drive activityWhen and how long you use the app, on which screen, app and system versions, navigation events during a drive (for example that a route started, rerouted or arrived), the approximate city and country where a drive started, and counts of the features you use.Understanding how the Service is used, keeping it reliable, enforcing plan limits, and supporting you.
Install source (Android)When the Android app first opens, Google Play tells it where the install came from, if it came from a link: the campaign details in that link (such as source, medium and campaign name, and Google Ads' click identifier), and the times of the click and the install. Without a link it says so and there is little to keep. We store it once with your account, and delete it when you delete your account.Knowing which of our own ads brought people to the app, so we can improve them.
Guidance contentThe text of the guidance and phrases the app delivers to you, which can include a road or place name, with its language and the character voice used. It does not include your coordinates or any recording of you.Checking quality and fixing faults.
Product feedbackIf you send feedback in the app: your message, any images you attach (with their metadata removed), the category and the time. Only authorized Michika operators can read it. An operator may have the text you wrote machine-translated by an AI service provider, to read it in their own language.Reviewing suggestions, bug and subscription reports, and inquiries.
Conversations (Max)With a Max plan on iPhone or Android, you can turn Chat on and talk to the character, by voice, or by typing while no route is running. To write her replies we send our AI service provider, OpenAI: the words you and she have said in the current conversation, your language, her notes about you (below) and, while you are driving, your location rounded to about 11 m. Each line, yours and hers, is also checked by OpenAI's moderation service, and a reply that fails the check is replaced. OpenAI processes this under its API terms and data controls. We do not send it your sign-in identifier or email address. We ask for your permission once in the app (Allow or Not now) before the first conversation, and you can withdraw it at any time in Settings ▸ Chat.
Transcript. We keep it on our servers until you delete it (Settings ▸ Chat ▸ Delete conversation history) or delete your account. We may review conversations, including lines our safety checks flag, to run and improve Chat, tune her replies and keep the service safe. If you Report a reply (a long-press on it), that reply, the line before it and any note you add go to our operators' inbox, like product feedback.
Her notes about you. She keeps up to 10 short notes about you, for example what to call you or your car, so she remembers between drives. All characters share them, and they are sent to OpenAI with each turn. She does not note health, religion, politics, an exact address, phone numbers or anything about a child. You can read, edit and delete them in Settings ▸ Chat ▸ What she knows about you; they are deleted with your account.
Voice. On iPhone, speech is turned into text on your iPhone, so no audio is sent to us or to OpenAI. On Android, the app records nothing itself and sends us no audio: your phone's own speech recognition service turns your voice into text, and only that text reaches us and OpenAI. We ask the service to work on the device where your language allows it; where it cannot, your phone's speech service (Google's, on most phones) may process the audio under its own privacy policy.
Providing the conversation, keeping her replies safe, and remembering what you asked her to.
My looks (Max)If you build looks for a character in the Character Studio and save them: the look's name, the choices that make it up (such as style and colours) and a small preview picture. They are stored on our servers with your account, so they appear on your other devices, and they are deleted when you delete your account.Keeping your saved looks and showing them where you sign in.
Subscription statePurchase and renewal information from the store you bought from — Apple (App Store) or Google (Google Play): product, dates, and a reference linking the purchase to your account; for Google Play, the purchase token our server verifies with Google and Google's notifications when the subscription renews, changes, ends or is refunded. Never your card details. Activating and managing the plan you paid for.
Device and security informationTechnical identifiers needed to protect licensed content on your device, and the request logs our hosting provider keeps (including IP address).Security, abuse prevention, protecting licensed content and fixing faults.

The microphone is used only for voice chat: the app asks for it (on iPhone, and for speech recognition), the first time you turn Chat on, and never at launch. Without it you can still type to her. On Android, while guidance is running the app shows a notification for as long as it uses your location; it does not ask for background-location permission. These records can be viewed, per account, by the operator to run the Service and to answer you when you write to us. They are not shared with anyone for their own purposes, not used for advertising, and not combined with data from other apps or companies.

3. Who processes it

We use service providers that process data on our behalf, each receiving only what its function needs and bound to protect it:

Data may be processed outside your country, including in Japan, Taiwan and the United States. We do not sell your data or share it with data brokers.

4. Retention and deletion

5. Security

Data is encrypted in transit and at rest, and access is limited to the operator. Payment card data never touches our systems.

6. Children

Michika is intended for people aged 16 or over (or older, where the law where you live sets a higher minimum age), as set in our Terms. We do not knowingly collect data from anyone under 16; if you believe someone under 16 has used the Service, contact us and we will delete the data.

7. Your rights

Depending on where you live, you may have rights to access, correct, export or delete your personal data, and to complain to a supervisory authority. Deletion is self-service in the app. For anything else, contact support@michika.app — we will respond within 30 days. We will post the current policy here and note material changes in the app.

8. Our website

michika.app uses the Meta Pixel to measure our ads on Facebook and Instagram. When it is on, your browser tells Meta which of our pages you opened and whether you tapped the App Store link, with your IP address, browser details and a cookie Meta sets (_fbp). Meta may connect this to your Facebook or Instagram account under Meta's privacy policy; we see only aggregated ad results.

If your browser reports a time zone in the UK, the EU, the EEA or Switzerland (or none), nothing is sent to Meta until you press Accept on the banner. Elsewhere it is on when you arrive. Either way, the "Ad measurement" link at the bottom of every page turns it off or on. Your choice is kept in your browser's local storage, and turning it off deletes Meta's cookie. Separately, our hosting provider's request logs record the web address you open, including any campaign tag in it (such as utm_campaign), which is how we count visits from our ads. We also count, per campaign, visits to the home page and taps on its App Store button: counts only, with no cookie and nothing that identifies you. That button passes the campaign's name to the App Store, and Apple reports App Store visits and downloads to us only as totals.