Overview
Tagback helps restore missing location metadata on imported digital camera photos. The core design principle is local-first processing: the main scan, comparison, review, and decision flow runs on your device.
Data Tagback can access
If you grant permission, Tagback can access the following information for its repair workflow:
- Photos in your Photos library
- Photo capture timestamps
- Whether a photo already contains GPS metadata
- Existing location metadata in photos
- Thumbnails or preview images needed for repair review
- Location metadata written back to Photos when you explicitly approve a repair
- App Store purchase entitlement information needed to unlock or restore Tagback Pro
How Tagback uses this data
Tagback uses this information to find photos missing GPS metadata, compare them against nearby iPhone reference photos from the same time window, classify results for automatic approval or review, and write approved location repairs back into Photos only after you confirm the save step.
Tagback also checks and restores App Store entitlement state for Tagback Pro monthly and annual subscriptions and lifetime purchases.
Uploads and server processing
Tagback does not upload your photos or photo library to developer-owned servers. The main metadata repair workflow does not require account creation, sign-in, or a Kinno Labs cloud sync account.
Even while using Firebase Analytics and RevenueCat, Tagback does not send photos, thumbnails, filenames, Photos asset identifiers, GPS coordinates, place names, capture timestamps, EXIF data, or individual location suggestions to those services.
Payment information
Tagback Pro monthly and annual subscriptions and lifetime purchases are processed through Apple's In-App Purchase system. Subscriptions can be managed or canceled from the App Store subscription settings for your Apple Account. Payment method details are handled by Apple, and Kinno Labs does not receive your payment card information.
Tagback uses RevenueCat to reconcile subscription and entitlement state. RevenueCat may process product identifiers, App Store transaction and subscription lifecycle information, an anonymous RevenueCat app user identifier, and limited app and device information. StoreKit 2 remains responsible for purchase completion and native Tagback Pro access. RevenueCat purchase sync runs only when you explicitly choose Restore Purchases, and automatic device identifier collection is disabled.
Analytics, tracking, and advertising
Tagback does not include an advertising SDK, collect IDFA, track you across apps or websites, or request App Tracking Transparency permission.
Firebase Analytics may process automatic first-open measurement and allowlisted events for onboarding steps, coarse Photos permission outcomes, first scan completion, scan result classes and count buckets, review and save intent, paywall and plan selection, purchase start, non-monetary entitlement activation, and writeback outcome classes. The SDK may also process an anonymous app-instance identifier and ordinary app or device metadata such as app version, operating system, device class, and approximate region. For purchase and subscription-lifecycle measurement, Tagback may pass this anonymous Firebase app-instance identifier to RevenueCat so RevenueCat purchase events can be connected with GA4 analytics. This handoff does not include an email address, custom user ID, or photo-derived information.
Tagback does not set a custom Firebase user ID, send revenue-valued custom events, or send sensitive photo-derived details. Ad-personalization signals are disabled.
Apple services and third-party processing
Tagback uses Apple-provided PhotoKit, MapKit, and StoreKit frameworks. These services may involve network communication as part of Apple's platform behavior, and Apple's policies may apply. Google acts as the Firebase Analytics processor and RevenueCat acts as the subscription and entitlement processor; each provider's privacy and retention policies may apply.
Your control over photo changes
Tagback is designed so that no change is applied to your Photos library until you explicitly confirm the save step. Buying Tagback Pro alone does not automatically modify any photo.
Data retention
Tagback's core processing, onboarding progress, and analytics deduplication markers are stored on device. Kinno Labs does not keep a server-side copy of your photo library. Allowlisted analytics and purchase-entitlement data may be retained according to Firebase and RevenueCat service settings and policies. Apple purchase records, Photos system records, or operating system logs may also be handled under Apple's policies and your device environment.
Children's privacy
Tagback is a general-purpose utility app. It does not operate a dedicated child-directed account or direct personal data collection flow.
Contact
If you have privacy-related questions, contact Kinno Labs at kinnolabs0216@gmail.com.