Miki is an AI travel companion. This policy explains what information the app collects, why, and what control you have over it. It applies to the Miki mobile app and its backend services.
| Category | What it includes | When |
|---|---|---|
| Account info | Email address, password (stored hashed, never in plain text), full name. If you sign in with Apple or Google, the name and email address they share with us (Apple may give us a private relay address instead of your real one) | When you sign up or sign in |
| Sign-in sessions | For each device you're signed in on: the network (IP) address and device type of the session, kept by our authentication provider (Supabase) while the session lasts, to keep your account secure | When you sign in |
| Sign-up network address | The network (IP) address a sign-up request comes from, used only to limit automated or abusive sign-ups. It isn't linked to your account or profile, and it's deleted automatically within a few hours | When someone signs up for an account |
| Profile | Profile photo, travel persona, and a username (an @handle of 3–20 letters, numbers or underscores, unique to you), which is what other people see on the comments and ideas you post. A profile photo (and a trip cover image you upload) is stored at a web address that is not listed anywhere but that anyone who has the link can open, even when signed out, so don't use a photo you wouldn't want seen | When you set one, or when Miki infers one from your activity (see "How we use it"). A username is chosen when you sign up, or later in Settings |
| Waitlist email | An email address you enter to join the waitlist when Miki is invite-only | When you tap "Join the waitlist" on the sign-in screen. It is used only to tell you when there is room, and to let you sign up when you are invited |
| Trip data | Destinations, dates, itinerary events, flight/hotel/booking details, traveler names on bookings, and the map coordinates of places, looked up from place names so they can be shown on your trip's map | When you add a trip or upload a confirmation |
| Uploaded documents | Booking confirmations (PDFs, screenshots, photos) you upload or photograph (please don't upload passports or ID cards; a booking confirmation is all Miki needs), including ones you share into Miki from another app (like Photos or Mail) using your device's own Share function; Miki also keeps each file's name (for example "Flight to Tokyo.pdf") so you can tell your documents apart, and deletes it with the document | When you upload, capture, or share one in |
| Trip memories (photos and videos) | Photos and videos you pick from your phone's gallery for a trip's Memories tab. Miki keeps a private copy inside the app on that phone only (with any like or note you add): they are never uploaded to Miki's servers, never shown to anyone else, and are not read by Miki's AI. Miki only sees what you choose in the phone's own photo picker | When you add them in the Memories tab |
| Shared trip invitations | The email address of someone you invite to a shared trip — even if they don't have a Miki account yet | When you invite someone to a trip |
| Public itinerary shares | An itinerary you choose to publish to the Explore tab — destination, dates, a cover image (see "Who we share it with"), your display name and profile photo (always shown with a published trip). A published trip stays in step with your trip: when you change its title, destination, dates or activities, the published copy updates automatically (activities waiting for the lead traveller's approval are left out, and a venue is shown by name only, never a street address). Remove it from Explore to stop that | When you publish a trip to Explore, and again whenever you change that trip |
| Country of residence | Shown as a flag next to your name on your own Profile screen and as a home marker on your travel map, and as a flag next to your name on your public profile page that other Miki users can open (for a private account, only to people who follow you) | When you sign up or update it in Profile |
| Discussion wall posts | A short message you post on another Miki user's profile page, or one posted on yours — always shown under your real name, not anonymously | When you or someone else posts to a wall |
| People you block | Which accounts you've blocked. Blocking hides their content from you, and yours from them. They aren't told you blocked them | When you tap Block |
| Follows | Which published-itinerary authors you choose to follow. Shown to others only as a total count — who specifically follows an account is never shown to anyone but that account itself | When you follow someone from Explore |
| Travellers search listing | Public accounts are listed in the Travellers tab on Discover, and a private account appears only when someone searches for it by name (at least three matching characters). A listing shows the account's display name, profile photo (if set), travel persona (if it has one) and number of followers. For a public account it also shows how many trips it has completed and how many countries those trips visited. Never trip titles, places, dates, bookings, documents or an email address | Automatically, for every account; what else is shown depends on your Account privacy setting |
| Follow requests | If you follow a private account, a request containing your name is sent to that account until they accept or reject it. If you switch that setting on yourself, requests from people who want to follow you are listed in the bell in the app's top bar | When you tap Follow on such an account |
| Requests for trip ideas | If you switch on "Ask followers for ideas" for a destination you're planning — the destination, your name, and the titles of the activities you've added to that destination so far (plus a short note, if an earlier request of yours has one). No dates, times, locations, booking details, or documents | Only when you switch it on for that destination |
| Booking links (the "Find booking links" button) | When you tap "Find booking links" on a tentative plan: for each activity you ticked, Miki searches the web through our AI provider, sending the activity's title, type, date, time, place, airline and notes (the details line), the plan's destination and the titles of the other activities you ticked, and never your name or account details; dates, travel party, rooms and budget are not asked or sent. Before sending, Miki removes the obvious personal details it can recognise from those words (e-mail addresses, phone numbers, web addresses, booking references and a title such as Mr or Mrs followed by a name); this is a best-effort filter, so please still don't type names, booking numbers or other personal details into an activity. We keep the result per activity (up to three sellers Miki found with their web addresses, ratings and the prices shown) so you can see it again. Prices are shown only in your home currency, at today's exchange rate; a price Miki cannot convert is not shown. Miki does not take payment, make the booking or see what you do on another website: you open the seller's own website and enter your details and pay there, under its own privacy policy. Miki receives no commission from sellers and adds no affiliate or tracking codes to their addresses. Prices and ratings come from public web pages and can be out of date. A booking confirmation you attach to an activity with its page icon is stored like the other documents you add to a trip | Only when you tap "Find booking links"; a confirmation only when you attach one |
| Chat messages | What you send Miki and its replies, kept so conversations have memory | Every message you send |
| Ratings of Miki's replies | A thumbs up or thumbs down you give a reply from Miki, and optionally a reason you pick (wrong, incomplete, not helpful, too slow). We record which reply it was about, but never copy the text of your conversation into the rating | Only when you tap a thumb on a reply |
| Location | Your live location, only while the app is open and only if you've granted permission. It's used to suggest real places near you and to work out which country you're in (so Miki can give the right emergency numbers). We don't store it or keep a history of where you've been, with one exception: a location you choose to send in a private chat is stored with that message (see "Private chats"). To turn coordinates into a place name, your phone asks Apple's or Google's mapping service | When you open Miki chat, or ask about nearby places |
| Device permissions | Camera and photo library access, only when you use a feature that needs them; notifications, only for the alerts described below | When you photograph or pick a document/photo, or when Miki has something to tell you about a trip |
| Reports you file | If you report a post, comment, published trip, profile or private message: what kind of content it was, which item, the reason you chose, any note you add, and a short excerpt of the reported content and who wrote it, so we can act on the report even if the content is later deleted | Only when you tap the flag icon and send a report |
| Feedback | Whatever you write in Settings → Share feedback, along with your account email so we can follow up. You can also attach up to 3 screenshots of an app problem. They're stored privately and emailed to our team, and may show anything that was on your screen, so only attach what you're comfortable sharing | When you submit feedback |
| Private messages | The messages you send in a private chat with another traveller: the text, any photo, document (PDF, Word, Excel or text file, up to 10 MB) or location you attach, and when each was sent; and when you last opened the conversation (to show what is unread) | When you send a message. Only you and the other person in the conversation can read it; it is not visible to your followers or anyone else |
| Notification engagement | Which kind of notification we sent you, when, whether you opened it, and whether you then did something related in the app shortly afterwards (such as asking Miki about that trip). We use this to judge whether our alerts are useful | When we send you a notification, and when you open it |
| Device time zone | The time zone your phone is set to (for example "Asia/Kolkata"), saved with your push notification token. We use it only to time a notification on your own clock, such as a check on your day's plan an hour before your first activity | When the app registers your phone for notifications, and again if your phone moves to another time zone |
| Usage statistics | Which phone type you use (iPhone or Android), the app version, whether you opened the app on a given day, and how many times you used each screen or feature (for example, opened chat or created a trip). Only counts: never the content of a screen, a message, a place or a person. You can switch this off in Settings → Share anonymous usage statistics. We use it to see how many people use Miki and which parts are useful, and to decide what to improve | When you open the app and use a screen or feature, unless you switch it off |
| Crash and error data | Technical details about a crash or error — what happened and where in the app, device/OS type — never trip content, messages, or documents | Only if the app crashes or hits an error |
We don't use advertising SDKs or third-party analytics tools of our own. On Android, Google's Maps software collects the technical data described in the Google Maps row to run its map service. We don't collect anything beyond what's listed here. The measuring described above (how AI replies and notifications perform) happens on our own servers.
We don't sell your data, and we don't use it to train AI models beyond what's needed to generate your own replies in the moment.
Other Miki users, if you share a trip. Miki lets you invite specific people to a trip by email — this is entirely opt-in, and only happens if you send an invite or accept one someone sent you. You choose the access level for each person you invite: view-only, or full edit access. Whoever accepts can see that trip's itinerary, events, and any documents uploaded to it, including ones they didn't personally add. If you invite someone who doesn't have a Miki account yet, we hold their email address and the invitation until they sign up with that same email or the invitation expires (see "How long we keep it") — we don't use that email address for anything else. This doesn't apply to trips you haven't shared, your chat history with Miki, or your Memories photos and videos — those stay visible only to you.
Every Miki user, if you publish to Explore. The Explore tab is a public feed of itineraries other travelers have chosen to share — anyone signed in to Miki can browse it, not just people on your trip. Publishing is entirely separate from sharing a trip with specific people and is always your choice: it copies a copy of that trip's itinerary, destination, and dates, and your display name and profile photo, which are always shown with a published trip (there is no anonymous option). After you publish, the published trip follows your trip: when you add, change or delete activities, the published copy is updated automatically (still without booking references, traveller names or street addresses), and deleting the trip deletes its published copy. If your account is Private (Account privacy in Settings), a published trip is shown only to people who follow you. A trip you published anonymously before this change stays anonymous until you update it; updating it adds your name. You can update or remove a published itinerary at any time from the Explore tab.
Trips other travellers build from yours. Anyone who can see a published trip can tap "Clone this" to add a separate tentative plan of their own (a draft they can later turn into a trip) built from it. What is copied is the trip's title and destination (with its map position) and, for each activity, its title, time, place name, airline and icon. Your name and profile photo, your own uploaded cover photo, your uploaded documents, your Memories photos and videos (which stay on your phone) and any amounts you spent are not copied, and nothing on the copy points back to you or to your published trip. We don't tell you when someone builds a copy. To keep a count, Miki records separately which account built a copy of which published trip (once per account per trip, not the copy itself) and shows the total as "trips inspired" on your entry in the Travellers list, to people who can see your trips: for a Private account, only your followers see it. It shows how many, never who. That record is deleted if either account is deleted. A copy belongs to the traveller who built it and stays in their account when you remove your published trip or delete your account.
The cover image on a published trip. A published itinerary has a cover image. The card uses your trip's own cover image, which can be a photo you uploaded yourself, so every Miki user who can see the trip can see that photo. A trip with no cover image of its own gets a royalty-free stock photo for the trip's main destination (the country or place in its name). If you later change the trip's cover image, the published card follows it. A trip you published anonymously before this change keeps a stock photo instead of your own photo until you update it. Removing the published itinerary or deleting your account removes the card and its image.
Seller websites, if you use Find booking links. Miki shows a seller's web address. Your phone opens it only when you tap, in your browser. Miki sends the seller nothing and receives nothing back, and the seller's own privacy policy applies. We receive no commission from sellers and add no tracking or affiliate codes to their addresses.
Your username. Your username is not secret. Other Miki users can find you by it in the Travellers search, see it next to your name there, and tag you with it (@username) in a comment. Anyone can ask whether a username is already taken (we answer only "available" or "taken", never who has it), and that is how we stop two accounts having the same one. Someone you have blocked, or who has blocked you, can't find you by your username.
When someone tags you in a comment. If another traveller writes your @username in a comment on a published trip, we send you a notification saying who tagged you, the name of the trip and the first part of the comment. We do this only if you can see that trip, and never if you and the person who tagged you have blocked each other. A comment can tag at most five people, and one person can tag at most thirty times an hour. To do this we record, separately from the comment, who was tagged in which comment; it is deleted with the comment or with either account. Tapping the notification opens the comment.
Private chats. A private chat is a conversation between you and one other traveller, and only the two of you can read it, including any photo, document or location in it. You can message someone you follow or who follows you, and neither of you can if either has blocked the other (blocking hides the conversation from both). Attachments are stored privately and are opened through a link that stops working after an hour. Deleting one of your messages removes it, and its file, for both of you. Deleting your account deletes every conversation you are in, with both people's messages and their files, and the other person loses that conversation. When you receive a message we send a notification showing the sender's first name and the start of the message (or "Sent a photo"), through the notification services described below. If you report a message, we read it to decide what to do, and we keep a short copy of its text with the report; we do not read private messages otherwise. These private chats are separate from the posts on a profile's discussion wall, which stay visible to that person's followers.
Anyone who follows you, or visits your public profile. Tapping a published itinerary's author name opens a read-only view of their other public trips, plus a discussion wall where the profile owner and their followers can post short messages to each other — always shown under real names, never anonymously. Following someone is visible to others only as a total count; the identity of who follows a given account is never shown to anyone but that account itself.
Your followers (or everyone, if your account is public), if you ask for trip ideas. In the Plan tab, you can switch on "Ask for ideas" for a destination you're planning. This is off by default and set separately for each destination. When it's on, a card appears in the "Recommend" list on Discover: if your account is private, only people who follow you can see it; if your account is public, everyone signed in to Miki can. It follows your Account privacy setting at the moment someone looks, so changing the setting changes who can see an open request straight away. The card shows that destination, your name, and any short note from an earlier request. If someone who can see it opens it, they can also see the titles of the activities you've added to that destination so far, and join a discussion about it — nothing else: no dates, times, locations, booking details, or documents. Anyone you've blocked can't see it. Replies are posted as messages on your discussion wall, under real names like any other wall post, and are visible to you and your followers. Miki doesn't send a push notification for a request, so followers only see it if they open Discover. You can switch it off at any time.
Every Miki user, through Travellers search. Anyone signed in to Miki can find you by name in the Travellers tab on Discover and see your display name, profile photo, travel persona and follower count. Whether they can see more is set by Account privacy in Settings, which is Private for new accounts. A public account also shows its trip and country totals, and the trips it has published to Explore, to everyone. A private account shows those only to people it has approved as followers, and anyone else must send a follow request first. People you have blocked, and people who have blocked you, never see you in the list. You can change this at any time and it takes effect straight away.
Accounts that approve new followers. A public account can be followed instantly by anyone signed in to Miki. A private account (the default for new accounts) works differently: someone who taps Follow sends you a request showing their name, which you accept or reject from the bell in the top bar — tapping it opens their profile. They are not a follower, and can't see anything that is limited to followers, until you accept. People who already followed you stay followers. A request is removed when you answer it, when the person withdraws it, or when either of you blocks the other; it's also removed if either account is deleted. Switching Account privacy to Public makes new follows instant again; requests already waiting stay in your list until you answer them.
We also use a small number of service providers to run the app. Each only receives what it needs to do its job:
| Provider | What they receive | What they do |
|---|---|---|
| Supabase | All account and app data | Database, authentication, file storage, and backend hosting. Hosted in Tokyo, Japan. |
| Anthropic (Claude) | Your messages, trip/itinerary context, uploaded documents, and profile details (name, travel persona); for upcoming events, the specific flight/venue details needed to search the live web for delays, cancellations, or closures; for the pre-trip check-in in the days before a trip, the trip's destination, dates, and itinerary; when location is on, the names of real places near you and your country, so Miki's answers fit where you are; when you ask Miki about a destination, the general question needed to search the live web for current guidance (opening hours, prices, entry requirements, local conditions); so that Miki can answer from any screen, the "Ask for ideas" posts on your own profile wall, the posts in your trips' discussions, the names of your co-travellers, who invited you to a trip, and your country of residence and account privacy setting; when you tap for tips on an activity in a published trip, only the activity's title, place and destination (no name or account) to search the live web, with the answer kept for everyone who taps the same place; for a booking-links search, the activity's title, type, date, time, place, airline and notes, the plan's destination and the titles of the other activities you ticked, to search the live web (no name or account details) | Generates Miki's replies, extracts itinerary data from documents, infers your travel persona, checks upcoming events against current public information, and looks up current destination guidance you ask about |
| Overpass (OpenStreetMap data) | Your live coordinates, when you use Miki chat with location on | Looks up real places near your current location |
| LocationIQ | The destination, and the place or title of itinerary activities so they can be found on a map (when an activity has no place of its own, its title is sent with the trip's destination, but only for hotels, restaurants and activities, never for trains, buses, cars or untitled entries; for a flight with no airport of its own, only a city name and the word "airport", never the flight's other details); and, when location is on in Miki chat, your coordinates, to find out which country you're in | Turns place names into map coordinates (used for your trip's map, the itinerary and your personal travel map) and your position into a country |
| Google Maps (Android) | While you view a trip's map on Android: your device's IP address and the area of the map being shown, as Google's map service requires to send you map images. Google's Maps software also receives technical information about your device and the app (such as device identifiers, the device model and operating system version, and the app version), crash reports and error data from the map software, and may record how you interact with the map (such as panning and zooming); Google handles this under the Google Privacy Policy. The pins and route are drawn on your device, and your name, account, and itinerary details are not sent to Google | Draws the map at the top of a trip, with your activities plotted on it |
| Google Maps (when you tap Directions) | Only when you tap Directions on a place on your trip's map: that place's coordinates, passed to the Google Maps app, or to Google Maps in your browser if the app isn't installed. Miki does not send your own location; Google Maps finds it itself, under your phone's permissions and the Google Privacy Policy | Opens directions to that place. A one-way hand-off: nothing comes back to Miki |
| Sentry | Crash and error technical details (see "What we collect"), stored in the EU | Crash and error monitoring, so we can find and fix problems |
| Expo | A device push token, and the notification content described above | Relays the notification to Apple's own push service for delivery to your device |
| Apple | Crash and performance data collected by the OS itself; the notification, for final delivery; if you use Sign in with Apple, the sign-in itself | App distribution, platform-level diagnostics, push notification delivery, and Sign in with Apple |
| If you use Sign in with Google, the sign-in itself and the name and email address Google shares with us | Sign in with Google | |
| Openverse | A trip's main destination (the country or place in its name), only when a cover image is needed: a trip with no cover photo of its own | Finds a royalty-free stock photo to use as the cover image |
| Resend | Your email address and the content of the account emails we send you (sign-up confirmation, password reset); and the content of feedback you submit (including any screenshots you attach) or a report you file (including the excerpt of what was reported), together with your account email | Delivers account emails to you, and delivers your feedback or report to our team by email |
We don't share your data with advertisers or data brokers, and we don't sell it to anyone.
You can review or revoke any of these at any time from Settings in the app (tap your profile picture at the top right), which links directly to your device's own settings.
We keep your data for as long as your account exists, so Miki can remember your trips. If you delete your account, everything you own is permanently deleted within 30 days — every trip you created, your itinerary, chat history, the ratings you've given Miki's replies, uploaded documents, trip cover photos, feedback you've sent (including attached screenshots), the messages you sent in private chats, your published trips, comments and wall posts, the people you've blocked and followed, your notification history, and your profile. This can't be undone. A copy of a feedback or report email we already received may remain in our inbox until we delete it. Photos and videos in a trip's Memories tab are kept on your phone only: removing one deletes its copy immediately, and they are not part of the 30-day server deletion because Miki's servers never hold them.
Chats in your main Miki chat history are deleted automatically after 90 days of inactivity; messages in a chat tied to a specific trip stay with that trip. A rating you give one of Miki's replies is kept with your account separately from the conversation — so it remains after the chat itself has been deleted — until you delete your account.
When something you own is deleted (a trip, a message, a profile), we keep a minimal log entry that says only what kind of item it was, its id, whose it was, whether you or the system deleted it, and when; it contains none of the item's content and is removed after 90 days. We keep it so we can show that a deletion happened. Records of how Miki's AI features were used (which feature and AI model, counts, speed and cost) are kept after your account is deleted, with your identity removed. The network address recorded at sign-up is deleted automatically within a few hours. Sign-in session records (including their network address) are removed when you sign out of that device, when the session expires, or when you delete your account.
Booking links. The results Miki found for a plan's activities (up to three sellers with their web addresses, ratings and prices shown) are kept while the plan exists and are deleted when you delete the plan, the activity or your account.
A report you file is deleted if you delete your account. A report about someone's content is kept until it is closed, and a closed report is deleted 12 months after it was filed; if the person it was about deletes their account, the report stays but their identity is removed from it.
Separately, once a trip's end date has passed, we automatically clear out the booking documents (confirmations, screenshots, photos) uploaded for that trip — this happens on its own, whether or not you ever delete your account, and keeps that document data from sitting around indefinitely once it's no longer needed. Your itinerary itself isn't affected and stays as a shareable recap of the trip.
A request for trip ideas stays until you switch it off, but followers only see it in "Planning now" for 30 days after you post it. It's also removed automatically when you turn that destination into a full trip, delete the trip, or delete your account.
If a trip you created was shared with other people, it is not deleted for them: ownership passes to the member who has been on it longest, and the itinerary stays as part of their plan, no longer linked to your identity. The booking documents you uploaded to it are deleted. A trip you created that has no other members is deleted. If you only contributed to someone else's shared trip, the itinerary items you added stay as part of that trip, no longer linked to your identity, and the documents you uploaded are deleted.
Private chats. The messages you sent in private chats are deleted, including the photos, files and locations in them. The other person keeps the messages they sent, and the conversation shows you as a deleted traveller; they can still read it but can no longer reply. When both people have deleted their accounts, the conversation is removed. A reminder you set for another traveller on a shared trip stays for them.
If a trip's owner removes you from a shared trip while it's already underway, we keep a read-only copy of that trip exactly as it looked at the moment you were removed, so you don't lose the plan you were relying on — this copy is kept for up to 1 year, then permanently deleted.
Usage statistics (the daily open record and the screen and feature counts) are kept for up to 400 days and are deleted if you delete your account. Anyone who reads them in our admin view sees only totals, and a group of fewer than 5 people is never shown on its own.
A pending invitation to join a shared trip — one that hasn't been accepted or declined — is kept for up to 30 days, then automatically removed.
An email address you add to the waitlist is kept for up to 90 days, or until you are invited and sign up, then it is deleted. The network address used to limit how often the waitlist can be joined is kept for about two hours.
If you're in a region with additional rights (such as the EU/UK under GDPR, or California under the CCPA), you may also have the right to request a copy of your data or ask us to correct it — contact us using the details below.
The controller of your personal data is Ajit Bhandary, who publishes Miki. You can reach us at privacy@getmiki.app for anything in this policy, including exercising any right described below. We aim to answer within one month.
Where the GDPR or UK GDPR applies to you, we need a legal basis to use your personal data. These are the ones we rely on:
| What we do | Legal basis |
|---|---|
| Run your account, keep your trips, itinerary and chat history in sync, generate Miki's replies, read documents you upload, and send account emails | To provide the service you asked for (contract) |
| Notifications, reminders, disruption and pre-trip checks, and trip invitations | To provide the service you asked for (contract); a push notification also needs the permission you give on your device |
| Searching the web for booking links when you ask (Find booking links) | To provide the feature you choose to use (contract) |
| Your location, to find places near you and the country you are in | Your consent, given through your device's location permission, and withdrawn by turning it off |
| Publishing a trip, following people, comments, mentions and private chats | To provide the features you choose to use (contract) |
| Travel persona suggestions and tailoring replies to you | Our legitimate interest in making Miki useful to you, balanced against your interests (you can set or change your persona yourself) |
| Measuring how well replies and notifications work, counting how many people use Miki and which features they use, finding and fixing crashes, limiting automated sign-ups, and keeping Miki safe (reports, moderation, blocking) | Our legitimate interests in running a reliable and safe service |
| Confirming you are old enough (at least 13, or at least 18 if you live in India), and acting on content that breaks the law or our Terms | Legal obligations, and our legitimate interest in protecting people |
| Reading and answering feedback you send us | Our legitimate interest in improving Miki |
Where we rely on legitimate interests you can object at any time (see "Your rights"). Where we rely on consent you can withdraw it at any time, and doing so doesn't affect what we did before. We don't use your personal data for automated decisions that have legal or similarly significant effects on you; the travel persona only personalizes what you see in the app.
Miki's backend (database, sign-in and file storage) is hosted by Supabase in Tokyo, Japan. Some of the providers listed under "Who we share it with" process data in other countries, mostly the United States (including Anthropic, Expo, Resend, LocationIQ, Google and Apple); Sentry stores crash data in the EU. So your personal data can leave your country, including the EEA and the UK. When it does, we rely on safeguards that the law accepts for such transfers. For most of our providers these are the European Commission's Standard Contractual Clauses (and the UK equivalent) in the provider's data processing terms, or the provider's participation in a recognised framework such as the EU–US Data Privacy Framework. Where a provider doesn't offer either, we limit what it receives: for example, a map lookup service gets place names and coordinates, never your name or account details. You can ask us which safeguard applies to a specific provider using the contact details below.
You can use these in the app where there is a control for it (see "Your controls") or by emailing us.
We will answer a request within one month. We may need to confirm it is really you before we act on it.
If you are in India (Digital Personal Data Protection Act, 2023): you can ask for a summary of the personal data we process and who we share it with, ask us to correct or erase it, and nominate another person to exercise these rights for you if you die or can't act for yourself. For any complaint about how we handle your data, our grievance contact is Ajit Bhandary, privacy@getmiki.app. We aim to respond to a complaint within 30 days. If you are not satisfied, you may complain to the Data Protection Board of India.
This is our notice at collection under the California Consumer Privacy Act (CCPA/CPRA). In the last 12 months we have collected these categories of personal information, for the purposes described in "How we use it", and keep them as described in "How long we keep it":
We do not sell your personal information and we do not share it for cross-context behavioural advertising, as those terms are defined in California law, and we don't knowingly sell or share the personal information of anyone under 16. We use precise location only to provide the service you asked for. You have the right to know what we collect, to have it deleted or corrected, and not to be treated differently for using these rights. Use the in-app controls or email us; an authorized agent may also make a request for you, and we may ask for proof of that authority.
Miki isn't directed at children. We don't knowingly collect data from anyone under 13, or from anyone under 18 who lives in India, where the law treats a person under 18 as a child and requires a parent's verified consent, which Miki does not collect. When you create an account (or the first time you open Miki after this was introduced), we ask you to confirm you are at least 13 (at least 18 if you live in India), and we keep only that you confirmed, which minimum, and when, not your date of birth; if you tell us you are under 13, we delete the account. If you believe a child has provided us data, contact us and we'll delete it.
If this policy changes in a material way, we'll update the effective date above and, where required, let you know in the app.
Questions about this policy or your data: privacy@getmiki.app