Something not working?

We check three things at once and each can reject a receipt on its own. First: you had to press „I am at the machine" at that machine beforehand - without a reported visit there is nothing to match against. Second: the printing time on the receipt must fall within the window of that visit; the window lasts half an hour, with a ten-minute tolerance for a machine clock that is set wrong. Third: the location read at the moment presence was reported must lie within the Zone radius.

The message always says which condition failed - it is worth reading before you take a second photograph of the same receipt.

Yes, up to a day after the presence window closes. The visit is identified by the printing time on the receipt, so the app does not have to remember anything between the button press and the photograph - you can close the app or switch the phone off in the meantime. After a day the receipt is lost for the game; you collect the deposit in the shop regardless.

We read the receipt from the photograph, so everything depends on the framing. Fit the whole receipt in the frame together with its bottom part - that is where the printing time usually is, and without it there is no way to match the visit - and make sure the barcode is sharp and fully visible.

Flatten the receipt, put it on a dark, matt surface and position yourself so that a lamp does not reflect off the paper. When the read is uncertain we ask for a better photograph rather than guessing the number of items - wrongly awarded Charge would be worse than taking another photo.

No. We remember the barcode hash and a second identical one is rejected - even when the photograph is different. The hash deletes itself after seven days, because a receipt older than a day would fail the time condition anyway.

That is normal and usually breaks nothing. Biedronka, Lidl, Dino and Netto print the address of their own head office on the receipt, identical across Poland, while Stokrotka and MPM print none at all - the receipt simply does not say where the machine stood. So we check the address only where it is genuine, and it is never the only condition.

If you still get a message about a mismatched address, it usually means a different machine is selected on the map than the one you are standing at.

Nothing. The photograph passes through server memory and is gone - there is no photo store and no job deleting them, because there is nothing to delete. All that stays is the barcode hash, for seven days, so the same receipt cannot be settled again. Details: privacy policy.

On the map press „Add your machine", move the map so the crosshair sits on the machine, correct the suggested address and drop a pin. That is only half the way: until you stand at that machine and press „I am at the machine", the pin is visible to you alone.

Because nobody has stood at it yet. A pin without confirmed presence is a hypothesis, not a machine - it lives one day and deletes itself, and the countdown is shown in its panel. A map full of non-existent machines is worse than an empty map: somebody would walk with a bag of bottles to an address where nothing stands.

A discovery confirmed by presence pays 60 Amber, 60 Spark and 60 Prism. Three discoveries a day are paid - the fourth and further ones enter the shared map normally, but the payout is then deferred, not cancelled: just come back to that machine on another day and press „I am at the machine" again. The map matters more than Charge, so the machine enters regardless of the limit.

It is worth going back there with bottles too: the first receipt settled at a machine you pointed out yourself counts one and a half times.

Presence proves the machine stands there. A receipt proves it accepts containers - and only that promotes a Zone to confirmed. That is why a machine can already be on the shared map and still be marked as reported: nobody has settled a receipt at it yet.

Tap the machine on the map - the Zone panel says how many Reactivators stand at it and leads to the window where you join. Joining itself needs no location permission and costs not one unit of Charge; the only condition is that the machine is on the shared map.

You are in one gang at a time, and moving to another is possible once a week. There is no separate „leave the gang", only a change. Everything a gang really gives rests on receipts settled at that machine - joining by itself gives nothing.

That is not a fault to repair but an error on the map - report it in the same window as a fault, choosing the „gone" kind. A machine that does not exist does not come back to the map after a repair, so we treat such reports separately.

That is how it should be. A new Reactivator gets a sealed Capsule, and only a bottle opens it: every settled receipt cracks it, the fifth tears it apart. A Sparkling cannot be bought, won or asked for - this is the one place in the game with no shortcut at all.

Before hatching nothing drains and there is nothing to feed, which is why there are no energy bars above the Capsule. A receipt sent for review cracks it too.

Charge has daily, diminishing returns. Up to the twentieth item in a day we count the full rate, from the twenty-first to the fortieth - half, and above forty an item does not enter the game at all. A bag of thirty bottles gives 250 instead of 300 and is still worth bringing.

The result screen says this in two separate sentences, because „counted at half rate" and „did not count at all" are two different messages. You collect the deposit for every container returned in the shop as usual - the limit applies to the game alone.

No. A receipt flagged as suspicious gets Charge normally and cracks the Capsule normally - the flag is for us, not for you. Soft conditions only flag; we reject only receipts that fail the hard conditions (time outside the visit window, location outside the Zone, a repeated barcode), and then the message says so outright.

Energy drains by itself, at 4 units an hour - a freshly hatched Sparkling has six days from full to empty. Every level enlarges the tank, not the appetite, so levelling up never raises the upkeep bill.

Only the charger in the care column raises it: you pick a kind of Charge, attach the clamps and pay only for the current that actually went in. The Sparkling will eat a container from the pile on the arena, but there is no energy in that - feeding is play, not fuel. A dimmed Sparkling does not enter mini-games, and that is the one place where energy really costs something.

Never. With empty Charge it dims and waits - one receipt and the charger are enough to bring it back. In duels the stake is Charge, never the creature itself.

Four statistics grow through training in mini-games and change the machine parameters, they do not multiply the score; equipped gear adds a bonus to them. A mini-game never gives Charge - training is exactly what it pays in.

Those same four numbers go onto the Sparkling card in DepositMonsters Tycoon - a separate game on Roblox where you rebuild a sorting plant and your Sparkling works at the machines: Strength at the press, Reflex at the chutes, Focus at sorting, and Stability earns while you are away. The Sparkling does not grow on Roblox - it grows only from bottles. Accounts are linked with a single-use pairing code generated in our app and typed in on the other side; the account code you give friends for challenges is not used for pairing and never will be. DepositMonsters Tycoon is under construction and cannot be played today.

Any of them, but one thing matters: Google or Apple sign-in cannot be attached later to an account created with a password. That is not a bug but a safeguard - otherwise someone would create an account on your e-mail address and wait for you to sign in with Google straight into an account whose password they know. If you intend to sign in with Google or Apple, start with them.

The licence belongs to the account in our database, not to the phone or to the store account. Sign in with the same account and the adverts will disappear by themselves. If they do not, press „Restore purchase" in Settings - the phone then sends us the store receipts, because we hold only their hash and so have nothing to ask about ourselves. One purchase unlocks one account.

A refund extinguishes the licence and the adverts come back - Settings says so outright. The licence can be bought again. Ask for the refund itself in Google Play or the App Store, because the store handled the payment, not us.

We show full-screen adverts in three places and only there: after the Sorting round summary, after the Launcher verdict and when leaving the games screen. There are none on the whole path at the machine, at the hatching of the Capsule, during care routines, on the map while looking for a machine, or at the start of the game - a new player will not see a single advert until their Sparkling hatches. There is no banner and there will not be one.

You open the consent form in Settings, the „Advertising consents" row. No advert and no money ever gives Charge - the licence buys quiet, not an advantage.

We send two kinds and only two: „your turn" in an arranged duel and „Charge running out", at most once a day. We ask for the system permission only at the first arranged duel, not at app start. Nothing arrives between 22:00 and 08:00 your time - a notification from those hours waits until morning instead of being lost.

You can mute them in Settings. Turning them back on has to be done in your phone settings: once the system permission is withdrawn, the app has no way to restore it.

From the app: Settings, „Delete account", two confirmation questions. Deletion wipes the account, the Sparkling and the whole history, and cannot be undone; the ad-free licence does not transfer to a new account. The route from outside the app, what remains after deletion and how long it takes are described on a separate page: account deletion.

The full list is in the privacy policy. Three things are worth knowing straight away: we do not store receipt photographs at all, all that stays from a receipt is the barcode hash for seven days, and we read your location once, after you press „I am at the machine". There is no background proximity detection and deliberately never will be - it would require „always" permission.