1. Scope & Core Principles

This policy covers the Across Us iOS app, Widgets, and supporting backend services. Across Us operates on the principle of mutual consent and minimal data retention.

2. Information We Process

• Account & Authentication: Your account identifier associated with Sign in with Apple, your provided display name and username, avatar palette, and authentication/session information. These records are linked to your account, not anonymous. We do not request your phone address book or phone number.
• City-Level Presence: Coarse city name, country code, and state or administrative region when available, resolved on-device (e.g., "New York, NY, US"). State or region helps distinguish places with the same name and choose regional artwork. It follows the same friend-sharing controls as your city. Precise coordinates used by Apple's CoreLocation stay strictly on your iPhone and are never sent to our servers.
• Friend Connections & Preferences: Friend requests, accepted friends, per-friend sharing toggles, and notification settings.
• Personal Travel Plans: Future cities, country and administrative-region information, time zones, travel dates, chosen friend audiences, plan-browsing consent, and reminder preferences. Plans are private by default. Upcoming matches require accepted friends to share eligible plans with each other. If you separately allow selected friends to view a plan, those friends can browse its full city and dates in Friend plans without a matching plan of their own. Existing plans do not gain this permission automatically. Joining a shared Trip does not automatically share a personal plan.
• Trips & Flights: Trip names, destinations, dates, membership and invitations; the flights you add, including flight number, travel date, airports, scheduled/updated times and status. Shared trip content and any previously submitted coordination notes or check-ins may be stored with the trip. Each signed-in member manages their own flight information.
• Flight Queries: Flight number and departure date used to look up flight information, cached provider responses, and request counts used to enforce service limits.
• Notifications & Devices: Installation identifier, APNs device token, delivery records, and notification preferences, including per-trip flight alerts and flight-planning reminders. When you open Trips, we store your device’s time zone and app language to schedule morning reminders at 9 AM in your local time. APNs tokens are encrypted by our backend before database storage.
• Service Operation: Authentication, request/error and security records needed to operate the service, diagnose failures and prevent abuse. The app does not include advertising or cross-app tracking.

3. How We Use Information

We use this information to authenticate accounts, maintain friend connections and sharing choices, display city presence and Widgets, synchronize shared trips across devices, process invitations, retrieve flight information, and deliver permitted notifications. Live flight alerts are optional and off by default for each trip. After you open Trips, flight-planning reminders can remind you each morning when an upcoming trip is missing your outbound flight; other trip members can also send limited reminders. You can turn these planning reminders off for each trip. Missing flight details do not tell us whether you have bought a ticket. Flight checks are periodic, not continuous; confirm travel decisions with your airline.

4. Data Sharing & Third Parties

• Accepted Friends: See your profile identity and the city presence you permit them to see. Selected friends can also browse a future plan when you explicitly enable plan browsing. You can change the audience, disable browsing, or delete the plan; subsequent reads enforce the updated permissions. Publishing a plan does not send an announcement to all friends. City-sharing settings control city presence, not personal plans or information you separately share within a trip.
• Authorized Trip Members: Can see the shared trip, participant identities and added flight details. Pausing city sharing does not automatically remove previously shared trip or flight content.
• Apple: Provides Sign in with Apple and Apple Push Notification service (APNs).
• Cloud Infrastructure (Supabase): Encrypted database storage and serverless edge functions.
• Flight Data (AeroDataBox through RapidAPI): Our server sends the requested flight number and departure date to obtain flight schedules/status. This lookup does not send your profile name, Apple account identifier or APNs token. The provider also receives technical request information from our server.

We do not sell, rent, or monetize your personal data in any way.

5. Account Deletion & Your Rights

You can pause city sharing, change notification preferences, and edit or remove your own flights using the app. Account deletion is available at You → Delete account and removes the authentication account and account-linked city, friendship and device records.

Shared trip records are separate: participant display information and previously added itineraries may remain in shared trips for other members after account deletion. Remove your own flights before deleting your account if you do not want them retained. Already delivered notifications or copies made by recipients cannot be recalled.

Records are retained to provide these features until removed through the applicable controls; operational records and infrastructure backups may remain subject to their retention cycles. For privacy or shared-record removal requests, contact us through our Support page.