Privacy Policy

Who We Are & How To Contact Us

Data At A Glance

Network Services & Third Parties

• Apple Maps / CLGeocoder. Used for place lookup and reverse geocoding outside mainland China. Coordinates and standard network metadata such as IP address may be sent to Apple.
• AMap. Used for reverse geocoding in mainland China. Coordinates may be sent to AMap when place lookup runs.
• Apple Weather / WeatherKit. Receives coordinates to fetch current weather context for timeline events.
• Map tiles and map assets. Base map tiles, glyphs, sprites, and style assets may load from MapTiler or another MapLibre-compatible host. Those providers typically see your IP address and the map area requested.
• Apple Health / StoreKit / TestFlight / Apple crash systems. Apple handles HealthKit authorization, purchases, receipts, and certain crash or performance diagnostics under Apple's policies.
• Autheai purchase service. Receives a random app user ID, current StoreKit entitlement status, original transaction IDs, and last activity time at apple.autheai.com for purchase reconciliation and aggregate free and paid usage statistics.

What We Process And Why

Background location and timeline data

• Why: create continuous routes, detect stays and gaps, show your day on a timeline, and recover after app relaunches or device restarts.
• How: collected from Core Location with your permission. Background tracking requires "Always Allow" location.

Motion, visits, and Wi-Fi context

• Why: detect when you start or stop moving, wake or pause higher-power GPS more intelligently, and improve stay detection.
• How: processed locally using Motion & Fitness, visit events, and optional Wi-Fi SSID or BSSID checks. Wi-Fi context is used on device to infer whether you are stationary and is not routinely uploaded to our servers.

Apple Health

• Why: improve calorie estimates, activity summaries, and optional health profile calculations.
• How: HealthKit data is read only after you grant Apple Health permission. Path does not write data back to Apple Health.

Photos and videos

• Why: show location-tagged media on the map and let you browse or focus the items you allowed.
• How: Path scans the creation date and embedded location metadata of the photos or videos you permit through Photo Library access. If you choose Limited Library access, only those permitted items are visible to the app.

In-app purchases, notifications, and diagnostics

• Why: unlock paid features, alert you when tracking stops, and improve reliability.
• How: Apple processes purchases through StoreKit. Path sends a random app user ID, current entitlement status, original transaction IDs, and last activity time to apple.autheai.com to reconcile purchases and produce aggregate free and paid usage statistics. These pseudonymous records remain linked to the random app user ID. They do not include your name, email, location timeline, HealthKit data, or photo data. Notifications are local system notifications. Crash logs and performance reports may be provided by Apple or TestFlight if you choose to share diagnostics.

Where Your Data Lives

• On device by default. Timeline data, cached state, HealthKit-derived values, and Photo Library linkage are stored locally on your iPhone.
• No routine timeline upload. Path does not operate cloud timeline sync or routinely upload routes, stays, HealthKit data, or photo metadata. Limited purchase status data is sent as described above.
• Exports create separate copies. If you export a backup file or share data, that copy is stored where you choose and is no longer controlled by Path.

Sharing & Disclosures

We do not sell personal data. We share data only in these cases:

• Apple for StoreKit purchases, HealthKit permissions, Apple Maps or CLGeocoder results, and Apple-managed diagnostics.
• Autheai purchase service. Receives a random app user ID, current StoreKit entitlement status, original transaction IDs, and last activity time at apple.autheai.com for purchase reconciliation and aggregate free and paid usage statistics.
• AMap and map tile providers when those services are needed to resolve a place or map asset.
• Recipients you choose when you export or share a backup, map snapshot, or other content.
• Legal compliance when required by law or when necessary to protect rights, safety, or security.

Your Choices

• Change permissions anytime in iOS Settings for Location, Motion & Fitness, Photos, Health, and Notifications.
• Use in-app data management tools to export data, delete local timeline data, or remove the app to erase local storage.
• Disable map media if you do not want Path to scan permitted photos and videos for location-tagged items.
• Manage or cancel subscriptions from your App Store account settings.

Legal Bases For Processing (EEA/UK)

• Consent - for background location, motion activity, photos, HealthKit, and notifications.
• Performance of a contract - to provide the app features you request, including timeline history and optional paid access.
• Legitimate interests – app security, crash prevention, debugging, abuse prevention, and service reliability.
• Legal obligation – to comply with applicable laws.

Your Privacy Rights

EEA/UK residents

You may have the right to access, correct, delete, restrict or object to processing, and to data portability. You can withdraw consent at any time. You also have the right to lodge a complaint with your local supervisory authority.

California residents (CPRA)

You have the rights to know/access, delete, correct, limit certain uses of sensitive data, and to not be discriminated against for exercising your rights. Path does not "sell" or "share" personal information for cross-context behavioral advertising.

How to exercise rights: email us at [email protected]. We may request information to verify your request.

International Transfers

If we use service providers outside your country, we will rely on appropriate safeguards (e.g., Standard Contractual Clauses) to protect your information, consistent with applicable law.

Security

We use platform security controls, local storage protections, least-privilege access, and HTTPS or TLS for supported network requests. No method of storage or transmission is completely secure, and third-party provider requests are also governed by those providers' own security practices.

Changes To This Policy

We may update this Policy as features evolve. We will change the "Last updated" date and, when appropriate, provide additional notice in the app.

Contact

Questions or requests? Email [email protected]

App Store Connect privacy labels should be read together with this Policy. If our processing changes, we will update both the app disclosures and this document.