Privacy & cookies

Updated 23 September 2026. This notice covers the Omega Flight website and the connected Omega DCS servers. Omega Group operates these services. Contact the team through Message admins for privacy questions, corrections or removal requests.

What we record and why

We use account information, password hashes, callsigns, squadron assignments and aircraft preferences to provide profiles and access controls. DCS records include player identifiers (UCIDs), connections, IP addresses where recorded, aircraft, missions, flight events, kills, fuel observations, awards and virtual-credit transactions. These support server operation, flight history, competition, economy accounting and abuse prevention. We also store messages you submit and security/audit records of administrative actions. The contact form uses an IP-derived hash for message limits.

Who can see it

The public roster shows active pilots' callsigns, squadron, rank, primary aircraft, flight hours, kills, accolades and virtual-credit balances. The home page shows connected DCS pilots and live activity. Signed-in members can view more detailed flight and financial records. Squadron announcements are restricted to the squadron and Web Admins. Conversation participants and Web Admins can access private conversations; these are not end-to-end encrypted. Authorized administrators can access operational and security details. Account email addresses, IP addresses and UCIDs are not part of the public roster.

Discord and other sites

Configured pilot activity and website news can be posted to Omega's Discord channels. Those copies are governed by Discord's service and privacy practices as well as channel access settings. Deleting a website profile does not automatically delete Discord history. Links to Discord and other websites take you to services operated by others; this website does not embed Discord tracking widgets.

Cookies and browser storage

We use the first-party OMEGASESSID session cookie for sign-in, security tokens, form protection and temporary preferences. It is a session cookie; browsers may restore sessions when reopening. Signed-in sessions expire after eight hours without activity. We currently use no advertising or analytics cookies or tracking pixels. Browser settings can block or clear cookies, but sign-in and protected forms will not work correctly without the session cookie.

The cookie notice's “Got it” button saves a first-party omega_cookie_notice preference cookie for up to 400 days, so the notice stays dismissed across sign-outs and later visits in the same browser. It contains only the notice version, not a personal identifier, and is not used for tracking. The notice can appear again if you clear cookies, use another browser or the preference expires. Acknowledgement does not give consent to advertising or analytics. If optional tracking is introduced later, this notice and the controls will need to change before it is enabled.

Retention and deleting your profile

You can delete your own website profile from its Profile section after confirming your password. This removes website identity fields and sign-in access, hides the profile from the roster and removes assignments and permissions. A minimal deleted-account marker remains to prevent accidental reactivation.

Shared game and economy history, DCS identity and callsigns, security/audit logs, messages already shared with others, Discord posts and backups are not all erased by this action. These records support shared history, transaction integrity and abuse investigation. The game database currently has no general automatic expiry for historical records. Continuing to use a DCS server creates further records and can appear on its live player listing. Ask the admins to review a broader deletion or access request; they will consider the records involved and applicable requirements.

Your choices

You can change your primary aircraft on your profile, request a squadron transfer, delete your website profile, or contact the admins to request access to your data, a correction or further removal. Do not send your password through the contact form. This notice describes the current system; it does not promise that all historical copies are erased by profile deletion.