privacy
Ranglr is for small groups coordinating a festival trip. The goal is to collect only what helps the crew, keep location sharing opt-in, and delete sensitive location data quickly. Ranglr does not track users for ads.
Data we collect
- Trip details, invite codes, display names, optional avatars, crew notes, packing checks, gear claims, lineup picks, needs, and activity updates.
- Mobile device records include a device id, platform, app version, last-seen time, hashed device token, and push token if notifications are enabled.
- Location records include coordinates, optional accuracy, optional note, update time, and expiry time only when a person chooses to share or responds to a ping.
- The iPhone app sends crash details, app version, build number, and platform to Sentry when crash reporting is configured. Crash data is used to keep the app reliable and is not linked to your Ranglr profile.
Data we do not collect
- No contacts, photo library, browsing history, advertising identifiers, or sale of personal data.
- No invisible continuous tracking. Location is not collected unless the user starts a share window or answers a ping.
- No location trail is kept by default; the app stores the latest active share, then deletes it after expiry.
- Crash reporting does not send screenshots, view hierarchy, session replay, performance traces, network breadcrumbs, SDK logs, or SDK metrics.
Retention
- Your location pin is stored only while you're sharing. Within 1 hour after a share window ends, your pin is permanently deleted.
- Pings are deleted after 7 days. We never store a trail.
- Location view audit entries are deleted after 30 days.
- Inactive device records may be cleaned up after 60 days. Activity events are kept by default so the crew can understand what changed.
User controls
- A host cannot turn on location sharing for someone else.
- Stop sharing expires the active share immediately.
- You can see recent location-view audit entries, delete your location history, revoke a device, or delete your profile from the current trip in the iPhone app.
- Deleting your trip profile is separate from Sign Out. It removes your current-trip profile, location and private data, poll and expense participation, revokes all of your devices for that trip, and anonymizes shared activity that the trip keeps. It does not delete another trip. A host uses the in-app transfer control to choose another current-trip member first.
Subprocessors
- Hosted Ranglr uses Vercel for hosting, Neon for the database, Apple APNs for push delivery, Sentry for iPhone crash reporting, and Stripe for hosted-plan billing when enabled.
- Self-hosted crews control their own database, domain, maps keys, push keys, logs, and retention jobs.
- Sentry is configured for crash-only diagnostics with default PII disabled. No analytics SDKs or third-party ad tracking are part of the current app.