Last updated: 2026-06-26
PSCC Flight Centre ("the site") is a private coordination tool for members of the PSX Shared Cockpit Crew (PSCC) community and their friends. Access requires an admin-approved account. This policy explains what personal data is stored, why, and what your rights are.
Data controller contact: the site administrator (reachable via your PSCC community channels).
| Field | Purpose |
|---|---|
| Username | Login identifier and display across the site |
| Display name | Shown on crew lists, schedule, and flight board |
| Email address | Account recovery and admin notifications |
| PSCC ID | Your PSCC community pilot identifier (optional) |
| VATSIM CID | Used to look up your current VATSIM online status (optional). We store only the numeric CID — your VATSIM password is never requested or stored. |
| Timezone preference | Displayed times use your configured timezone |
| Account creation and last login timestamps | Admin oversight and account hygiene |
| Password (bcrypt hash only) | Authentication — the plaintext is never stored or logged |
| IP address | Recorded in web server and reverse-proxy access logs for security and abuse prevention; not stored in the application database |
| Data | Purpose |
|---|---|
| Simulator display names and configuration | Identifying your simulator on the map and fleet |
| Flight path (GPS waypoints recorded every ~15 s) | Drawing the live and historical flight track on the map |
| Flight number, departure and arrival airports, start/end times | Flight log and board display |
Flight path data is stored while the flight is active and retained after the flight ends to support the historical track feature. It is deleted automatically when you delete your account.
Flight plans contain crew names (free-text fields for P1/P2 across departure, cruise, and arrival phases), callsign, route, schedule, and notes. These are visible to all logged-in users and retained until manually deleted or your account is removed.
If you sign up for WorldFlight events, we store: leg assignments (phase and role), bidding preferences and comments, leg assignments confirmed by an admin, and scenery library entries. All of this is retained until you delete your account.
Schedule slots you create are attributed to your account and visible to all logged-in users.
If the ACARS ground station is configured, sent and received telex messages are stored including station callsigns and message text. Messages are routed through the Hoppie ACARS network, which makes them publicly visible — anyone can browse the live message log at hoppie.nl/acars/system/log.html. Do not send sensitive information over ACARS.
Crew assignment changes and airframe changes are recorded in audit logs, including your username, for admin oversight. These logs are retained for operational integrity and may not be immediately purged on account deletion (see Right to erasure below).
Processing is based on performance of the service you signed up for and the legitimate interests of the PSCC community in running a shared flight coordination tool. We do not use your data for advertising or profiling.
No unencrypted passwords or session tokens are stored on disk.
| Name | Type | Purpose | Consent |
|---|---|---|---|
psccfc_session |
Cookie (HttpOnly, encrypted) | Keeps you logged in. Contains only your numeric user ID, encrypted. | Strictly necessary — no consent required |
psccfc_map_layer |
Browser localStorage | Remembers which map layer you last selected (e.g. Light, Satellite). | Functional preference, stored only in your browser, never sent to our server |
wf_cookie_consent |
Cookie | Remembers your yes/no answer to the cookie prompt on the public WorldFlight music/merch pages, so we don't ask again. | Strictly necessary — no consent required |
wf_visitor_id |
Cookie (HttpOnly) | A random number, set only if you accept the cookie prompt on the public WorldFlight music/merch pages. Used to count unique visitors, song plays, downloads, and merch "purchases" on those two pages. Not linked to any account, name, or email, and not used anywhere else on the site. | Opt-in — only set if you accept the prompt |
wf_preview_code |
Cookie (HttpOnly) | Set only if you enter a valid preview code on the jukebox's keypad on the public WorldFlight music page, so you don't have to enter it again. Contains the code itself, no personal data, and is not linked to any account, name, or email. | Set only at your request (entering a code) — not a tracking cookie |
Aside from that one opt-in counter on the WorldFlight music/merch pages, we use no tracking cookies, no third-party analytics, and no advertising technology.
| Service | What is shared | When |
|---|---|---|
| Map tile providers (OpenStreetMap, OpenTopoMap, ESRI World Imagery, ESRI Gray Canvas) | Your browser requests tiles directly from these CDNs. They see your IP address and the map area you are viewing — the same as visiting any website that uses these maps. No personal data from our server is sent to them. | When you view any map page |
| VATSIM (vatsim.net) | If you provide a VATSIM CID, our server calls the public VATSIM API with that CID to check your current online status. The CID is already public information on the VATSIM network. | Periodically while the server is running, if you have set a VATSIM CID |
| Hoppie ACARS (hoppie.nl) | If the ACARS feature is configured by the admin, aircraft telex messages (callsigns and message text) are routed through the Hoppie ACARS network. | Only when the ACARS ground station is active and messages are sent or received |
We do not share your name, email, or any other account data with any third party.
Under GDPR you have the right to:
You can delete your own account at any time from your profile page (scroll to the bottom). This will:
ACARS ground-station messages are not linked to user accounts (they are keyed by aircraft callsign) and cannot be selectively deleted. For a complete wipe including ACARS message history or audit log entries, email the admin at the address in your PSCC community channels with the subject line "GDPR erasure request". We will action it within 30 days.
If we make material changes, you will be asked to re-accept the updated policy on your next login.