← Back to home
Privacy policy
Last updated: 2026-10-11 · v1.3
1. Controller
The controller within the meaning of Art. 4(7) GDPR is:
suPlay BV
Enschede, The Netherlands · KvK 70176264 · BTW NL858175691B01
Email: info@suplay.nl
2. What we collect
The Beer Game is a small educational simulation. The data we hold falls into three groups:
- Instructor account data — your email, your chosen display name (optional),
a salted password hash, your role (user/admin), timestamps for account creation, last login
and Terms acceptance, and the verification / password-reset tokens you receive by email.
- Game data — the games you host: scenario key, decisions placed each week,
an optional chat log between seated players, and aggregate statistics that the debrief
renders. Games are linked to the instructor that created them.
- Player session data — players (your students) don't create accounts. They
claim a role in a lobby with a one-shot opaque token, stored in their browser. The server
keeps the seat name they typed and their submitted orders — no email, no IP profile.
- Administrator activity records: a short record of privileged actions,
so we can tell who did what and when. It covers administrators verifying, promoting,
demoting or deleting accounts and deleting games; instructors deleting a session,
downloading a CSV export, adding or removing a co-host, clearing a game's chat or
reissuing a player's seat link; you downloading your account data or deleting your
account; and the automatic deletion of an inactive account. Each record holds the time,
the action, the account number of whoever did it
(plus the email address of an administrator, for administrator-only actions) and the
number of the account, game or session it concerned. It never holds chat messages,
players' orders or names, join codes, seat links or passwords. When you delete your
account, or it is deleted after 24 months without a login, the record of that deletion
keeps only your former account number, never your email address or name.
3. Lawful basis
- Contract (Art. 6(1)(b) GDPR) — for processing tied to operating your instructor account and the games you host.
- Legitimate interest (Art. 6(1)(f)) — for server logs, abuse prevention, account security (login-attempt throttling), and the administrator activity records described above.
- Consent (Art. 6(1)(a)) — for any marketing or non-essential analytics. Today we send no marketing email and run no analytics scripts.
4. Retention
The deletions below for games, accounts and administrator activity records run
automatically every night. "Activity" in a game means creating it and the changes made
while playing it: a player taking a seat, an order, a chat message, or the host starting,
pausing or resuming the game, moving to the next round, restarting a round, advancing a
week, issuing a new seat link, sending a message or event, clearing the chat or muting a
player. Opening a page to look at a game, downloading it as CSV and adding or removing a
co-host do not count.
- Instructor accounts are kept while you use them, and you can delete
yours from the dashboard at any time. An account with no login for 24 months (counted
from its creation if it was never used) is deleted automatically, with its classroom
sessions. We send no reminder before this. Its games are kept but no longer linked to
the account, and from then on follow the game rules below. The last remaining
administrator account is never deleted this way.
- Games in a classroom session are kept as long as the session. Once
the session is deleted, or the account of the instructor who ran it, its games follow
the rules below.
- Lobby games outside a session that were never started are deleted
after 24 hours without activity.
- Unfinished games outside a session (started or paused, and stopped
part-way through a round) are deleted after 90 days without activity.
- Finished games outside a session are deleted 730 days (about 24
months) after their last activity, which is normally the moment they finished. A game counts as finished once one of its rounds was played to its end, even if a later round was never started or was stopped part-way. Download
a game as CSV from your dashboard if you need its results for longer. To have a game
deleted sooner, email us.
- Administrator activity records are kept for 90 days and then deleted automatically.
- Email logs from transactional mail (verification, password reset) are kept 30 days by our mail provider for delivery troubleshooting, then purged.
- Backups. Deleted data can remain in our encrypted backups until they
rotate out, at most 12 months later.
5. Cookies
We use only first-party functional cookies — the session cookie (PHPSESSID or
equivalent) and, optionally, a "remember me" cookie if you tick the box at login. No
analytics, no advertising, no third-party cookies.
6. Recipients and sub-processors
- Hosting — server01.purchasinggame.com, operated by suPlay BV.
- Outbound email — your configured Symfony Mailer transport (e.g. Resend, Sendgrid, or your own SMTP). Choose a GDPR-aligned provider; we don't read your messages.
- Font delivery — Google Fonts (Nunito). The CSS request transmits your IP to Google's font CDN; you can self-host the font in production to avoid this.
7. Your rights
Under GDPR you can request:
- Access (Art. 15) — a copy of the data we hold on you.
- Rectification (Art. 16) — correction of inaccurate data.
- Erasure (Art. 17) — deletion of your account and your classroom sessions. Games you hosted are unlinked from you and then deleted under the game retention rules above; to have them deleted straight away, email us.
- Restriction (Art. 18) and objection (Art. 21).
- Data portability (Art. 20) — your games as CSV (already available from the dashboard).
Email info@suplay.nl to exercise these. You also have a
right to lodge a complaint with the Dutch DPA (Autoriteit Persoonsgegevens).
8. International transfers
Servers and storage are located in the EU/EEA. If you configure a non-EEA mail transport,
data may be transferred to that provider; choose one with Standard Contractual Clauses in place.
9. Security
Passwords are stored as Argon2id/bcrypt hashes; verification + reset tokens are 32-byte
cryptographically random and single-use; HTTPS terminates at the front proxy; session
cookies are HttpOnly/SameSite-Lax/Secure-when-HTTPS; login attempts are throttled (5 per
15 minutes per IP).
10. Changes
We'll note changes in the "Last updated" date at the top. Material changes are sent to
every active instructor's verified email.