Order 66 (ORDR66) is a Star Citizen player organization. This policy covers this website and the SC-Comms voice app. We run them to manage recruitment, operations, fleets and voice comms for our members and allies. We are not affiliated with Cloud Imperium Games or Discord.

For any privacy question or request, email Cybo.game@gmail.com, or message an officer in our Discord server.

When you sign in with Discord. We ask Discord for your user ID, username, avatar, display name or server nickname, and the roles you hold in our server. We do not ask for your email address and we never see your Discord password. We use this to sign you in, decide what you can see, and show your name and avatar to other members. We do not keep your Discord access token.

If you apply. Your RSI handle, timezone, when you play, your Star Citizen experience, why you want to join, and an optional “referred by”. Officers read this to decide your application.

If you apply as a creator. The name(s) you create under and the links to your channels. Officers read these to decide whether to give you read-only access to the operations and calendar pages. You do not need to be in our Discord server.

If you link your RSI account. Your RSI handle, a one-time code you put in your RSI bio, and whether you are in our RSI organization. To check these we send your RSI handle to the third-party service starcitizen-api.com, which reads your public RSI profile.

Your hangar. The ships you add. If you use the import bookmark, a script runs in your own browser on your own RSI hangar pages and sends only ship names to us. Your RSI login, cookies and everything else on those pages stay in your browser.

Operations. Your RSVPs and seats, ally sign-ups (ship, role, organization, optional note), and the operations you create. Commendations awarded to you, with any citation.

Voice comms (SC-Comms). Voice is relayed live between participants and is not recorded or stored. The relay receives your Discord ID, display name and comms tier from the website so it can place you in the right channels. If a leader removes someone from an operation's comms, we record who was removed, by whom, the operation, the reason given and the time.

Page views. To see which pages are used, we log the page address, the website you came from (hostname only) and a code made from a one-way hash of your IP address and browser details that changes every day. It is not linked to your account, and it uses no cookies or browser storage.

Cookies. Only what is needed to keep you signed in and secure the sign-in: a session cookie (up to 30 days) and short-lived sign-in security cookies. We use no advertising or analytics cookies, so there is no cookie banner. When you press play on a video, YouTube (privacy-enhanced mode) may set its own cookies.

Hosting logs. Our hosting provider may log requests, including IP addresses, for security and operation.

We do not sell your personal information, we do not share it for advertising, and we make no automated decisions about you. Officers see attendance and activity reports to help them run the organization; people make the decisions.

Where the GDPR or UK GDPR applies: running your account, applications and sign-ups is needed to provide what you ask for (contract or steps before joining); running a safe, organized community, keeping a moderation record and measuring page use is our legitimate interest, which we weigh against your rights; we rely on consent only if we ask for it clearly.

• Members can see your name, avatar, rank, verified RSI handle, ships, and your RSVPs and seats.
• Allies see the operations open to them, seat counts without names, and the other allies signed up.
• Approved creators can see the operations that officers have opened to creators, the same way members do. That includes the briefing, the fleet and seat assignments, and the names and avatars of the members who are going. They cannot RSVP or take seats.
• Officers additionally see applications (including creator applications), commendations, attendance and activity reports, and moderation records.
• Service providers that process data for us: Railway (our hosting provider), Discord (sign-in, roles, notifications and the server widget), starcitizen-api.com (RSI profile checks), and GitHub (the SC-Comms app checks it for updates, which reveals your IP address to GitHub). The UEX Corp ship catalog is fetched by our server and receives none of your data. Avatars and ship photos are fetched by our server, so your browser does not contact those sites.
• We disclose data if the law requires it or to protect people's safety.

Our providers are mostly based in the United States, so your data may be processed outside your country. We rely on the safeguards those providers offer, such as standard contractual clauses.

• Account, RSVPs, hangar, commendations: while you have an account. People who leave our Discord server and do not sign in for 365 days have their account erased.
• Application and creator-application answers: the text (including creator names and channel links) is removed 180 days after a decision. We keep only the outcome and date, so the 30-day reapply rule works.
• Page-view log: 90 days.
• Comms moderation records: 365 days.
• Delivered Discord notification jobs: 30 days.
• Backups made by our hosting provider may keep deleted data for a short time longer.

Signed in, your profile page lets you download a copy of your data and delete it. Deleting removes your applications, RSVPs, hangar, ally sign-ups and commendations, clears your profile and signs you out. Operations you led remain, shown as led by “Deleted user”. Deleting does not remove you from the Discord server or change your Discord roles; an officer can do that.

You can also ask us to correct your data, restrict or stop using it, or send it to you in another form. Contact us: email Cybo.game@gmail.com, or message an officer in our Discord server. We will answer within the time the law requires (generally one month). To correct your name, avatar or roles, change them in Discord; they refresh when you next sign in and every 15 minutes through our bot.

If you are in the EU, UK or a similar region you have rights of access, correction, erasure, restriction, portability and objection, and you can complain to your data protection authority. If you are in California or a state with a similar law you can ask to know, correct and delete your personal information; we do not sell or share it, and we will not treat you differently for asking.

• Push-to-talk keys. So your keys work while Star Citizen is in focus, the app watches keyboard and mouse-button presses system-wide. It reacts only to the keys you bound to push-to-talk and ignores and discards everything else. It never records, stores or sends what you type.
• Microphone. Your microphone is used only to capture audio, and audio is sent only while you hold a push-to-talk key. Nothing is recorded.
• On your device. Settings such as your keybinds, microphone choice and per-person volume are saved on your computer and not sent to us.
• Sign-in. Signing in opens your browser. The app listens briefly on your own computer (127.0.0.1) to receive the sign-in result.
• Updates. The app contacts GitHub to check for and download updates. The app may ask to run as administrator so keybinds work while the game has focus.

The website and app are not for children. You must be old enough to use Discord in your country (at least 13) and to meet the age rules of Star Citizen. We do not knowingly collect data from anyone younger. If you think a child has given us data, email Cybo.game@gmail.com, or message an officer in our Discord server and we will delete it.

Connections use HTTPS, sign-in cookies are not readable by scripts, and access to officer tools is limited by Discord role. No system is perfectly secure; if a breach affects you we will tell you as the law requires. We will update this page when our practices change and change the date at the top.