What Counts as a Breach
Under the GDPR, a personal data breach is a security incident that leads to personal data being destroyed, lost, altered, disclosed or accessed without authorisation. For example:
- Someone gets into our database or servers
- Personal data is exposed publicly by mistake
- Stored data is changed or deleted by someone who shouldn't be able to
How We Limit the Risk
- All traffic to discordium.org is encrypted with TLS.
- Sign-in refresh tokens and API tokens are stored only as hashes.
- We don't store card numbers or other payment credentials. Stripe handles payments.
- Accounts have no password of their own, so there is no password database to leak.
What We Do
- Contain it and secure the affected systems.
- Work out what happened, which data was affected and whose.
- Report it to the supervisory authority and tell the people affected, where the law requires it (below).
- Fix the cause.
- Record it. We document every personal data breach, including ones we don't have to report.
Telling the People Affected
If a breach is likely to pose a high risk to you, we tell you without undue delay (Art. 34 GDPR). We don't hold an email address for your account, so we post a notice on discordium.org, and email you as well if we have your address (for example because you bought Premium or wrote to us). The notice says:
- What happened and which data was affected
- What it could mean for you
- What we've done about it
- What you should do, if anything
- Who to contact with questions
Breaches at Our Providers
A provider that processes data for us has to tell us about a breach on their side, and we handle it the same way. The providers are listed under Data Processors.
Report a Security Problem
Found a vulnerability or a leak? Email support@discordium.org.
Last updated: October 2026