Apps for iPhone
MiPie — effective September 4, 2026
MiPie does not collect any information. Every record stays on your device and is never transmitted to the developer. There is no server, no account, and no analytics.
The app does communicate with Apple’s map services to draw the map and to give your records a neighborhood name. Section 5 explains exactly what is sent.
The sections below explain this in detail.
To place your Wi-Fi connections on a map, MiPie processes the following:
| Information | When | Stored |
|---|---|---|
| Precise location coordinates (latitude, longitude) | Once, at the moment a record is created | Yes |
| Wi-Fi network name (SSID) | At the same moment | Yes |
| Wi-Fi security type | At the same moment | Yes |
| Wi-Fi access point identifier (BSSID) | At the same moment | Yes |
| Time of the record | At the same moment | Yes |
| Administrative region (country, city, neighborhood) | Just after the record is saved | Yes |
| Name you give a record | When you type it | Yes |
| Your current position (the blue dot on the map) | Continuously, while the map is on screen | No — used only to draw the dot, then discarded |
| Travel speed | At the moment of the decision | No — used only to decide whether you are in motion, then discarded |
| Location accuracy | At the moment of the decision | No — used only to decide whether the fix is precise enough to record, then discarded |
| Recent activity history (walking, automotive, etc. — last 3 minutes) | At the moment of the decision | No — used only to decide whether you were recently in a vehicle, then discarded |
The security type is stored so that open networks — those needing no password or login — can be excluded from your records. Networks you join automatically on the street or on public transit would otherwise pile up and make the records meaningless. Security type describes the kind of network (open / password / login) and is not the password itself.
The BSSID is stored so that moving access points can be filtered out. Wi-Fi on a bus or train reappears with the same name and the same access point several kilometers away. If the same access point is seen more than 500 m from where it was recorded, the app treats it as something other than a fixed place and deletes that record automatically. This value is never shown on screen.
The administrative region is stored to label records with a neighborhood name and to award regional badges. It is derived from the coordinates; section 5 explains how.
The app does not receive your location in the background. While the map is on screen, it receives your location continuously to draw the blue dot that shows where you are. That value is not stored. The only coordinates kept as a record are the ones taken at the moment a record is created, and location updates stop as soon as the app leaves the screen.
Activity history is likewise not monitored continuously. At the moment the app decides whether to record, it reads the last three minutes that your device has already accumulated, once, and then discards it.
One purpose only: showing your records on a map. The information is not used for anything else.
Records are stored solely in your device’s local storage (Apple SwiftData).
None. MiPie contains no third-party SDKs of any kind, including analytics tools, advertising networks, and crash reporters. Your information is never sold or shared.
The app communicates with Apple’s map services for two reasons. Both are governed by Apple’s privacy policy.
1) Map tiles — downloaded to draw the map on screen.
2) Turning coordinates into a neighborhood name — to label a record as, say, San Francisco, CA and to award regional badges, the record’s coordinates are sent to Apple’s reverse-geocoding service. This happens once just after a record is saved, and again when the app retries records that have not yet been labeled. The result (country, city, neighborhood) is stored on your device, and once stored the app never asks again for that record.
Network names are never included in this request. Only coordinates are sent.
The app never sends your records to the developer.
MiPie requests “While Using the App” location access with Precise Location. It never requests “Always” access.
Precise Location is required for two reasons:
MiPie requests Motion & Fitness permission so that rides on a bus or subway do not turn into records.
Speed alone cannot catch a bus stopped at a light, because at that moment the speed is near zero. So, at the moment it decides whether to record, the app reads the last three minutes of activity history your device has already accumulated (walking, running, cycling, automotive) once, to see whether you were recently in a vehicle. What it reads is used for that decision only and is never stored.
If you deny this permission, no records are created, because there is no way to tell whether you are in a vehicle. The button at the bottom of the map says so and becomes a shortcut to Settings. The app never monitors your activity continuously.
MiPie never asks for, reads, or stores Wi-Fi passwords. The app does not connect you to any network. It reads only the name, security type, and access point identifier (BSSID) of the network you are already connected to.
Wi-Fi names combined with locations accumulate into a history of where you were and when.
These records never reach the developer (see section 5 for the coordinates sent to obtain a neighborhood name), but anyone who can unlock your device can see them. We recommend setting a device passcode along with Face ID or Touch ID.
MiPie is not directed at children and does not knowingly process children’s personal information.
Changes will be communicated through app updates and this document. In particular, if a change ever causes data to leave your device — synchronization, backup, analytics, or anything similar — we will give notice in advance and update the App Store privacy disclosure accordingly.
junchoia25@gmail.com
This document describes how the app actually behaves. It is not legal advice.