Privacy
Your photos and tracks stay where the work happens.
LensPin analyses photo and video metadata, GPX tracks, and optional workout routes on your device. It does not upload your photos, videos, GPX files, or workout data for matching. LensPin also collects usage statistics that you can turn off in Settings. Automatic time-zone display may send coordinates to Apple; both uses of network services are explained below.
Last updated
Photo library access
LensPin needs the Photos access you grant in order to find eligible camera photos and optional videos, read metadata, display previews, add approved locations, and collect successfully updated items in the LensPin album. Automatic location suggestions only process items without a current library location. Video scanning is off by default.
Immediately before saving, LensPin reads the Photos item again. If a location now exists, the app skips that item rather than overwriting it.
Photos and metadata
Photo inspection and matching happen on the device. LensPin may read camera make and model, lens information, capture time, exposure details, existing GPS metadata, Photos-library location, and original data needed to inspect metadata, display a preview, or create an optional JPG export.
LensPin does not upload the photo or its embedded metadata to a LensPin server for matching.
GPX files
A GPX file is opened and parsed locally for timestamped track points and segment boundaries. It is used only for the current matching workflow and is not retained when the workflow is restarted. LensPin does not upload the GPX file.
Optional workout routes (version 1.3.2 and later)
If you choose Workout Routes, LensPin requests read-only access through Apple HealthKit to workouts and their recorded routes. These may include outdoor workouts started on Apple Watch and viewable in Apple Fitness. LensPin uses workout dates, activity types, and timestamped route coordinates to let you select recordings and suggest missing locations for photos and optional videos taken at the same time. This is a photo-location feature, not a health or fitness assessment.
Workout records and routes are processed locally for the current workflow. LensPin does not write workout or health records, upload workout data to LensPin or analytics providers, or store raw workout datasets in iCloud or CloudKit. It does not use health or workout data for advertising or analytics. Matching and saving analytics are suppressed while a workflow uses Workout Routes. You can use iPhone photo references or GPX files instead, and manage Health access in iOS settings.
After you review and explicitly confirm a suggested location, LensPin can save that derived coordinate as the item's location in Apple Photos. If iCloud Photos is enabled, Apple may sync the saved Photos metadata under your settings. Automatic time-zone lookup may also send a small number of route-derived coordinates to Apple's geocoding service, as described below. Workout records and full routes are not sent to that service.
Automatic location time zone
When automatic time-zone display is enabled, iOS may send a small number of coordinates to Apple's geocoding service to identify the time zone for the suggested place. Photos, GPX files, workout records, and full routes are not sent. Coordinates used for this lookup can come from a photo reference, a GPX track, or a selected workout route. You can choose a manual UTC offset instead.
iCloud Photos
When an original is stored only in iCloud, LensPin can ask the Photos framework to download it so metadata inspection can continue. That transfer is handled by Apple's Photos and iCloud services under your iCloud settings.
Location writeback
Saving an approved location updates the location associated with the item in Apple Photos. Saving a library location does not rewrite original-file GPS metadata, create a replacement library item, or modify the original photo, RAW file, or video. A Photos-library location may not appear in every shared or exported file because file-level metadata depends on the Photos export path and settings.
Optional JPG export
If you choose Export JPG, LensPin creates separate JPG copies. When Include Location is enabled, the item’s current Photos-library coordinates are embedded in those copies. Non-JPG photos are converted; originals remain unchanged. Exporting does not upload the photos to LensPin. The receiving app or service handles any files you choose to share. Video GPS export is not supported.
Optional app usage statistics
The current version of LensPin collects app usage statistics and sends usage reports to PostHog by default when analytics is configured. You can turn sharing off at the bottom of Settings → Help Improve LensPin and continue using every feature. An existing choice to turn sharing off is preserved across updates.
Reports describe app launches, photo permission results, GPX import outcomes, scans, matching previews, location-saving outcomes, paywall views, purchases, and purchase restoration. They may include quantity ranges, rounded task and stage durations, predefined error categories, fixed page names, app versions and build numbers, iOS versions, the app language and device region setting, event timestamps, a random installation identifier, and random session, workflow, and operation identifiers. The device region is a system preference, not your physical location. Minimal task checkpoints let the next launch report an unfinished operation without identifying it as a confirmed crash. These identifiers let us understand repeated use and the steps within a task; they are not your name or an account login.
Usage reports do not contain your photos, thumbnails, filenames, photo-library item identifiers, photo capture dates, EXIF metadata, coordinates, GPX contents, health or workout data, or screen recordings. LensPin does not enable automatic screen or tap recording, advertising identifiers, advertising attribution, or cross-company advertising tracking. IP-based location enrichment is disabled, and the analytics project is configured to discard client IP addresses from stored events. Like any network service, PostHog receives connection information needed to handle requests; this does not make reports fully anonymous.
We use these reports to find unsuccessful workflows, improve reliability, and understand feature and purchase usage. PostHog processes the reports for us. See PostHog’s privacy policy for information about that service.
Reports may wait in a bounded queue on your device while offline. Turning sharing off stops new collection and clears that queue, task checkpoints, and the local analytics identifier. Reports already received by PostHog, or requests already in transit, cannot be recalled by this switch. Turning sharing on again starts with a new local analytics identifier.
This website
This is a static information website with no account system, upload form, photo processor, or GPX uploader. It does not access your Photos library or receive your media or GPX files.
Cloudflare serves and protects the website and processes connection information for those purposes. Cloudflare also inserts its Web Analytics beacon into delivered pages for page-visit and performance measurements; those measurements depend on whether the browser permits the script and its requests. See Cloudflare’s data collection documentation and privacy policy. App usage reports sent to PostHog are separate from website measurements and are described above.
Changes and questions
Material privacy changes will be reflected on this page with a new review date. For product questions, start with the LensPin support page or use the support contact shown on the App Store listing.