Security & privacy
Collect less, separate sensitive context, and protect every write.
ArrivalWise uses data minimization, separate public and protected records, access controls and abuse protections.
Public data
Only fields needed for aggregated estimates
- Airport, terminal, lane and broad forecast group
- Rounded completion time and duration
- Capture method and app version
- No name, email, public flight number, exact traveler type, processing method or public device identifier
Protected data
Exact context is separated
Exact timestamps, rotating pseudonymous device identifiers, optional flight, exact traveler type and optional processing method are written to non-public collections for authorized quality control, abuse review and modeling.
Access
Client reads are restricted
Firestore rules allow the app to read only the public-safe schema. Protected collections are write-only from the client; authorized backend access must use controlled administrative credentials.
Layered safeguards
Security controls work together
Authentication, app-integrity checks, validation rules and restricted data access are designed to reduce abuse. No online service can guarantee absolute security.
Plan the full arrival—not only the passport-control line.
Set your airport, current terminal, eligible lane and exact traveler type, then build a pickup or connection plan.