The controller responsible for data processing in connection with the VR game Tesserian is:
Henryk Trappmann
c/o POSTFLEX PFX-626-521
Emsdettener Straße 10
48268 Greven, Germany
E-mail: admin@eretrandre.org
See also the legal notice (Impressum).
Tesserian is distributed through three stores: the Meta Quest Store (Meta Quest headsets), the PICO Store (PICO headsets) and Steam (PC VR). This policy covers all three. Below, your store is the one you obtained the game from, your store account name is the name that store shows for you (your Meta Quest username, your PICO display name or your Steam persona name), and your device is the headset, or on PC VR the computer the game runs on.
| Data | When | Purpose | Where it is processed and stored | Retention |
|---|---|---|---|---|
| Entitlement status — whether your Meta account owns Tesserian (Meta Quest only) | Every app start on Meta Quest | The platform’s entitlement check, which Meta asks apps to run at launch | On the headset only; a yes/no answer from Meta | Not stored |
| Store account name — your Meta Quest username, PICO display name or Steam persona name — together with the name of your store (“Quest”, “PICO” or “Steam”) | Only with your opt-in (section 4): when you switch it on, and at every app start while it is on | Showing your name on the highscore list, marked with the store it belongs to (section 4) | On your device, which obtains it from your store (section 5), and on our server (section 6) | Device: in memory while the app runs, until you opt out, and in the app’s upload queue until the upload has succeeded. Server: until you opt out or request deletion |
| Milestone events — a level was entered for the first time, a level was solved for the first time, a tutorial step was completed, the tutorial was completed, the intro was completed; each with the app version, a timestamp and a random event ID | Always, each milestone once per installation | Learning where players get stuck and how far they come (section 3) | Our server (section 6) | Indefinitely. On the default tier they consist of the milestone, app version, timestamp and event ID only; with your opt-in they additionally carry your store account name, the name of your store and the installation ID until you opt out, which strips all three and keeps the count |
| Device model name (the headset model on Meta Quest and PICO, for example “Meta Quest 3”; on PC VR the model name of the computer as reported by the operating system) and system language of the device (for example “German”), each with the app version, a timestamp and a random event ID | Once per installation | Knowing which devices to optimize for and which languages to translate the game into (section 3) | Our server (section 6) | Indefinitely; shared by every device of that model or every player of that language, so they identify no one. Same opt-in rule as the milestone events |
| Installation ID — a random ID generated in the app, not derived from your device or account | Only with your opt-in (section 4) | Identifies your installation on our server: groups your progress snapshots and milestone events into your highscore entry (a rename keeps the entry; a second device gets its own) and names what the removal order deletes when you opt out | Our server; also on your device, in the app’s settings | Server: until you opt out or request deletion. Device: until you uninstall — kept after opting out so that a later opt-in reuses it |
| Progress snapshots — which levels you have solved, which tutorial steps you have completed, whether you finished the intro and the tutorial, your device model and system language | Only with your opt-in (section 4) | Computing your highscore points on the server; the rest lets us exclude our own test installations from the statistics | Our server | Until you opt out or request deletion |
| Consent record — that and when you opted in (section 4) | When you opt in | Proof of your consent (Art. 7(1) GDPR) | Our server | Until you opt out, when it is deleted together with the snapshots |
| Feedback messages — the text you type on the Feedback page, with the app version, the device model name, a timestamp and a random event ID; optionally the e-mail address you enter for a reply | Only when you press Send on the Feedback page | Reading what you tell us and, if you gave an address, answering you (section 9) | Our server (section 6) and the developer’s mailbox, to which the server forwards each message | Until we have dealt with the message, at most twelve months after receipt; earlier on request (section 9). A message carries no store account name or installation ID |
| Save file and settings — solved levels (your points are derived from them), current level, intro and tutorial progress; your settings | Always | Running the game | On your device only (the save file itself is never uploaded) | Until you uninstall the app. On Meta Quest, if you use Meta’s cloud backup, Meta may keep a copy of app data as part of that platform feature (Meta’s processing, section 5) |
| IP address, time and requested URL of each connection | Every connection to our server | Security and operation of the web server | Hosting provider’s access logs (section 6) | Rotated routinely by the hosting provider |
This table is complete: the first two rows are the data Tesserian receives from your store account, the others the data it collects itself. Tesserian contains no third-party advertising, analytics or tracking SDKs; all data collection is the one listed in this table, performed by our own code and our own server. We do not sell your data. Two parties process it besides us: our hosting provider, which stores our server’s data on our behalf (section 6), and the operator of your store as platform operator (section 5). Other players see only your highscore entry — name, store and score — and only if you have opted in (section 4).
To learn where players get stuck, how far they come, which devices to optimize for, and which languages to translate the game into, the game reports the milestone events listed in section 2 to our own server. The device model name (for example “Meta Quest 3”) is shared by every device of that type, and the system language (for example “German”) by every player of that locale; neither identifies a device. Each event contains the milestone itself, the app version, a timestamp, a running number and a random ID that identifies the event (so a retried upload is not counted twice). On the default tier the events carry no store account name, no store name and no installation ID, so we cannot tell which player sent them. This telemetry is always on.
In the game, on the Highscores page, you can switch Progress Sharing from Anonymous (default) to sharing with your name. Choosing it adds four items to what our server processes about you (all in the table in section 2): your store account name together with the name of your store, and the random installation ID, both attached to the milestone events from then on; a record of your consent; and progress snapshots. Tesserian reads your store account name at the moment you opt in, and again at every app start for as long as the setting stays on.
Purpose: displaying the highscore list inside the game. The list shows player name, store and score, and is visible to every player who has opted in themselves. Legal basis: your consent, Art. 6(1)(a) GDPR, given by opting in.
Withdrawal is one switch: setting Progress Sharing back to Anonymous withdraws your consent and deletes these four items from our server — see section 7.
How your store account name reaches Tesserian depends on your store. In every case the name is read on your device, and nothing is sent to our server before you opt in (section 4).
Meta Quest. The entitlement status reaches Tesserian through the Meta Platform SDK. Your Meta Quest username is requested from Meta’s servers with an access token that the SDK issues on the headset for your Meta account; the token is used for that request, is sent to Meta only and is not stored. The username comes from the platform feature “User Profile” in Meta’s Data Use Checkup for this app. Independently of this policy, Meta Platforms processes data as platform operator (store, entitlement check, providing your profile data to apps, cloud backup); see the Meta Privacy Policy.
PICO. Your PICO display name is obtained through the PICO Platform SDK on the headset, which asks the PICO system for the signed-in user. Independently of this policy, PICO processes data as platform operator (store, account, providing your profile data to apps); see the PICO Privacy Policy.
Steam. Your Steam persona name (the display name of your Steam account) is provided by the Steam client on your computer through the Steamworks API; Tesserian reads only the display name, never your Steam ID or login name. Independently of this policy, Valve processes data as platform operator (store, Steam client, account); see the Steam Privacy Policy.
Telemetry and highscores are handled by our own server software on shared hosting at
Alfahosting GmbH, Halle (Saale), Germany (eretrandre.org). IP addresses are stored
only in the hosting provider’s access logs, not in our telemetry database:
as with virtually every web server, those logs record the IP address, time, and requested URL of
each connection for security and operations (legal basis: legitimate interest,
Art. 6(1)(f) GDPR); they are managed and routinely rotated by the hosting provider and are not
used by us to identify players.
You can have all personal data Tesserian holds about you deleted at any time. No account, login or form is needed:
Milestone events sent on the default tier carry no store account name or installation ID, so we cannot find the events of a particular player and cannot delete them individually.
Where we process your personal data you have the rights of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20), and objection (Art. 21), as well as the right to withdraw consent at any time with effect for the future (Art. 7(3) — in Tesserian: the Progress-Sharing switch). You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). To exercise erasure, use one of the routes in section 7; for any other request, e-mail the controller (section 1).
The game’s Feedback page lets you write to us directly. When you press Send, the game queues your message together with the app version, the device model name, a timestamp and a random event ID, uploads it to our server (section 6), and the server forwards it to the developer’s mailbox. Nothing is sent before you press Send. A message never carries your store account name or installation ID, whatever your Progress-Sharing setting: the only personal data in it is what you type, and the e-mail address you may enter so that we can reply. The address is used for that reply alone and is never passed to anyone else.
Legal basis: answering a request you sent us, Art. 6(1)(b) GDPR. Messages are kept on the server and in the mailbox until we have dealt with them, at most twelve months after receipt. To have one deleted earlier, e-mail the controller (section 1) and quote the message or the address you gave.