In short: Tesserian collects and processes the following data about you: your Meta User Profile (username) through the Meta Platform SDK (the Meta platform feature “User Profile”), which also confirms that your account owns the game; anonymous milestone events about your game progress plus, once per installation, your headset model and system language; and — only if you opt in to “Progress Sharing — With Quest Name” — your username, a random installation ID, your consent record and progress snapshots for the highscore list; plus your save file on the headset and the usual web-server access logs. Section 2 lists every item with its purpose; section 7 explains how to have your data deleted, in the app with one switch or by e-mail.
The controller responsible for data processing in connection with the VR game Tesserian (Meta Quest) 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).
| Data | When | Purpose | Where it is processed and stored | Retention |
|---|---|---|---|---|
| Entitlement status — whether your Meta account owns Tesserian | Every app start | The platform’s entitlement check, which Meta asks apps to run at launch and which precedes the profile lookup below. Tesserian only logs a failure. | On the headset only; a yes/no answer from Meta | Not stored |
| Meta User Profile — your Meta Quest username (Meta platform feature “User Profile”) | Every app start | Showing your name on the highscore list, if you have opted in (section 4) | On the headset; sent to our server only with your opt-in | Headset: in memory while the app runs and, with your opt-in, 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 username and installation ID until you opt out, which strips both and keeps the count |
| Headset model name (for example “Meta Quest 3”) and system language of the headset (for example “German”), each with the app version, a timestamp and a random event ID | Once per installation | Knowing which headsets to optimize for and which languages to translate the game into (section 3) | Our server (section 6) | Indefinitely; shared by every headset 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 headset gets its own) and names what the removal order deletes when you opt out | Our server; also on the headset, in the app’s settings | Server: until you opt out or request deletion. Headset: until you uninstall — kept after opting out so that a later opt-in reuses it |
| Progress snapshots — which levels you have solved | Only with your opt-in (section 4) | Computing your highscore points on the server | Our server | Until you opt out or request deletion |
| Consent record — that and when you chose “With Quest Name” | 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 |
| 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 the headset only (the save file itself is never uploaded) | Until you uninstall the app. 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 Meta 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 Meta as platform operator (section 5). Other players see only your highscore entry — name and score — and only if you have opted in (section 4).
To learn where players get stuck, how far they come, which headsets 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 headset model name (for example “Meta Quest 3”) is shared by every headset 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 username or 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 With Quest Name. Choosing it adds four items to what our server processes about you (all in the table in section 2): your Meta Quest username and the random installation ID, both attached to the milestone events from then on, a record of your consent, and progress snapshots.
Purpose: displaying the highscore list inside the game. The list shows player name and score and is visible to every player who has opted in themselves. Legal basis: your consent, Art. 6(1)(a) GDPR, given by choosing “With Quest Name”.
Withdrawal is one switch: setting Progress Sharing back to Anonymous withdraws your consent and deletes these four items from our server — see section 7.
The entitlement status and your Meta User Profile reach Tesserian through the Meta Platform SDK; the latter is the platform feature “User Profile” in Meta’s Data Use Checkup for this app. What is read, why, and for how long is in the table in section 2.
Independently of this policy, Meta Platforms processes data as platform operator (store, entitlement check, providing your profile data to apps). For this, see the Meta 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 username 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).