Slavic Airlines GroupEST. 1929 · EPWA WARSAW
Slavic Airlines GroupEST. 1929 · EPWA WARSAW
Legal
What we collect, why we collect it, where it goes, and how to get rid of it. Written to be read, not to be skipped.
Last updated: 6 September 2026
Slavic Airlines Group ("SAG", "we", "us") is a hobbyist virtual airline for flight simulation. We are not a real airline, not a business, and not affiliated with any real-world carrier. This site is operated by a private individual, and we are the data controller for the information described below.
For any privacy question or request, contact us at ops@slavicairlines.com.
When you create an account on this site we store your username, an encrypted form of your password and, only if you choose to give one, your email address. We never see or store your password in readable form.
Our flight operations run on vAMSYS, a third-party virtual airline platform. If you choose to link your vAMSYS pilot account to this site, we access the following through the vAMSYS Pilot API, and only with your explicit authorisation:
You grant this access through a consent screen operated by vAMSYS, and you can revoke it at any time from your vAMSYS account settings. Revoking access stops us receiving any further data. It does not by itself delete what we already hold — see "Deleting your data" below.
vAMSYS is the controller of your underlying user account, and its own privacy policy governs that relationship. Ours covers only what we receive and store.
What we actually keep from the link: your vAMSYS user id, pilot id, pilot username (for example PSL0042) and home hub id on your profile, and the access tokens vAMSYS issues to us, which are stored encrypted (Supabase Vault) and used only to read the data listed above and, when you ask for it, to book or dispatch flights for you. "Unlink" on your Account page deletes the tokens and the ids immediately.
We store records of flights flown for the airline: departure and arrival airports, aircraft registration, flight numbers, times, passenger loads, and the performance figures produced by the flight tracker. This is what drives the fleet board, the operations page, and pilot statistics.
Some optional features let you save a personal API key from another service — for example SayIntentions.AI, so that flight details can be sent to your own simulator session. If you provide one, it is stored encrypted (Supabase Vault), is never displayed again on the site, and is used only for that purpose by our backend. We never share it, and you can remove it from your profile at any time. If you would rather not store a key with us, simply do not use those features; everything else works without them.
Our hosting provider processes standard web request information — IP address, browser type, and pages requested — as part of serving the site and protecting it from abuse. We do not use advertising trackers, we do not sell data, and we do not build advertising profiles.
This site loads fonts from Google Fonts, which means your browser contacts Google's servers and your IP address is visible to them as part of that request. We do not send Google anything else about you.
Plainly: to run the airline. Account data identifies you. Flight data produces your logbook, rank progression, the live fleet map, and the operational picture on the Ops page. Linked vAMSYS data lets us show your flights on this site instead of making you visit two places. That is the whole purpose.
We rely on your consent for the optional integrations, and on our legitimate interest in operating a members' hobby site for the rest. You can withdraw consent for any optional integration at any time without losing your account.
We do not sell your data and we do not share it for marketing. Data is processed by the services that make the site work:
Some information is public by design within the airline: your pilot name, ID, rank, and flight statistics may appear on rosters, leaderboards, the live map, and pilot profiles visible to other members and to site visitors. If you would rather not appear publicly, tell us and we will discuss what can reasonably be hidden.
Weather and daylight information shown on the Ops page comes from public sources (the NOAA Aviation Weather Center and sunrise-sunset.org) and involves no personal data about you.
Our database and backend are hosted on infrastructure operated by Supabase and Cloudflare, which may store and process data in facilities outside your home country, including outside the European Economic Area. Those providers operate under standard contractual protections for international transfers.
Account and flight data is kept for as long as you are a member. If you leave or ask to be removed, we delete your personal data. We may keep flight records in an anonymised form — stripped of anything identifying you — so that network and fleet history remains coherent.
You can ask us to:
Email us and we will action it. We aim to respond within 30 days. If you are in the EEA or UK and are unhappy with how we have handled a request, you have the right to complain to your national data protection authority.
Ask us and we will delete your site account and everything personal attached to it. Two things worth knowing: revoking the vAMSYS connection stops new data arriving but does not delete what we already have, so ask for both if you want both; and deleting your SAG account does not touch your vAMSYS user account, which is separate and managed by vAMSYS.
This site is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has registered, contact us and we will remove the account.
Access to the database is restricted, credentials and API keys are held as server-side secrets rather than in the site's public code, and traffic is encrypted in transit. We take it seriously, but no system is perfectly secure, and we cannot promise absolute protection. If something goes wrong that affects you, we will tell you.
If we change this policy we will update the date at the top. For anything significant — a new integration, a new category of data — we will notify members directly rather than quietly editing the page.