There is one way to reach this desk, and it is deliberately boring:
No contact form, no chat widget, no social accounts. A form would mean a third-party script on a site that currently loads nothing from anywhere else, and that trade is not worth it.
What is most useful to send
A code that worked. The most valuable message we can get. Include the exact string, the date and time you redeemed it, the platform you were on, and what the game gave you. We will redeem it ourselves before it goes in the vault, and the published row will carry the date of our test.
A measurement. Hatch times from a stopwatch, how far a belly meter fell over a known number of minutes, how long a complete dig cycle takes you. These are the numbers the whole site is currently missing, and two independent reports of the same figure is enough to turn a “to be announced” into a dated fact.
A correction. If a page here contradicts what you see in game, say which page and what you saw. Corrections are logged with a date on the update page rather than quietly patched.
What happens next
The address reaches the editor directly. Code reports get tested in game, usually on the same day’s check. Measurements are recorded and held until a second independent observation arrives or an editor reproduces it. Corrections are made as soon as they are confirmed.
What we do not want
Please do not send account credentials, personal details, or anything you would not want sitting in an inbox. We have no use for any of it. We also have no interest in link exchanges, guest posts, sponsored placements or affiliate arrangements — the site runs without advertising and intends to keep its recommendations unpurchasable.
Your email address is visible to us simply because you emailed us. It is not added to any list, not passed to anyone, and not used for anything except replying. The privacy page covers the rest.
Sources: this page describes our own process. See the editorial policy for how a reader report becomes a published fact.
Questions
Frequently asked questions
How do I report a working code?
Email the code, the date you redeemed it and what you received. We will redeem it on our own account before publishing, and the vault row will carry the date of our test.
Will you credit me?
If you want credit we will name you by whatever handle you give us in the update log entry. Say so in the message — the default is no attribution, because most people would rather not be named.
Do you reply to everything?
Not always individually, but every code report and every correction is read and acted on. Corrections show up dated on the update page, which is the real reply.