Alagos Privacy Policy
Effective: November 9, 2026
Alagos is a Discord bot that helps gaming leagues, guilds and alliances run their events, attendance, rosters and rotations. It is run by Jason Lagasse, Indiana, United States (“we”, “us”).
This policy explains what Alagos keeps about you, why, who can see it, how long it is kept and how to have it removed.
Contact: alagos@nestaron.com, or the Alagos support server.
The short version
- Alagos keeps what a league needs to run: who is on its roster, who signed up and who turned up, and the league’s settings. This is tied to your Discord user ID and your in-game name.
- It cannot read the messages in your server. It does not collect your email address (unless you email us), your payment details or your IP address.
- Your league’s officers see your league’s records. Nobody else does, apart from us when we run and support the service.
- Nothing is sold, used for advertising, or used to train AI.
- A server’s data is deleted 90 days after it removes the bot. You can ask us to remove your own data at any time.
1. Who this policy covers
- Members of a Discord server that uses Alagos: signing up for events, being recorded as attending, claiming a character, using
/my-profileor/feedback. - Server owners, administrators and officers who add Alagos to a server, set it up and run it.
- People who use the Alagos support server: verifying a league, reporting a bug, asking for help.
- Servers on a paid plan, and whoever bought it (section 5, “Paying for a plan”).
Alagos runs on Discord. Your Discord account, and everything you do on Discord, is covered by Discord’s own privacy policy. We are not part of Discord and are not endorsed by it.
2. Whose data it is
A league’s records (its roster, characters, events, sign-ups, attendance, rotations, teams, seasons, awards, settings and permissions) are the league’s. The league’s officers decide what is recorded and who can change it, and Alagos keeps it for them. If you want something changed or removed in one league’s records, its officers are usually the quickest people to ask. You can also come to us directly (section 9).
Our own records are about running the service: the link between your Discord account and the league you verified on the support server, messages you send us, the bot’s logs and backups. For those, we decide what is kept, and you ask us.
3. What Alagos keeps
From Discord. Alagos uses only Discord’s “Guilds” access. It is given the server, its channels and roles, and whatever is sent to it when someone uses one of its commands, buttons or forms. It cannot read messages in your server, and does not ask for access to them. It keeps:
- your Discord user ID, when you sign up for an event, claim a character, press one of its buttons, or take an action as an officer;
- your server display name at the moment you sign up, if you have not linked an in-game character (so the sign-up list can show who you are);
- the IDs and names of the server, and of the channels and roles its officers set up.
Entered by your league’s officers, or by you.
- The roster: in-game names, whether a player is active or on leave, previous leagues, and who referred them. When a player is renamed, the old name is kept in a name history, so past records can still be understood.
- Characters and groups: a player’s character in each game the league plays, and which of the league’s groups it belongs to.
- Game details, where the league uses a game module: for DC Dark Legion, for example, power, rank, preferred train seats, and the events and times a player prefers.
- Events, sign-ups, attendance, rotations (such as the train and Guardian), team assignments, seasons and rewards.
- Loot, where the league keeps it with Alagos: points earned and spent (every change, with its reason and who made it), bids and requests for items, soft reserves, wishlists, and the items each player received, with any reason the officers gave.
- Claims: the link between your Discord account and your in-game character, once an officer approves it, or once you add your own character where your server allows it. Requests to add a character are kept with who asked and which officer decided.
- Permissions: which Discord roles may do what in Alagos.
- Event banners: images officers upload for event posts.
Anonymous feedback. Feedback sent with /feedback is stored without any record of who sent it: no Discord ID, no name, and no code standing in for either. Alagos keeps the text, its category, and the hour it was sent. Officers’ replies are kept with the replying officer’s Discord ID. Whatever you write in the message is kept as you wrote it, so leave out details that would identify you if you want to stay anonymous.
Welcome questions. If a server’s welcome flow asks you a question, Alagos keeps your latest answer to it (the answer you picked, or what you typed, up to 500 characters) with your Discord ID and when you answered, so the server’s officers can read it. It is not kept in the record of changes. Answering again replaces it.
Notifications. If Alagos sends you private messages (reminders, event changes, your train seat and so on), it keeps your choices: which kinds you want, whether an event’s messages are off, your quiet hours and the timezone you gave for them, and whether you have paused them. It keeps each message it queues for you (what it was about and whether it was sent) for 30 days, so it never sends the same one twice and can keep to a daily limit. If Discord refuses a message because your DMs are closed, it notes that for a week. Every message has a button to stop that kind, and /my-profile changes the rest.
Cleaning up event channels. A server can have Alagos remove its own messages about an event once the event is over, or clear its event channel of messages older than a set time (pinned messages, and everything from an event that is not over yet onwards, are kept). To do that Alagos remembers the IDs of the messages it posts about each event until they are removed. When it clears a channel it looks only at who posted each message, when, and whether it is pinned: it cannot read what a message says. Removing messages never removes the event’s sign-ups or attendance, which stay in Alagos’s records as above.
A record of changes. Alagos logs changes made through it (who changed a player’s details or recorded attendance, and when), so officers can see what happened and mistakes can be traced and put right.
The support server. If you verify a league there, Alagos keeps the link between your Discord account and that league, to give you the right role. Verification codes are stored only as a one-way fingerprint and expire after 24 hours. Bug reports, feature requests and support questions are posts in Discord’s own forums.
Beta codes. If your server joined the Alagos beta with a code, we keep which server used it, the Discord ID of the person who entered it, and when. Codes themselves are stored only as a one-way fingerprint.
Free trials. If your server has a free trial of Premium, we keep the server’s Discord ID, when the trial started and ends, and whether it came from a code. If it came from a code, we also keep the Discord ID of the person who entered it. Codes themselves are stored only as a one-way fingerprint. Each server can have one free trial, so the record that a server had one is kept even after the server’s other data is deleted; it holds nothing about its members.
If you email us, we keep your email and what you write, to answer you.
4. Why, and the legal basis
| What for | Legal basis (EU and UK) |
|---|---|
| Running the features a league has set up: events, sign-ups, attendance, rosters, rotations, reports | Legitimate interests: the league’s interest in running itself with the bot it chose, and ours in providing it |
| Keeping a record of who changed what, to settle disputes and correct mistakes | Legitimate interests (accountability) |
| Anonymous feedback | Legitimate interests, designed so that the sender cannot be identified |
| Verifying leagues and answering support requests | Legitimate interests, and steps you ask us to take |
| Keeping the service running, secure and backed up; logs for fixing problems | Legitimate interests |
| Removing data on request, and keeping the records the law requires | Legal obligation |
| Paid plans: knowing which server is subscribed, and recording any payment made to us outside Discord | Performing our contract with you |
We do not sell personal information, do not use it for advertising, and do not use it, or anything Alagos receives from Discord, to train machine-learning or AI models.
5. Who can see it
- Your league’s officers see your league’s records, according to the permissions the league has set.
- Members see what is posted in the server: sign-up lists, team posts, rotation posts.
- We can access the data to run, support, back up and repair the service.
- The services we use, each only for what it does:
| Service | What it does | What it receives | Where |
|---|---|---|---|
| Discord | The platform Alagos runs on | Everything Alagos posts, and what Discord sends it | United States |
| Our own server | Runs the bot and its database | All of the above | United States |
| Proton (Proton AG) | Encrypted off-site copies of the backups; the alagos@nestaron.com inbox | Encrypted backups (Proton cannot read them); emails you send us | Switzerland |
| GitHub | Hosts these policy pages | Visits to the pages | United States |
| Venmo (PayPal) | Only if you pay us by Venmo | The payment, under PayPal’s own privacy policy | United States |
Paying for a plan. Subscriptions are bought through Discord, which handles the payment. Alagos receives from Discord which server is subscribed, to which plan, when it started and ends, and the Discord ID of the person who bought it, never any payment details. If you pay us another way (for example by Venmo, part of PayPal), we keep a record of that payment: the name it came from, the amount, the server and the months it covers.
We may share information if the law requires it, or to establish or defend a legal claim. If the service is ever transferred to someone else, this policy goes with the data, and we will announce the change before anything about it changes.
6. Where it is kept
On our own server in the United States, in a database only we can access. Backups are kept on a second drive on the same private network and, encrypted, with Proton Drive in Switzerland. If you are outside the United States, your information is transferred there. Where EU or UK law applies, we rely on the safeguards that law provides for such transfers.
7. Event banners: please read
Banners are stored on our server and attached to event posts in Discord. Once posted, the image is served by Discord, and anyone given its link may be able to see it, including people outside your server. Do not upload anything you would not want seen outside your league.
8. How long it is kept
| What | How long |
|---|---|
| A league’s records (roster, characters, groups, events, sign-ups, attendance, rotations, teams, seasons, awards, loot, settings, permissions, name history, banners) | As long as the server uses Alagos |
| Beta codes: which server used one, who entered it, when | Kept as a record of the beta; the person’s ID is removed when they ask us to remove their data, and the server’s link when the server’s data is deleted |
| Free trials: the server’s Discord ID and the trial’s dates | Kept, so each server has one free trial; holds no member data |
| Trial codes: which server used one, who entered it, when | Kept as a record of the trial; the person’s ID is removed when they ask us to remove their data |
| The record of changes (who changed what) | 24 months, then deleted automatically |
| Anonymous feedback | 30 to 90 days (the server chooses) after officers mark it handled; until then, until it is handled |
| A server’s subscription (plan, dates, who bought it) | While the server uses Alagos; deleted with the server’s data |
| Records of payments made to us outside Discord | As long as tax law requires us to keep them (usually 7 years), even if the server’s data is deleted |
| Your answers to a server’s welcome questions | Until you answer again, the server removes the question, or your data or the server’s is removed |
| Your notification choices (kinds, quiet hours, pause) | Until you change them, or your data or the server’s is removed |
| Messages queued for you, sent or not | 30 days |
| Unfinished attendance panels | 7 days |
| Support-server verification codes | 24 hours |
| Your support-server verification link | Until you ask us to remove it |
| The bot’s logs | 30 days |
| Emails you send us | Up to 24 months after we answer them |
| Everything for a server that removes Alagos | 90 days, then deleted automatically (in case the bot was removed by mistake). If the bot is added back within 90 days, nothing is lost |
| Backups | Up to 14 days (daily copies), 8 weeks (weekly) or 12 months (monthly). Anything deleted can remain in a backup until that backup expires. Backups are used only to restore the service |
9. Your rights, and how to have data removed
Depending on where you live, you may have the right to see what we hold about you, to have it corrected or deleted, to receive a copy, to object to or restrict how it is used, and to complain to a data protection authority.
See or correct it. Much of it is visible in /my-profile and on your league’s posts, and your league’s officers can correct roster details. You can also email us for a copy of what Alagos holds about you.
Remove your own data. Email alagos@nestaron.com or ask on the support server. We remove your Discord account from the records of every server that uses Alagos: your character links, sign-ups and verification links are deleted, and your ID is replaced with “removed” everywhere you took an action. We aim to do this within 30 days. Before acting, we may ask you to confirm through Discord that the account is yours, so that nobody can have someone else’s data deleted.
What a removal does not cover:
- your in-game character’s attendance and history belong to the league that recorded them; ask its officers if you want them removed from its roster;
- copies in backups, until those backups expire (section 8).
Remove a server’s data. Remove Alagos from the server: everything is deleted 90 days later. A server’s owner or administrator can ask us to delete it sooner, once the bot has been removed.
Complaints. Please contact us first. You can also complain to your data protection authority: in the EU, the authority in your country; in the UK, the Information Commissioner’s Office.
10. Cookies
Alagos runs in Discord and sets no cookies. These policy pages set none either, and use no analytics or tracking. GitHub, which hosts them, may keep its own technical records of visits.
11. Security
- The database is not reachable from the internet: only Alagos itself, on the same machine, and we can reach it.
- Backups that leave our network are encrypted before they leave.
- Verification codes are stored only as fingerprints.
- Anonymous feedback is built so that its sender cannot be identified, even by us.
- We keep the software up to date and watch for errors.
No system is perfectly secure. If a breach puts your information at real risk, we will tell the people affected, and the authorities where the law requires, within 72 hours of learning of it where EU or UK law applies.
12. Children
Discord requires its users to be at least 13, or older in some countries. Alagos is not meant for anyone below Discord’s minimum age where they live, and we do not knowingly keep information about them. If you believe we do, contact us and we will remove it.
13. Changes to this policy
When this policy changes, the date at the top changes, the change is listed below, and significant changes are announced on the Alagos support server before they take effect. Every earlier version stays visible in this page’s public history.
Changes
- November 9, 2026: free trials of Premium (what is kept, and that a server’s trial record outlasts its other data).
- November 8, 2026: cleaning up event channels.
- November 8, 2026: paying for a plan (Discord subscriptions, and payments made another way).
- October 11, 2026: first published.
14. Contact
Jason Lagasse, Indiana, United States. alagos@nestaron.com