1. What this policy covers
This policy covers the OUT! iPhone and Apple Watch apps, the OUT! website, the waitlist, and related services. “OUT!,” “we,” and “our” refer to the operator of OUT!.
2. Information kept on your device
OUT! stores commitments, preparation estimates, departure and arrival history, companion choices, free-plan counters, and app settings on your device. This information supports timelines, reminders, history, and learned preparation estimates.
Removing a plan removes the related plan record. Removing OUT! from your device removes its local app data, subject to Apple backup behavior.
3. Calendar, location, motion, alarms, and notifications
- Calendar: With permission, OUT! reads calendar events to build departure plans. Calendar contents are not uploaded merely to create a plan.
- Location: Precise location is used while needed for route estimates, current-origin refresh, optional Strict Mode verification, and optional Meet ETA calculation. OUT! does not maintain a continuous location diary.
- Motion: Optional motion signals help Strict Mode check whether movement started. OUT! does not use motion data for advertising.
- Alarms and notifications: Operational departure alerts are scheduled through Apple system services. You control permission through iOS Settings.
Routing and place searches use Apple MapKit. Apple processes requests under its own privacy terms.
4. Optional Meet Mode
Meet Mode uses Supabase with anonymous authentication. Remote Meet records include the Meet title, destination text, target arrival time, participant display name, coarse departure status, optional ETA, and an anonymous user identifier. Exact participant coordinates are not stored in Meet tables.
Meet sessions expire no earlier than 12 hours after creation and at least 6 hours after the target arrival time. Expired Meets stop accepting new participants. Remote records remain until routine backend cleanup or a valid deletion request.
5. Purchases and subscriptions
Apple processes App Store payments. RevenueCat receives the app user identifier, product and transaction details, entitlement status, subscription state, and related technical information needed to provide OUT!+. OUT! does not send calendar titles, precise coordinates, or Meet participant data to RevenueCat.
6. Retention messages and product measurement
OneSignal supports optional return messages and notification delivery. OUT! sends an opaque RevenueCat app user identifier, coarse subscription state, and allowlisted milestone tags. These signals do not include plan titles, destinations, calendar text, precise coordinates, participant names, or contact lists.
Layers supports privacy-limited attribution and activation measurement when configured. OUT! sends allowlisted milestone events and coarse properties. Advertising consent stays off, and OUT! does not request App Tracking Transparency for Layers. Deferred-link clipboard attribution must remain disabled in the Layers dashboard unless a separate privacy review approves it.
7. Website and waitlist
When you join the waitlist, OUT! sends your email address and waitlist source to Loops so we can send launch updates. You can unsubscribe through any waitlist email or contact us.
Our hosting provider, Vercel, processes standard network and device logs needed to deliver and protect the website. OUT! does not run third-party advertising on the website.
8. How we use information
- Build and update departure plans.
- Estimate travel, preparation, and leave times.
- Deliver alarms, notifications, Live Activities, and watch updates.
- Provide OUT!+ purchases, restores, and access control.
- Run optional Meet Mode sessions.
- Measure coarse activation and improve product reliability.
- Protect the service, prevent abuse, and comply with law.
9. Sharing and sale
OUT! does not sell personal information. OUT! does not use personal information for third-party advertising. Information is shared only with service providers described in this policy, with your direction, to protect rights and safety, or when law requires disclosure.
Service providers must process information for their assigned purpose and protect it under their contracts and applicable law.
10. Retention and deletion
- Local planning data stays on your device until you delete a record or remove the app.
- Waitlist email data stays with Loops until you unsubscribe or request deletion.
- Purchase records follow Apple and RevenueCat retention duties.
- OneSignal and Layers records follow the provider retention settings used by OUT!.
- Expired Meet records remain until routine backend cleanup or a valid deletion request.
Send deletion, access, or correction requests to support@outapp.site. We will verify the request and respond under applicable law.
11. Your choices
You control Calendar, Location, Motion, Alarm, and Notification access through the app and iOS Settings. You can decline optional permissions and continue using available features. You can unsubscribe from marketing messages and request access, correction, or deletion through the contact address below.
12. Security, children, and international processing
OUT! uses platform security, encrypted network connections, access controls, and data minimization. No security method eliminates every risk.
OUT! is not directed to children under 13. Contact us if you believe a child provided personal information.
Service providers process information in countries where they operate. Applicable safeguards and provider contracts govern those transfers.
13. Changes and contact
We will update this page when data practices change and revise the effective date above. Material changes will receive notice through the app, website, or another appropriate channel.
Privacy questions and requests: support@outapp.site