Aer-Ports LAX Beta

Privacy Notice

Effective October 6, 2026

The short version

Aer-Ports is testing whether travelers on the same flight will share useful airport context. We collect only what is needed to operate and evaluate that beta. We do not sell beta participants’ email addresses or personal travel data.

Information we collect

  • Application information: email, optional first name, optional LAX travel frequency, whether you plan to test on an LAX departure, adult-eligibility confirmation, Aer-Port Session acknowledgment, and iOS or Android preference.
  • Account information: email and the public handle or optional display name you choose.
  • Beta travel context: the flight number, route, and travel date you intentionally save to enter a temporary flight community.
  • Community activity: posts, structured report topics, replies, Helpful reactions, Confirm reactions, and safety reports.
  • Limited technical information needed for authentication, security, diagnostics, and abuse prevention.
  • Aer-Port Session information in the native beta: the result and time of an airport-presence check and limited activity events while the session is active.

How the Aer-Port Session works

The native beta will request location permission to confirm that you are within the LAX area before it unlocks your selected flight community. The Aer-Port Session remains useful through the flight’s departure window. Aer-Ports is designed not to collect or retain a continuous route, and it does not need your location away from a participating airport. Other travelers do not see your precise location.

What the beta does not require

The beta does not require a boarding-pass upload, payment, contact-list access, or investment. Aer-Ports will not publicly display your email, full itinerary, or exact location through a feed post.

How information is used

We use beta information to provide access, create the correct same-day flight room, operate community features, investigate reports, secure the service, communicate about the beta, and measure whether multi-traveler flight communities are useful and safe enough to expand.

Service providers and disclosure

Aer-Ports uses infrastructure providers such as Vercel and Supabase to host the application, authentication, and database. Information may also be disclosed when legally required, to protect safety or the service, or as part of a future corporate transaction subject to applicable law and participant notice. Aer-Ports does not sell beta participants’ email addresses or personal travel data.

Retention and temporary communities

Flight communities are intended to be time-limited. During the LAX Beta, community records may be retained long enough to evaluate usefulness, investigate safety reports, prevent abuse, and debug the service. Aer-Ports will not intentionally retain raw off-airport location history. Specific native-beta retention periods will be published before Aer-Port Session data collection begins.

Your choices

You may read without making yourself socially discoverable, choose a handle instead of a public legal name, decline optional waitlist fields, and stop participating. A signed-in traveler can permanently delete their account and connected beta information from the account page. To request access, correction, or help with deletion, email jacob@aer-ports.com from the address connected to your beta account.

Beta changes and contact

This notice describes the controlled LAX Beta, not a final public release. Material changes will be reflected here and, when appropriate, communicated to participants. Questions can be sent to jacob@aer-ports.com.