Privacy Policy

Last updated: 5 August 2026

This policy covers the R2-D2 Discord bot, operated by Mar Trepodi. It describes exactly what the bot stores about you, why, how long it keeps it, and how to get rid of it. It is written to be read.

The short version. R2-D2 stores your Discord ID, your Star Wars: Galaxy of Heroes ally code, and — only if you choose to link an EA account — a credential that lets it act on that account in game. It does not store your game data: everything shown to you is fetched live and discarded. Running /unlink deletes your credential and your data. Your EA password is never seen by the bot at any point.

Who operates this

R2-D2 is a free, non-commercial Discord bot run by Mar Trepodi on self-hosted infrastructure. It is not affiliated with, endorsed by, or connected to Electronic Arts, Capital Games, Lucasfilm, or The Walt Disney Company.

For anything in this policy, including access and deletion requests, contact contact@swgohutilsonline.com.

What the bot stores

Data	Why	Kept until
Your Discord user ID	To connect you to your registered accounts	You deregister, or ask us to delete it
Your SWGOH ally code(s), and a display name	So commands know which account you mean	You deregister that account
EA account credential — an account identifier and a refresh token, encrypted at rest	To create game sessions on your behalf without asking you to sign in every few hours	You run `/unlink`
Audit log of authenticated game actions — what was done, when, by which Discord user	Security. It is how you or we can tell what happened to your linked account	Retained after deletion — see below
Error logs, which may include your Discord ID or ally code	Diagnosing failures	Rotated on a short schedule
Per-Discord-server settings	Which commands are enabled in a server	The bot is removed from that server

What the bot does not store

Your game data. Rosters, guild information, Territory War and Conquest state are fetched live each time you run a command and are not written to any database. There is no cache. When you stop using the bot, there is no accumulated copy of your game history to delete, because one was never made.
Your EA password. The bot never receives it. Linking works by a one-time code that EA emails to you, which is exchanged for a credential and then discarded.
One-time codes. Never written down, in any form.
Active session identifiers. Held in memory for the life of a session and never written to disk.
Message content. The bot reads the commands you run, not your conversations.

The EA credential, in plain terms

This is the most sensitive thing the bot holds, so it is worth being direct about it.

When you link an EA account, the bot stores a refresh token. That token lets it create game sessions as you, without a fresh sign-in each time. Those sessions are read-write, meaning they are technically capable of taking actions in your game account, not only reading from it.

What protects it

It is encrypted at rest, with a key held outside the database. The bot refuses to start if that key is missing, so it cannot accidentally run storing credentials in the clear.
Nobody can act as your account except you. There is no command — at any permission level, including the bot operator's — that runs as another user's linked account. This is deliberate: an operator who could impersonate would be a single point of compromise for every linked account.
Discord server administrators have no access to your linked accounts or your data. They configure their own server and nothing else.
Every authenticated action is written to the audit log.

You can revoke the credential at any time with /unlink. You can also revoke access from EA's side by changing your EA password, which invalidates the token independently of us.

Who else sees your data

The bot shares data with no one for marketing, analytics, or profiling. There are no ad networks, no trackers, and nothing is sold. Data reaches exactly three places:

Discord — necessarily, because that is where the bot runs and where responses are displayed. Discord's own privacy policy governs that.
The SWGOH game servers (Electronic Arts / Capital Games) — when a command asks the game something on your behalf. This is the point of the bot.
A game API service operated by us, self-hosted, which relays requests to the game servers. It is not a third party and does not share data onward.

Who can see your information in Discord

Linking an account in one Discord server does not reveal it to any other. Being in a server does not disclose your accounts to that server. Guild-wide views — Territory War, Territory Battle contribution — show information only to members of your own in-game guild, and are resolved from your own linked account rather than from a server setting.

Deleting your data

/unlink is the real thing, not a soft delete. It:

tells the game API service to destroy the account link entirely;
deletes the stored credential from our database;
purges data associated with that account.

It cannot be undone. Linking again afterwards creates a completely new identifier — the old one is gone, not restored.

/deregister removes a registered ally code without touching an EA link.

One exception, stated plainly. Audit log entries survive deletion. That record — that an account was linked, what was done with it, and that it was later removed — is the point of having an audit log at all; erasing it on request would make it useless precisely when it matters. It contains actions and timestamps, not credentials or game data. If you need those entries removed too, contact us and we will discuss it.

Your rights

Wherever you live, you can:

See what we hold about you — ask, and we will tell you. /auth-audit shows your own audit trail directly.
Delete it — /unlink and /deregister do this yourself, immediately, without asking anyone.
Correct it — most of what we hold is a Discord ID and an ally code you supplied; re-register to change them.
Object — stop using the bot and delete your data. Nothing is retained to keep a relationship going.

If you are in the EU, UK, or California, the substance of your access, deletion, and portability rights is honoured as described above. Requests go to contact@swgohutilsonline.com, and we will respond within 30 days.

Security

Credentials are encrypted at rest with a key stored separately from the database and managed in a password manager rather than on the host. The service runs on self-hosted infrastructure that we control. Access to the underlying systems is limited to the operator.

No system is perfectly secure, and this one is run by a person rather than a company. If you would not be comfortable with a hobby project holding a credential to your game account, do not link one — the bot's unauthenticated commands work without it.

If you find a security problem, please report it to contact@swgohutilsonline.com rather than disclosing it publicly.

Children

Discord requires users to be at least 13, or older where local law sets a higher age. This bot is not directed at children and we do not knowingly collect data from anyone below Discord's minimum age. If you believe a child's data is stored here, contact us and it will be removed.

Changes to this policy

If this policy changes materially — particularly what is collected or how long it is kept — the date at the top will change and a notice will be posted in the bot's support channel. Continuing to use the bot after a change means accepting it; if you would rather not, /unlink and stop.

Contact

contact@swgohutilsonline.com — for privacy questions, data requests, and security reports.