Parkgoer
Privacy Policy
Effective October 19, 2026 · Developer: Aidan Pink
Parkgoer keeps your visit journal and automatic location detections on your device. Network features send the information needed to answer a search, deliver an alert, or validate a purchase. We do not sell personal information or use it for cross-app advertising.
1. Information on your device
The app stores preferences, favorite attraction identifiers, wait-alert definitions, and your park visit and ride journal locally. Journal entries can include parks, rides, dates, times, and waits you enter. You can export your local journal, favorites, and alerts in Settings. An exported file is under your control.
Automatic visit and ride detection requires your permission for Always and Precise Location. Location observations are processed on your device. The app keeps limited detection progress, public attraction geometry, timestamps, and counters; it does not save a trail of your location observations or upload your location or visit journal to our service. Detected visits and rides become editable local journal entries. Detection can be incomplete or incorrect.
Optional local beta diagnostics count supported app actions by day. They exclude search text, location, park and attraction identifiers, account details, and your visit journal. Local collection and sharing are separate choices and both default off. Previously enabling local counts does not enable sharing.
2. Information used by network features
| Feature | Information and purpose |
|---|---|
| Park data & Search | Our data service receives requests for parks, rides, waits, and schedules. Search sends the question you submit, the selected park identifier when applicable, and favorite attraction identifiers used to scope an answer. Do not include sensitive personal information in a question. Available on-device language-model features process their prompts locally; submitted park-data questions still go to our data service. |
| Background alerts | If you enable wait alerts and notifications, our delivery service receives an anonymous installation identifier, an authentication credential, your Apple push-notification token, and alert settings such as attraction identifiers and wait thresholds. This allows the service and Apple Push Notification service to deliver your requested alerts. Notification delivery does not require uploading your location or visit journal. |
| Optional beta usage sharing | If you separately enable sharing in Settings, the app sends daily counts of supported actions, such as page views, searches by category, alert changes, and purchase outcomes, to our server. Reports exclude search text, location, park and ride identifiers, personal trip history, account data, and a persistent installation identifier. Each day uses separate random report credentials so the app can update or delete its report. Counts do not establish unique visitors, cross-day retention, actual notification delivery, or a valid purchase entitlement. |
| Purchases | Apple processes payments. Our service assigns a private billing identifier to your app installation and stores its association with the installation identifier and a hash of its authentication credential. The app uses that billing identifier with RevenueCat to validate purchases and manage Pro access using product and transaction information and entitlement status. This setup does not require an app account, notification permission, your location, or your visit journal. Purchase information is also used for subscription reporting and fraud prevention. We do not receive your payment-card details. |
| Connections & support | Network and hosting providers necessarily process connection information such as IP addresses and request metadata to deliver and secure the service. If you contact us or choose to send an export or diagnostic report, we receive the information you provide. |
We use service providers for hosting, purchase management, and notification delivery. Their processing may take place outside your country. Read Apple’s privacy policy and RevenueCat’s privacy policy. This website is hosted by Vercel; visiting it involves ordinary connection metadata such as IP addresses and request metadata. See Vercel’s privacy policy. These pages do not add advertising, analytics scripts, or a contact form.
3. Your choices
- Manage or revoke Location and Notifications permissions in iOS Settings. Turn off Track park visits or Detect rides in the app’s Settings to stop those detections. Pending ride evidence is cleared when ride detection is disabled.
- Edit or delete detected journal entries. Use Export data or Delete local data in the app’s Settings to manage local records. Deleting local data also disables automatic tracking.
- Remove or disable wait alerts in the app to stop those alert definitions from being delivered. Changes must reach the server over a network connection; disabling notifications in iOS also stops their display on that device.
- Use the Beta diagnostics controls to collect counts locally, share them separately, export, or reset them. Enabling sharing starts new counters and does not upload earlier local counts. Turning sharing off or resetting diagnostics requests deletion of previously shared reports. If you are offline, deletion remains queued until the app can reconnect.
- Manage auto-renewal with your Apple Account. Deleting local data or uninstalling the app does not cancel a subscription.
4. Retention and deletion
Local journal entries and preferences remain until you edit or erase them or remove the app’s local storage. Device backups and exported copies may retain data separately under your control. Local and shared beta usage counts are retained for up to 30 days. A successful deletion removes the active shared report. Short-lived deletion markers retain a report identifier and hashed credential for up to 30 days to prevent a delayed upload from restoring it. Uninstalling the app before a queued deletion reaches the server can prevent that request from completing; automatic retention still applies.
Server-side alert settings are replaced when changes successfully synchronize. Removing an alert removes its active server definition and associated pending delivery; anonymous installation or delivery records may remain. Service, security, support, and purchase records are kept as needed to operate the service, resolve delivery or purchase issues, and meet applicable obligations. Purchase records held by Apple or RevenueCat are separate from the local journal and are not erased by Delete local data.
The installation’s private billing association is kept separately from alert settings so turning off notifications or removing an alert does not replace its purchase identity. Delete local data does not erase this association or Apple and RevenueCat purchase records. Reinstalling the app or changing devices does not itself guarantee purchase restoration; use Restore in Membership to check purchases Apple can verify.
You can manage local information through the controls described above. For service-side access, correction, or deletion requests, contact support@parkgoer.app. Do not post personal information, passwords, authentication secrets, or push-notification tokens publicly.
5. Children and advertising
Parkgoer is not directed to children under 13. We do not knowingly collect personal information from children under 13. For privacy questions or concerns, contact support@parkgoer.app. The app does not use an advertising identifier, run targeted advertising, or sell or share personal information for cross-app advertising.
6. Contact and changes
Parkgoer is developed by Aidan Pink. For support or privacy requests, email support@parkgoer.app.
We will update the effective date when this policy changes. Material changes will be communicated through the app or an updated notice as appropriate.