Skip to main content
DB

Disruptor Beam

GDPR evidence

disruptorbeam.comLast verified 17 Sep 2026
GDPR mark, CertReports state No public evidenceNo public evidence

Disruptor Beam and GDPR

CertReports found no public GDPR evidence for Disruptor Beam as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.

Evidence

ExpiredInactive
as of 17 Sep 2026 · confidence 100%
Kind
listing
Issued or listed
23 Nov 2016
Scope
We collect personal data in order to provide player-specific game data. The specific types of personal data we collect are Device IDs (unique to each mobile device), Player IDs which we assign to the customer based on their login from Apple or Google, and we also log IP Addresses when a player logs in. The Player ID, which we assign, is a unique ID in our back end system which we use to allow the player to log into the game, save their progress, and should they choose, make in game purchases. The Device ID and IP Addresses are used in the event of a customer complaint involving claims of fraudulent purchases. We would look to see if a purchase was made from a different Device or IP address than is normally used, and allows us to credit the customer if their account was compromised. We do not ask for any other personal information in order to play our games.
SourceCapturedQuoteLinks
Data Privacy Framework list
Official registry · HTTP 200
17 Sep 2026Disruptor Beam: Inactive
Live pagesha256 92774f25fc
What GDPR means, and what it does not

"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.

Read the GDPR guide and browse all vendors with evidence

Questions buyers ask

Is Disruptor Beam GDPR compliant?

There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.

How does CertReports verify this?

Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.

Alternatives with GDPR evidence

Similar vendors (shared product tags) whose GDPR row is verified or vendor-stated, ranked by similarity.

No same-category vendor has GDPR evidence in the index yet.