Privacy — After Landing

These notices apply to the mobile app After Landing (Android package / iOS bundle com.after.landing), operated by Clean Bytes LLC. They are not the general website privacy notice — that is at clean-bytes.com/en/privacy.

1. Controller

Clean Bytes LLC is a Florida, USA limited liability company. Where the GDPR applies — in particular to people in the EU — the following applies. We have not appointed a separate EU representative.

2. What the app is for

After Landing is a community and organisation app for adult airline crews on layover. It is not directed at children. You must be at least 18. It is not a dating app: a like is a one-way nod, not a match and not an extra chat.

3. Data we process

Account. Sign-in with Google or Apple. The identity provider typically sends a user id and an email (Apple may use a relay address). That is stored in our auth system (Supabase Auth). The app does not write email onto the public crew profile.

Profile. First name, optional last name, photo, bio, role (pilot / cabin crew / other), airline, homebase, language, theme.

Layovers and evenings. City, arrival/departure, optional hotel and notes; evening meetups (place name, address, venue coordinates, type such as restaurant/bar/club, time, description, attendance).

Communication. Chat messages. Optionally you can send a location pin (coordinates) in chat, visible to that chat’s members.

Social. One-way likes. Reports and blocks.

Verification. A photo of an airline ID and a review status. The file sits in private storage and is not visible to other users. Admins at Clean Bytes LLC can review it.

Device / operations. Approximate location while using the app, to suggest a city — we do not store those GPS coordinates on our servers for Discover, only the city you use. Push token (FCM). Last-seen (short window, “online”).

4. Purposes

Run the account, show crew in the same city, run evenings and chats, hotel reviews, limit abuse, send push, operate the app. No third-party personalised ads, no sale of data, no in-app purchases in version 1.0.

5. Visibility to other crew

Other signed-in users can see, in particular: profile (name, photo, bio, airline, homebase, role), layover city and dates, evening attendance, hotel reviews, likes depending on settings, and chat content for members of that chat including an optional location pin. ID documents are not public.

6. Recipients

• Supabase — auth, database, file storage and edge functions (host / processor).
• Google — sign-in; Maps and Places; Firebase Cloud Messaging. Search queries and, for Places, a city vicinity may go to Google.
• Apple — sign-in, if you use it.
• Google Fonts — the app loads Plus Jakarta Sans at runtime; your IP may be visible to Google’s font servers.

These providers may process data in the EU and/or third countries (in particular the USA). OpenStreetMap/Nominatim may be used as a fallback for place search. We do not publish the text of our processor agreements here.

7. Storage and deletion

You can delete your account in the app under Settings. You can also email contact@clean-bytes.com or use the delete-account page.

In-app deletion removes the profile, photos, ID document, layovers, likes, direct chats and the auth record. Evenings you created are removed with the account.

Host backups and logs may hold data for a limited time until they rotate. We do not currently publish a backup period in days. An ongoing abuse review may require limited further storage.

8. Security

Traffic uses HTTPS. For encryption at rest we rely on Supabase’s published platform statements; we have not separately certified that.

9. Your rights

Where the GDPR applies: access, rectification, erasure, restriction, portability, objection, withdrawal of consent. Contact: contact@clean-bytes.com. You may also complain to a data protection authority.

10. Changes

We will update these notices if the app or the law changes. The current version is at this URL and in the app.