Privacy

What this portal stores, why, who else sees it, and how long it stays. Written against what the software actually does, not against what a portal like this usually does.

Draft, not legal advice. To be reviewed before the public launch (Plan L1/P5). The bracketed items below need filling in.

Who is responsible

Same details as the Impressum: name, postal address, email.

[ TODO: Vorname Nachname ], [ TODO: Straße ], [ TODO: PLZ Ort ], Germany · [ TODO: kontakt@playmations.com ]

There is no data protection officer. A one-person operation of this size is not required to appoint one.

You can read without an account

Browsing the catalogue, watching a preview and downloading a public clip need no account and no sign-in. For those requests the server stores nothing about you beyond the ordinary operating logs described below.

What is stored

Data	Why	Legal basis
Account: your Discord user ID and display name	So an upload has an owner and you can come back to it	Art. 6(1)(b) GDPR – performing the agreement you enter by signing in
Uploads: the `.awclip` file, title, description, tags, the sharing choice	The point of the service	Art. 6(1)(b) GDPR
Upload declaration: the exact wording you confirmed, the time, and your IP address	Evidence of who claimed the rights to a clip, if someone later disputes it	Art. 6(1)(f) GDPR – defending against rights claims
Reports: what was reported, by whom, when	Moderation, and recognising repeated false reports	Art. 6(1)(c) and (f) GDPR – obligations under the Digital Services Act
Takedown requests: name, email, the claim, time, IP address	Answering the notice and documenting the decision	Art. 6(1)(c) GDPR
Audit log of uploads, removals and moderation decisions	Being able to reconstruct what happened	Art. 6(1)(f) GDPR
Workbench sign-in: a token, of which only a SHA-256 hash is kept	Letting the Animation Workbench act for you without holding a password	Art. 6(1)(b) GDPR
Server logs: IP address, time, requested address, status	Operation, and recognising attacks	Art. 6(1)(f) GDPR

Discord is asked only for the identify scope. That is your user ID and display name – not your email address, not your servers, not your messages.

No tracking

No analytics, no advertising, no tracking pixels, no external fonts or scripts. Everything the page loads comes from this server.

Two cookies are set, both strictly necessary, both without an alternative: JSESSIONID keeps you signed in for the session, and XSRF-TOKEN stops a foreign page from acting in your name. Neither is used to recognise you anywhere else, which is why this site has no cookie banner. When you link the Workbench to your account, your browser briefly remembers the device code under aw-link-code in its own session storage; it never reaches the server and disappears when you close the tab.

Who else sees it

Contabo GmbH, Munich, Germany – the server this runs on. Data stays in Germany.
Data processing agreement (Art. 28 GDPR) with Contabo: conclude and file before launch.
Discord – only if you choose to sign in. You are sent to Discord, and Discord learns that you signed in here. Their privacy policy applies to that step.
[ TODO: Mail provider ] – delivers notification mail about reports.
Name the provider once the mail channel is set up, or delete this line if notifications stay on Discord only.

Nothing is sold, and nothing is passed on for advertising.

How long

IP addresses in declarations, reports and takedowns: replaced by a keyed pseudonym after 30 days. The record stays, the address does not. Running this is a scheduled job on the server, not a promise for later.
Your account and uploads: until you delete them or the account.
Removed clips: the file goes, the record of the decision stays – it is what stops the same clip being uploaded again.
Audit log and moderation decisions: kept as long as they can still matter for a dispute.
Server logs: a few days, rotating.

Your rights

You may ask for access (Art. 15), correction (Art. 16), deletion (Art. 17), restriction (Art. 18), portability (Art. 20), and you may object to processing based on legitimate interests (Art. 21). One email to the address above is enough; no form.

You may also complain to a supervisory authority.

Name the competent authority – the one for the state you live in, e.g. Bayerisches Landesamt für Datenschutzaufsicht for Bavaria.

Changes

If this page changes in a way that affects you, the change is announced on the portal before it takes effect.