Prepared against the app as of October 11, 2026. Effective date: the date the app is first made public
Operator: HyoSeop SHIM
Privacy contact: HyoSeop SHIM, hoihoi.support@gmail.com
Re:Mapping creates travel records from the capture times and locations of your photos.
| Information accessed or stored on the device | Purpose |
|---|---|
| Photos, photo-library asset identifiers, and filenames | Finding photos by date, checking duplicates, and linking photos |
| Capture times, latitude and longitude, and altitude when available | Ordering photos and estimating routes, distances, and transport modes |
| Photo previews | Displaying trip lists, maps, and photo screens |
| Trip names and dates, day names, transport edits, and custom place names with their area (city and district) | Saving and editing your trips |
| Saved places (name, coordinates, area, use count and time) and corrected photo locations (the corrected and original coordinates) | Picking the same place name again later, and correcting where photos appear on the map |
| Language, theme, distance units, and route colors | Maintaining your preferences |
| Map data and place-lookup caches | Reducing repeated requests and data usage |
| Error times, messages, and stack traces | Keeping diagnostic logs on the device |
The list of saved places and the records of corrected photo locations are stored only on your device and are not sent to the developer's servers. However, when you correct a photo's location, viewing the map or looking up place names at that location can send the corrected coordinates, or the map area around them, to the services in Section 2. Correcting a photo's location does not change the original photo or its EXIF in your photo library; only the location shown in the app changes.
For some photos, the app reads EXIF data from the original file to find location information. Filenames are used to check duplicates and are not stored in a separate photo-point database field. Error logs may contain file paths included in an error, but are not automatically sent to the developer. The app does not continuously track your device's current location.
| Service | When and why it is requested | Information sent |
|---|---|---|
OpenFreeMap (tiles.openfreemap.org) | When displaying or moving a map, to retrieve the light map style, tiles, and fonts (the dark map style is built into the app and is not requested) | Request URLs identifying map areas and connection information needed for communication |
| Operating-system geocoder | On screens requiring automatic place names | Photo coordinates, the app language, and service connection information |
Overpass (overpass-api.de) | When opening the place-name editor, to find nearby facilities | A representative photo's coordinates, search conditions, and connection information needed for communication |
Requested map areas may relate to the locations of your travel photos, and for a photo whose location you corrected, they are based on the corrected location. External servers may process connection information such as your IP address. These requests do not include photo files, capture times, travel names, or complete travel records.
iOS uses Apple's system geocoder. The system geocoding provider on Android can vary by device. System geocoding may use the network, and external requests may be processed in countries other than your own. The developer cannot directly delete information held by external services or control their retention periods.
For the map provider's practices, see the OpenFreeMap Privacy Policy and Terms of Service. Map and facility data are attributed to OpenFreeMap, OpenMapTiles, and OpenStreetMap. Tapping a source link on the map credits screen opens that site in your device's browser. The app does not pass your photos or trip information when it does, and further traffic is between the browser and that site.
Photo access is requested to find photos for travel records and display previews. On iOS, granting access to selected photos restricts searches to those photos. You can change or revoke access in your device settings. Revoking access alone does not delete trips or previews already stored in the app.
Current imports use photos whose originals are available locally. The app does not offer downloading iCloud-only photos for import.
| Information or feature | Retention and deletion |
|---|---|
| Trips | Kept until you delete a trip or local app data is removed. Deleting a trip also deletes its linked photo points, segments, custom place names, day names, and previews |
| Photo, place, and map caches | Removed through Clear Cache in settings. Original photos, trips, custom place names, saved places, and corrected locations are kept |
| Saved places | Kept even after you delete a trip. Delete them one by one or all at once under Saved places in settings (place names and corrected locations already on photos are kept) |
| Corrected photo locations | Removed when you restore the original location in photo details. Deleted along with the trip |
| Place-lookup disk caches | Currently expire after 30 days, with up to 1,000 entries per cache type |
| Map cache | Currently managed toward a 500 MB limit. Actual disk usage may vary with the SDK and device environment |
| Diagnostic logs | Up to 50 recent entries are kept and can be deleted in settings |
Deleting trips or caches in Re:Mapping does not delete originals from your photo library. Operating-system backups and log copies you send elsewhere may remain separately. Offloading an app may differ from deleting its data; the results of app removal and data deletion depend on the operating system.
You can view, edit, and delete trips, place names, and saved places in the app, and restrict photo access through device settings. The developer cannot remotely access your device's trips or delete them on your behalf.
The app uses local app storage and HTTPS addresses for the external services specified above. It does not provide separate database encryption. Please use your device lock and operating-system security features.
For privacy inquiries, contact hoihoi.support@gmail.com. Contact details and inquiry contents are used only to answer and handle your inquiry, and are deleted within one year after the inquiry is resolved. If the law requires us to keep them longer, we keep them separately only for that period.
When data practices change, this policy and its effective date will be updated, with notice through the public policy page and in-app information. New features such as advertising, analytics, or synchronization must first be reviewed against their actual data practices.