Fleet Command: Privacy Policy
Effective date: October 21, 2026
This policy explains what information Fleet Command (the "Bot": a Discord bot, its website and its optional browser extension Fleet Command Connect) keeps, why, and how you can have it removed. The Bot is run by the volunteers who operate Fleet Command ("we", "us").
The short version: the Bot only keeps what it needs to organize ops. It can't read your chat messages, it doesn't send DMs, and we never sell or share your information.
1. What the Bot can't see
The Bot only uses Discord's basic permissions. It does not read the messages you post in channels, your DMs, or the server's member list, and it does not track your activity or voice chat. (When a lead looks up a member by name to give them a seat, the Bot asks Discord for members whose names start with what the lead typed; nothing from that search is kept.)
2. What we store
The Bot stores information only when you use its features:
| Information | When it's stored | Why |
|---|---|---|
| Your Discord user ID and display name | When you sign up for a seat, offer a ship, or add a ship to your fleet | To show who is in which seat and to let only you change your own things |
| Your gamer tag (Star Citizen handle) | When you type it into a sign-up form | To show it on the roster, and so you don't have to retype it next time. It's remembered separately for each server, so one server never sees a handle you typed in another |
| Seat sign-ups and ship offers (ship, roles, notes, the seat you want on your own ship) | When you sign up or offer a ship | To build the op's crew list |
| An op's standby list (you're signed up for an op without a seat) | When an op lead takes you out of your seat, removes your seat or ship, or adds you to the op | So leads can still seat you. Taking a seat or dropping out takes you off it |
| Your preferred crew role (for example Gunner) | When you choose one in My Fleet | So op leads' Auto-fill can seat you in a role you like. It's kept separately for each server; choose "No preference" to remove it |
| Your fleet (ships, nicknames, notes, crew seats, whether each ship is available, and for ships synced from RSI their pledge number) | When you add ships to My Fleet, from the menus, by uploading a spreadsheet or file (read once and not kept), or by syncing your RSI hangar (section 4) | So leads can see which ships members can bring, and so the next sync can update your RSI ships |
| Ops, templates and settings (titles, times, staging locations, descriptions, channels, who created them) | When a lead creates them | To run and post the op |
| Ship pictures | When a lead uploads one | To show on that server's op briefing cards |
| Your own pictures of your fleet ships | When you upload one for a ship in My Fleet | To show with that ship in My Fleet, in the server's Org Fleet and on op cards and summaries when your ship is in an op. Only members of that server can see them; its op leads can remove them |
| Official Fleet (which of your fleet ships a server's leads picked for their org's fleet, its division, which lead added it and when) | When a lead adds one of your ships | To show the org's official fleet. Removing the ship from My Fleet also takes it out |
| Server settings (org name, time zone, chosen lead role, reminder channel, fleet divisions, and a fingerprint of the public fleet feed key) | When a server's leads or admins change them | So the Bot works the way each server wants |
Server, channel and message IDs are stored so the Bot can update its own posts. The Bot can be added to more than one Discord server. Each server's ops, fleets, templates, pictures and settings are kept separate, and other servers can't see them.
3. The web dashboard
Members and leads can also use the Bot from a website instead of Discord. To log in, you click Log in with Discord and approve it on Discord's own page. Discord then tells the website your user ID, username, display name, avatar and which servers you're in (the "identify" and "guilds" permissions).
- The website keeps only your user ID, display name, avatar and the servers you share with the Bot, in a signed cookie in your own browser. It lasts 7 days, or until you press Log out. If you press Log out on every device, the Bot stores your user ID and the time, so older logins stop working.
- Discord's login token is used once and never stored.
- Each page asks Discord whether you're still in that server and what your roles are, so leaving a server or losing a role takes effect straight away. That answer is kept in memory for a few minutes, never on disk.
- Anything you do on the website (signing up, your fleet, managing ops) is stored exactly as if you had used the buttons in Discord, as described above.
- For security, the server's log notes when a button on the website is pressed: your user ID, the page and the result. It never records what you typed. These logs are deleted automatically after about a month. Your internet address is used for a few minutes to limit login attempts and is never saved.
4. Syncing with your RSI hangar
You can bring in the ships from your RSI "My Hangar" page. It's optional, and there are two ways:
- The Fleet Command Connect browser extension. When you click Sync from RSI on the website, the extension opens your "My Hangar" pages on robertsspaceindustries.com in the background, using the login you already have in that browser. It keeps only the ships from those pages (each ship's name, the name you gave it, its insurance and the pledge number) and passes only that to the website, which shows it to you before anything is saved. The extension never sees or asks for your RSI password, never reads any other page or website, never changes anything on your RSI account and does nothing until you click the button. It has no tracking or analytics and keeps nothing in your browser.
- A file from hangar.link (its Export CSV or Save Pledges file). It's read once and not kept. Only the ships are taken from it, like a spreadsheet.
Once you save, these ships are part of your fleet as described in section 2, and each one's pledge number is kept so the next sync can update it. If you choose Sync in all my servers, the same ships are saved to your fleet in each Discord server you're in that uses Fleet Command; each server still has its own copy and only sees that one. Prices, dates and anything else in your pledges are never stored.
Public fleet feed. A server's admins can turn on a feed that lets their org's own website show the server's fleet. It shares only ship counts: how many of each ship are in the Official Fleet (by division) and in all members' fleets together, how many members own each ship and how many are available, with each ship's maker and standard crew size. It never includes names, user IDs, gamer tags, nicknames or notes. Only a website holding that server's secret key can read it, and an admin can turn it off at any time.
Public ops feed. With the fleet feed on, a server's admins can also choose to share upcoming ops with their org's website, using the same key. It shares only ops posted in the channels the admins picked: each op's title and description (with any mentions removed), the day it happens (never the time), the types of ships in it, how many crew seats there are and how many are taken, and a link to the op post in Discord. It never includes who signed up, names, user IDs, gamer tags, offers or notes. Admins can stop sharing at any time, and it stops whenever the fleet feed is turned off.
5. How it's used
Only to run the Bot's features, in Discord and on its website. Your information is shown in the servers where you use the Bot, and on the website to people in those same servers (for example, your name on an op roster). We don't sell it, share it with advertisers, or use it for anything else.
6. Where it's kept and who can see it
Data is stored in a database on a private cloud server that only the Bot's administrators can access. Discord also processes everything sent through it, under Discord's Privacy Policy. The server downloads ship pictures from the Star Citizen Wiki (starcitizen.tools) and RSI's public ship list (robertsspaceindustries.com); nothing about you is sent with those downloads.
7. How long we keep it
- Op data stays until a lead deletes the op. Deleting an op also deletes its seats, ships and offers.
- Your fleet stays until you remove the ships. Removing a ship (or its picture) also deletes your picture of it.
- Your remembered gamer tag stays until you ask us to remove it.
- The website's login cookie lasts 7 days, or until you log out.
- Backup copies are kept for safety. Only a small number of the newest backups are kept and older ones are deleted automatically, so deleted data drops out of backups over time.
8. Your choices
- Drop out of an op at any time with the Drop Out button.
- Remove ships from your fleet, or your pictures of them, in My Fleet.
- Ask us to delete everything about you: ask an admin of the Discord server where you use the Bot to pass it on to us. We'll remove your information from the Bot's database.
9. Children
The Bot follows Discord's age rules and is not meant for anyone below Discord's minimum age.
10. Changes
We may update this policy. The effective date at the top will change when we do.
11. Contact
Questions or deletion requests? Message an admin in the Discord server where you use the Bot. They can pass it on to us.