Locter Privacy Policy
Last updated: October 13, 2025
This Privacy Policy explains how Locter (the "App"), developed by the project owner, collects, uses, stores, and
shares information from users. Locter is designed to keep your location data on your device and give you full
control over exports and backups.
1. Data we collect
- Location data: Locter collects your device's location (GPS coordinates, timestamp, accuracy,
altitude, speed, course) to detect where you have been and to generate visits and tracks. Location data is
collected when you grant location permissions (When In Use or Always). The App uses background location features
to track visits and locations when permitted. See the App's Info.plist keys:
NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription.
- Visit metadata: The App records detected visits (arrival/departure timestamps, coordinates,
horizontal accuracy) and may perform reverse geocoding to obtain a human-readable place name or address for
notifications and display.
- Local device files: Locter stores all collected location and visit data in a local database
located in the App Group container (
group.me.linjun.Locter). The database filename used by the app is
db.locterdb.
- Photos (optional): If you grant Photo Library access, the App can match locations to your
photos to aid organization. Photo access is only used for local matching and not uploaded to external servers.
- iCloud backups (optional): If you enable iCloud/Backups on your device, Locter can create
backups of your local database in your iCloud ubiquity container (
iCloud.me.linjun.Locter.backup).
Backups are stored in your iCloud account and are managed by iCloud; Locter does not transmit data to any external
server besides your iCloud account.
- GPX exports: You can export selected track data as GPX files. Exported GPX files are generated
locally and saved/shared according to iOS share sheet behavior. The App does not automatically upload GPX files to
developer-run servers.
2. How we use the data
- Provide core functionality: Location and visit data are used to detect places you've been,
display them in the app, and create timelines and maps.
- Notifications: The App may reverse-geocode visit locations to prepare user notifications about
places you visit.
- Exports & backups: When you choose to export or back up your data (manual or automatic iCloud
backups), the App creates files (GPX or database backups) and either hands them to the iOS share sheet or writes
them to your iCloud container.
3. Data sharing and third parties
- No developer servers: Locter does not send your location, visit, photo data, or backups to any
developer-controlled servers. There is no analytics or remote telemetry that collects personal data by default.
- iCloud: Backups written to iCloud are stored under your iCloud account and are subject to
Apple's iCloud Terms and privacy. Locter only writes the database files to the iCloud ubiquity container when
iCloud is available and enabled on your device.
- System frameworks: Locter uses Apple frameworks (CoreLocation, CoreLocation Visit monitoring,
CLGeocoder) which may communicate with system services as part of their operation. For example, reverse geocoding
requests go through Apple's geocoding services. This is part of standard iOS functionality.
4. Data retention and deletion
- Local retention: All location and visit data is stored locally in the app's database
(
db.locterdb) inside the App Group container. Data remains on the device until you delete it from
within the App or uninstall the App.
- Delete data: You can remove individual visits or locations from within the App's UI. To fully
delete all stored data, use the App's provided delete/clear data option (if available) or uninstall the App and
delete any iCloud backup files created by Locter.
- iCloud backups: Backups in iCloud remain until you delete them via the App's UI (if the App
exposes deletion) or via iCloud Drive management in iOS Settings / Files.
5. Your choices and controls
- Location permissions: You control location access in iOS Settings > Privacy & Security
> Location Services > Locter. You may choose "Never", "Ask Next Time", "While Using the App", or "Always".
The App recommends "Always" for the most accurate background tracking but will still work with limited
functionality if set to "While Using the App".
- Photo Library permissions: You can revoke Photo access in Settings > Privacy & Security
> Photos > Locter.
- Backups and exports: Automatic iCloud backups are optional and occur only if iCloud is enabled
on your device. You can disable iCloud Drive or delete backup files from iCloud using iOS Files or Settings.
- Exporting data: Use the App's export (GPX) feature to create shareable track files. The App
will present the standard iOS share sheet so you decide where to send or save exported files.
6. Security
On-device storage: Collected data is kept on your device and in your iCloud account if you opt
into backups. When stored locally, the database file is stored in the App Group container. The App does not
implement server-side storage or remote endpoints.
Transmission: When you share or export data using the iOS share sheet or write backups to iCloud,
the transmission security is handled by Apple's platform and the receiving service you choose (for example, AirDrop,
Files, or third-party apps).
7. Children
App Store age rating: 4+. The App is appropriate for users aged 4 and older according to App Store
guidelines.
We do not knowingly target or collect personal information from children under 13.
8. Changes to this Privacy Policy
We may update this policy to reflect changes to the App. When we do, the "Last updated" date at the top will be
changed. Significant changes will be posted in the repository's README or release notes.
9. Contact
For questions about this privacy policy, please contact the app owner at locter+support@omitlens.com.
Appendix — Technical notes (for app reviewers and technical users)
- Location APIs used: CoreLocation (
startUpdatingLocation,
startMonitoringVisits, startMonitoringSignificantLocationChanges, region monitoring).
The App requests both WhenInUse and Always location authorizations.
- Storage: GRDB-backed SQLite database stored as
db.locterdb inside the App Group
container group.me.linjun.Locter.
- iCloud backup container:
iCloud.me.linjun.Locter.backup. Automatic backups name
files under auto-backup and may rotate up to a configured number of backups.
- Photo usage: Photo access is used to auto-match photos to recorded locations locally; no photo
data is uploaded elsewhere by the App.