OortWake and your information

What the game collects

Crash reports, and nothing else. There is no account and no sign-in. There are no advertisements, no analytics, no attribution or measurement service, and no social-network component. The game never reads your advertising ID.

There is also nowhere in the game to type anything — it has no text field at all — so there is no way for you to hand us a name, an address or a message except by writing to us yourself.

Crash reports

When the game crashes, Firebase Crashlytics (a Google service) sends us a report over an encrypted connection. It contains the crash itself and the technical context we need to fix it:

• the stack trace, including the native C++ frames;
• your device model, its Android version, and the version of the game;
• a short trail of what the game was doing — which screen, which mission, the sector seed, the ship tier, whether the run was local or online;
• a few technical keys we set ourselves: the processor architecture, the graphics driver name and version, and the screen size.

Deliberately not sent: your pilot callsign, the machine key described in section 04, and ANDROID_ID. We never attach a user identity to a report, so a crash cannot be traced back to a person. Crash reports are not used for advertising and not used to track you across apps or websites.

Why we collect them at all: OortWake is almost entirely C++, and a crash without a stack trace is a crash we cannot fix. This build has no in-game switch to turn reporting off. If you would rather not send them, uninstalling the game stops it.

What stays on your device

The game keeps one save file, profile.sfp, in its own private storage. It holds game state only: your credits and run tally, the weapons you own, your permanent upgrade ranks, your records, the hull you chose and how you assembled it, your helper-bot roster, and a pilot callsign the game invents on your device at first launch — something like PILOT-4C1A.

The game also unpacks its graphics data into its own cache folder the first time it runs. Both places are private to the app: no other app can read them, and Android deletes both when you uninstall OortWake.

If you have device backup switched on in your Android settings, Android may copy that save file into your own Google account backup so a new phone restores your progress. Android does that, under your account and your settings — we neither perform it nor have access to it, and you can switch it off in your system backup settings.

Device identifiers

At launch the game reads ANDROID_ID, an identifier Android generates separately for each app on each device. Its only purpose is to derive a one-way machine key for the online mode in section 06.

Because online play is not enabled in this release, that value is never hashed, never written to the save file and never transmitted. It exists in memory while the game is running and is gone when you close it.

The game does not read your advertising ID, IMEI, serial number, phone number, SIM details, contacts, calendar, photos or files.

Permissions and network

The game asks for one permission of its own, internet access, which crash reporting needs and which the online mode will need. It requests nothing at runtime: no microphone (every sound is synthesised by the game and only goes out), no camera, no location, no contacts, no calendar, and no access to your files.

This release has no game server configured. There is no Online entry on the menu, the game opens no game connection, and it plays in full with the device offline.

The online mode, which is not switched on

OortWake contains a shared-sector mode that is off in this release. It is described here so you know in advance what it will do, and so this page does not have to change the day it is switched on.

When a release is built with a server address, an Online entry appears on the menu. Nothing is sent until you choose it. If you do, the game would send to our game server your pilot callsign, a machine key derived from ANDROID_ID by a one-way hash (used only to bind a callsign to one device, so nobody else can fly it), the protocol version the game speaks, and — while you are in a round — your ship's live position and the results of the round, recorded against your callsign so progress carries between sessions.

As with any internet connection, the server would also see the IP address your device connects from. It would not receive your contacts, location, files or advertising identifiers, and there are no account credentials to send. Before online play opens to the public we will update this page with who operates that server, how long it keeps the data, and how to have it deleted.

Children

OortWake is not directed at children. It is a science-fiction combat game: you fly a spacecraft, mine asteroids and destroy hostile ships and drones. The fighting is between machines — there are no human characters, no blood, no sexual content, no profanity and no gambling. There is no chat and nothing players can post, so nobody can send your child anything through this game.

Sharing, keeping and deleting

We do not sell, rent or trade information about you, and nothing goes to advertisers or data brokers. Google processes crash reports on our behalf and holds them for a limited period before deleting them; nobody else receives them.

To have crash reports from your device removed, write to us with your device model and roughly when the crash happened and we will delete what we can identify. Your save file is yours: uninstalling the game removes it, and if you use Android backup, remove the app's backup through your Google account settings as well.

Under EU data protection law you have rights of access, correction, deletion, restriction, portability and objection, and the right to complain to a supervisory authority. In Finland that is the Office of the Data Protection Ombudsman (tietosuoja.fi).

Changes, and who is responsible

If a future release collects, sends or shares anything more — online play being the foreseeable case — this page is updated and its date changed before that release is published. The current version is always the one linked from the game's Google Play listing.

Metsaro GG, Tampere, Finland. Questions about any of this go to hello@metsaro.gg and a person will answer.