Privacy Policy

Effective Date: September 29, 2026

This Privacy Policy explains how Map My Parks ("Map My Parks," "we," "our," or "us") collects, uses, stores, and shares information when you use the Map My Parks mobile app, Map My Parks Pro features, and related services.

1. Information We Collect

We collect information you provide and information required to operate syncing and account security.

• Account data: email address used for shared-map sign-in.
• Authentication data: login challenge records, hashed one-time login codes, hashed session tokens, session expiry, request IP, and user agent for security and abuse prevention.
• Trip and map content: visited park checkoffs, trip dates, notes, and trip photo metadata.
• Trip media: trip photo files you upload for shared-map sync. Uploaded originals may include embedded location, date, and device metadata; other members who can access a shared photo may be able to inspect that metadata.
• Safety reports: the topic and description you submit through Shared Map settings, linked to your account and map so our support team can review and respond.
• Location data (optional): if you enable location features, the app accesses device location only to show your position on the map. We do not use that location data for other purposes.
• Subscription status: Pro entitlement state from Apple App Store / Google Play Billing.

2. How We Use Information

• Provide core app features, including visited parks and trip logging.
• Sync shared-map data across devices and between iOS and Android.
• Authenticate users and protect accounts from abuse.
• Determine Pro access status and restore purchases.
• Operate, troubleshoot, and secure our services.
• Review and respond to concerns about shared content or members. Other members do not receive your report.

3. Where Data Is Stored

• On-device: iOS stores app data in app sandbox storage (including trip photos) and stores shared-map auth tokens in Keychain. iOS trip photos are written with Apple file-protection controls. Android stores shared-map auth data in EncryptedSharedPreferences and stores trip data/photos in app-private storage with app backup disabled.
• Cloud sync (iOS Apple services): iOS trip/log sync uses iCloud key-value storage and iOS photo sync may use CloudKit private database when shared-map sync is not enabled.
• Cloud sync (Map My Parks shared map): shared-map metadata is stored in Cloudflare D1 and shared trip photos are stored in Cloudflare R2 object storage.

4. Security and Encryption

• Data in transit uses HTTPS/TLS between app clients and our API endpoints.
• Shared-map auth sessions and one-time login codes are stored server-side as SHA-256 hashes (not plaintext values).
• iOS stores shared-map session data in Keychain; Android stores shared-map session data in EncryptedSharedPreferences (AES-based encryption via AndroidX Security Crypto).
• Cloudflare-managed infrastructure (D1/R2) is used for backend data storage, with provider-managed encryption controls.
• Shared-map trip photo uploads are validated server-side for supported image types and file size limits.
• Android app network security disallows cleartext HTTP traffic in production builds.
• Current architecture does not implement end-to-end encryption with user-managed keys for shared-map notes/photos.

5. How We Share Information

We do not sell personal information. We share data only as needed to operate the service:

• Cloudflare (API, database, storage, and edge infrastructure).
• Apple (iCloud/CloudKit, App Store billing and purchase restore on Apple platforms).
• Google (Google Play Billing on Android).
• Resend (email delivery for shared-map login codes and support report notifications).
• Other users in your shared map can see shared-map trip content that you sync into that map.
• Creating a shared map adds this device's existing visited parks, trip logs, and photos to it. Members you invite later can see that content.
• When you join a map, you choose whether to merge this device's existing visited parks, trips, and photos into the shared map or use only the shared map's data on this device. Merging makes that existing content available to other map members.

6. Data Retention

• On-device data remains until you delete it or uninstall the app.
• Shared-map contributions remain while the map exists if you choose to leave them when you leave. If you later delete your account, your attributable cloud contributions are removed. Another member's independent contributions remain.
• When the last member leaves or deletes their account, the shared map and its cloud photo objects are deleted through a retryable cleanup process.
• Some deleted shared-map photo records may be retained in a soft-deleted state for up to 30 days before scheduled permanent cleanup.
• Safety reports are removed from our service database when the reporter deletes their account or 90 days after a report is closed. Open reports remain until reviewed. Report notifications, including your email address and report details, go to [email protected] through our email provider. Support mailbox copies may have a separate retention period.
• Expired login codes and invites, revoked sessions, and revoked push registrations are normally removed from our service database after 30 days. Active sessions and map content are not deleted because an account has been inactive.

7. Your Choices

• You can disable location access through app settings and OS permission controls.
• You can remove trips and photos in the app.
• You can leave a shared map and choose to keep your contributions there for now or remove them when leaving. Another member manages the map after you leave.
• The map administrator can revoke unused invitations or remove a member's access. Removing access does not delete that person's account or their attributable contributions. The removed person can request deletion of their account and contributions.
• In Shared Map settings, you can block another member. If you manage the map, blocking removes that member's access. Otherwise, blocking leaves the map and lets you choose whether to keep or remove your contributions. Blocking does not delete either account. You can unblock someone in Shared Map settings, but that does not restore map access automatically.
• While in a shared map, you can submit a private safety concern through Settings > Shared Map > Report a Concern.
• Choosing "Use Shared Map Only" when joining replaces this device's map data after the shared map loads. Copies in iCloud, other devices, exports, or backups may remain.
• You can delete your Shared Map account and its attributable cloud contributions, including those left in earlier shared maps. Your on-device copies remain until you remove them.
• You can cancel Pro subscriptions through Apple or Google subscription management.

8. Children’s Privacy

Map My Parks is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

9. Policy Changes

We may update this Privacy Policy from time to time. We will post the updated version on this page with a new effective date.

Contact: [email protected]