Map It for iPhone
Map It Privacy Policy
Updated September 25, 2026
Who operates Map It
Map It is provided by Codecentrate, Inc. This policy explains the iPhone app’s handling of recording data and the information you choose to send when requesting support.
Recordings on your iPhone
Map It stores your route positions, dates and times, GPS accuracy and speed samples, recording intervals, distance, available steps, motion classifications, splits, and optional titles on your iPhone. Motion information helps distinguish movement from GPS drift. Recording and local saving work without a Map It account or internet connection.
Optional private iCloud sync
Sync is off until you enable it. When enabled, saved recording data is sent to your private CloudKit database under your Apple Account. Apple operates iCloud, and this data uses your iCloud storage. Codecentrate does not receive a copy on its own servers or have access to other users’ private recording databases. Sync runs while Map It is open and pauses during recording. Device settings and unfinished recordings are not synced.
Maps and Apple services
Map backgrounds and shared map images use Apple Maps. Apple processes requests needed to provide map imagery under its own privacy terms. iOS manages location and motion permissions, speech voices, system backups, and any diagnostic sharing you enable with Apple. Map imagery may require a connection even when route recording works offline.
Exports and sharing
A Map It archive contains your saved recording history, including precise raw and filtered positions and other recording details. It is written only to the destination you choose in Files. A GPX export or map image contains the shared route you select; GPS timestamps are optional for GPX. Endpoint hiding removes positions near both endpoints from the shared copy, including returns to those areas. Shared copies omit your recording title and original trip totals. Visible locations can still identify places you visited. Recipients and file services control copies after you share them.
Deletion and retention
Recordings remain until you delete them. For previously synced recordings, deletion propagates to the associated iCloud account when sync resumes and removes the recording’s referenced route assets. A deletion marker retains an identifier, an opaque route fingerprint, and change revisions to prevent an offline device from restoring it; it contains no title or coordinates. An interrupted upload can leave unreferenced temporary cloud data. Disabling sync, signing out, or uninstalling the app does not automatically erase existing iCloud copies. Exported files and device backups are separate copies. You can manage Map It’s iCloud storage through Apple’s iCloud settings. Explicitly importing an earlier archive can restore a deleted recording.
Your controls
Manage location, Precise Location and motion access in iPhone Settings. You can record without step access, choose optional metrics, turn sync on or off, export your history, edit titles and delete recordings. Sync is not an independent backup: keep a separate archive for recovery. We cannot recover local-only recordings after they and their backups are lost.
Advertising, analytics and support
Map It includes no advertising, cross-app tracking, third-party analytics SDKs or developer-operated location-history service. We do not sell recording data. If you contact support, we receive the address, message and attachments you choose to send and use them to respond and maintain support records as needed. Please avoid sending precise route files unless they are necessary for your request. Contact support to request deletion of correspondence, subject to applicable retention obligations.
Policy updates and contact
We update this policy when the app’s handling of data changes. The date above identifies this version. Use Help & support in Settings or the support page on codecentrate.dev to contact Codecentrate about the app or this policy.
Contact support
Include your iPhone model, iOS version, Map It version and what happened. Please do not send passwords or precise route files unless they are needed to explain the issue.