Rebellion Privacy Notice
Effective date: 5 October 2026 · Version 1.1
This notice supplements the Privacy Policy with what is specific to the game Rebellion. The data controller is APERTURESyndicate OÜ, Priisle tee 8, Lasnamäe linnaosa, Tallinn, Harju maakond, 13914, Estonia. Your rights, our legal bases in general and how to reach us are in the Privacy Policy; this page covers only what concerns the game.
We write these documents in good faith and keep them accurate to how the game actually works. They have not yet been reviewed by qualified Estonian legal counsel.
1. In short
- Single-player sends us nothing. Saves, your village, settings, your own music and logs live only on your computer.
- Online play needs very little: sign-in, invitations and squads in your APERTURESyndicate profile, an "in game" mark for your friends, and the relay's service log.
- The relay does not store the game — it forwards your squad's messages and forgets them.
- Your squad sees your nickname and avatar, not your handle or your email.
- The game has no telemetry, analytics, automatic crash reports, advertising or trackers.
2. On your computer
The data folder is %LOCALAPPDATA%\APERTURESyndicate\Rebellion Saves\. What it contains is
listed in Saves, Progress & Support. The personal
data in it:
- the sign-in token (
syndicate.session) — your account's refresh token, encrypted with a key bound to this computer. The key is used locally only and is never sent anywhere; - music settings — which Resonance playlists you added to the game, and their names;
- game logs (
logs\rebellion.logand the four before it) — these can contain the path to the game folder (often with your Windows user name), the file names of your music and of the tracks that played, and your squad members' nicknames.
The game streams Resonance music and never writes it to disk: the audio is held
in memory only while a track plays. We receive nothing from the data folder unless
you send us a file for support. Your own music in the music folder is never
uploaded.
If you played an early version, on first launch the new game copies your data from
the old folder %APPDATA%\Godot\app_userdata\Rebellion\ once and leaves it as a
backup; the old music cache is erased.
3. Signing in
Sign-in happens in your system browser on the APERTURESyndicate page; the
game never sees your password. The game asks for openid and profile access and
receives your account identifier, nickname and avatar address. Your handle and
email address are not given to it. The game asks for resonance:read access
separately, and only when you connect Resonance music.
- The access token lives for 15 minutes and only in the game's memory.
- The refresh token lives for 30 days, is replaced with a new one on every refresh, and is stored as an encrypted file (Section 2).
- Signing in creates a session on your account — with an IP address and a description of the client, like any sign-in (Data Retention Schedule, Section 3). It appears among the sessions in your account's security settings.
- "Sign out" in the game erases the stored token from your computer.
4. Friends, invitations and squads
This is stored in your APERTURESyndicate profile (the profile service):
- invitations — who invited whom, to which game, the status (pending, accepted, declined, closed), when it was created, answered and expires, and marks showing that the squad members are still in the game;
- the "in game" mark — while you are signed in and the game is open, it asks the server about your squad and invitations every three seconds; those requests set a mark that lasts about 20 seconds. Only your mutual friends see it, in the Rebellion squad list.
The game does not store a friends list — it is built from the mutual follows on your profile.
5. The relay and the network
Co-op runs through the relay rebellion.aperturesyndicate.com on our servers in
the EU, behind Cloudflare. The connection is encrypted (TLS).
What passes through it: players' input (position, aim, attacks), commands (buy, equip, build…), service messages and — from the host, on entering town or a floor — the host's whole world: the run save and the village with its name. The relay does not read or store any of it; rooms exist only in memory and disappear when the host leaves or the server restarts.
What goes into its log: that a room was opened, or a player joined, left or was refused — with the account identifier, the room number (which is the host's account identifier), the seat number and the close code. The log contains no message contents and no tokens.
What our web server and Cloudflare see: the IP address, the time and the request address — for a guest it includes the room number, that is, the host's account identifier. Cloudflare is listed in Data Processing & Sub-processors.
6. What other players receive
| Who | What |
|---|---|
| Friends in the squad list | Nickname, avatar, the "in game" mark |
| Members of your squad | Nickname, avatar, account identifier (the game needs it to match the squad; it is not shown in the interface), your actions in the shared world |
| Your guests, if you host | Your world: the run save and your village with its name |
Squad members do not exchange IP addresses while the game runs through the relay. Over a local network (currently the only way to play as a squad of three or four) the computers connect directly and see each other's addresses.
The game loads each squad member's avatar from our public storage, so the storage and the CDN see the IP address of that request.
7. Resonance and Audius
If you connected Resonance, the game receives your playlists and the audio of the tracks, and plays of catalogue tracks of 30 seconds or more are recorded in your Resonance listening history — just as in Resonance itself. Details: Rebellion & Resonance and the Resonance Privacy Addendum.
The game downloads open-catalogue tracks from Audius network nodes, and Audius sees your IP address — as described in Section 11 of the Resonance Privacy Addendum.
8. Legal bases
| Processing | Basis |
|---|---|
| Sign-in, invitations, squads, the relay, Resonance music | Contract — Art. 6(1)(b) GDPR: you ask for these features |
| Server and relay logs, limits, abuse protection | Legitimate interests — Art. 6(1)(f) GDPR: keeping the service secure and running |
| The "in game" mark for friends | Contract — Art. 6(1)(b) GDPR: it is how the squad list works |
9. Retention
| Data | How long |
|---|---|
| Files on your computer | Until you delete them |
| Invitations and squads | While the account exists; deleted with it |
| The "in game" mark | About 20 seconds after the game's last request |
| Relay rooms | While the host is in the game; never written to disk |
| Relay and web server logs | 30 days |
| A sign-in session, its IP address and client description | While the session is alive; the IP address and description are erased after 30 days |
10. Export and deletion
- Export. Settings → Privacy → Export everything on aperturesyndicate.com also exports your Rebellion invitations, together with the rest of your profile data.
- Deleting your account deletes invitations and squads (see
Deleting Your Account & Data). It does not touch the
files on your computer — we cannot reach them. To delete them, sign out in the
game and delete the data folder and the
musicfolder (Getting the Game & Updates, Section 7). - Your other rights — access, rectification, restriction, objection — work as in Sections 9–10 of the Privacy Policy; we answer within 30 days.
11. Children
An APERTURESyndicate account can be created from age 13; below the age of digital consent in your country, with a parent's consent (Section 12 of the Privacy Policy). We recommend the game for 16 and over — Content & Age Rating.
Contact
Questions about your data — [email protected], subject "GDPR request". Complaints to the supervisory authority — Andmekaitse Inspektsioon (Estonian Data Protection Inspectorate), https://www.aki.ee/en.
APERTURESyndicate OÜ · Registry code 17384111 · VAT EE102972654 · Priisle tee 8, Lasnamäe linnaosa, Tallinn, Harju maakond, 13914, Estonia
The English version is the controlling version; translations are provided for convenience.
Version history
- v1.1 — 2026-10-05 — The new data folder and the move from the old one; no music cache any more — Resonance streams; the
rebellion.loglog; a squad of three or four over a local network. - v1.0 — 2026-10-04 — First publication.