Emberfall — catch every ember in its own bowl
Emberfall keeps your scores and tells nobody, because there is nobody to tell.
No account, no sign-in, no cloud save, no advertising and no measurement. The app remembers your best scores, your longest combos and how you like it set up, writes that into its own private folder on the phone, and leaves it there. Nothing is transmitted and nothing reaches us.
What follows sets out the detail: what is stored, what the app is not permitted to reach, what Google sees because the game is distributed through Google Play, and what you can ask of us.
Emberfall is made and published by Pea Consult AS, registered in Norway at Skogliveien 17, 3047 Drammen, with Per Erik Abrahamsen answering for it.
Data protection law calls that role the controller. Here it is a role with very little to control, because the game hands us nothing about anybody. Where it means something is email, which has a section of its own below.
The address for anything on this page is spark@peaconsult.rest.
Three sorts of thing, none of which say anything about who you are:
Read that list again and notice what is absent from it: anything that would let a score be traced to a person. The file knows that a number was reached. It does not know whose thumb reached it, on what handset, or at what hour. Android seals each app's private folder away from every other app installed, and that sealed folder is the entirety of this game's memory.
This is the sentence the rest of the page rests on. Emberfall is built without the internet permission, and Android enforces that in the operating system rather than in our code: an app that does not hold it cannot open a connection at all. The claim is not that we choose not to send anything. It is that the game has no means of sending anything, and adding that means would be a visible change to the app's permissions.
There is likewise no permission for the camera, the microphone, your location, your contacts, your photos or your wider storage. A game about catching falling light has no use for any of them. The short buzz when an ember lands is the vibration motor, which requires no permission and reports to no one.
An arcade game with high scores is very nearly obliged, by convention, to offer a table of strangers to be ranked against. Emberfall declines. Nothing is ranked, nothing is published, nothing is compared with anyone, and you will not be invited to post a number anywhere. That is not an oversight waiting to be corrected in a later version — it is the reason the game never needs to learn your name, since a name is exactly what a ranking table demands first.
Your best run in Rush stands against one thing only: your previous best in Rush, on this phone.
There is no ad network in this build, no analytics library, no crash reporter, no attribution kit and no social sign-in. Nothing here is paid for by observing anyone.
Worth saying plainly for an arcade game, because bright, quick, colourful games are where advertising finds children most reliably. Since Emberfall shows no adverts and collects nothing from anybody, there is no profile to be built out of a child's play, no audience to be sold, and no reason to ask anyone's age, because no answer would change what the app does.
One thing happens above the app's head. If backup to Google Drive is switched on for your phone, Android may copy the small scores-and-settings file into your own Google account, alongside the backups of your other apps. That copy belongs to you, sits under Google's terms rather than ours, and is invisible to us — we have no account there to open and nothing to look at.
It is also the only way a shelf of records survives a new handset. Android's own settings turn it on or off, for everything at once or for this app alone.
Installing from Google Play is a transaction between you and Google, recorded under your account. What comes back to a developer afterwards is a console of totals: installs by country, which Android versions are in use, how the rating is drifting. There are no individual rows beneath those figures for us to open, and nothing in them touches a score or a combo.
Google's own part runs under Google's privacy policy at policies.google.com/privacy.
Everything lives in one folder, so there is a single thing to remove and nobody to write to. Uninstalling Emberfall takes the records, the settings and the unlocked twists with it. To keep the game but start from zero, Android's app settings will clear its storage, which returns every score and every combo to blank.
Both happen at once, neither can be undone, and neither needs anything from us, since there was never a second copy anywhere to delete.
Everything above describes data that never reaches us. This section is the exception, and it is a small one. Writing to us means we then hold an email address and a message, for as long as the conversation is alive and a while after it closes, on the chance that it reopens. After that the thread goes.
It is used to reply. It is not added to anything, not sold, not forwarded, and not used to send you something you did not ask for. Our ground for keeping it at all is the legitimate interest in answering correspondence. It cannot be tied back to your play, since the game holds no identifier that any email could be matched against — and if you would rather the exchange did not sit in a mailbox, say so and it will be removed.
The General Data Protection Regulation reaches Norway through personopplysningsloven, and it hands you a set of levers: find out what is held, get a copy of it, have it fixed, have it deleted, freeze its use, object to it outright, or take it elsewhere in a portable form. Most of those levers, pulled here, move nothing — there is nothing behind them to move. The one that does anything is aimed at the mailbox described just above.
Pull it at spark@peaconsult.rest; a reply is due inside thirty days and will arrive sooner. Complaints in Norway are heard by Datatilsynet (datatilsynet.no). Outside Norway but inside the EEA, the equivalent authority where you live will take one just as readily.
Only one date appears on this page, at the top, and it is the version you are reading. The order of events for a real change — collection of anything, a third-party component arriving, data crossing a border — is fixed: this page is rewritten first, the Data safety form in the Play Console is corrected in the same sitting, and only then does the release that caused it go out. Never the other way round.
Polishing a sentence does not count and earns nothing more than a fresher date.
Pea Consult AS
Skogliveien 17, 3047 Drammen, Norway
Responsible: Per Erik Abrahamsen
Du kan gjerne skrive på norsk.
© 2026