A personal project, offered as it is. The parts that describe how the system behaves are accurate; the parts a lawyer has to write are marked as missing rather than filled in with something plausible.
This document is available in English only. The English text is the one that governs. If it is ever translated, the translation is offered as a convenience and the English still governs.
Last updated 30 August 2026
ROK is a personal project. It is offered as it is, with no guarantee that it works, that it stays up, or that a hunt you started can be finished. Codes get rained on, tokens get pocketed by strangers, servers fall over, and seasons end.
Using it means accepting that. If something matters to you — a trip planned around a hunt, a prize you want — do not plan around this holding together.
Scanning a code and walking a hunt needs no account and never will. That is a rule about the product and not a temporary state.
An account is the price of four things: keeping a token, holding a completion record, opening hints, and putting a picture on a hunt’s wall. A picture on a public page is signed, and a guest has no name to sign it with.
A station is a physical thing in a real place. Reaching it may mean roads, traffic, heat, weather, stairs, water, animals, opening hours and other people’s property. None of that is under our control and none of it is checked by us.
Judge for yourself whether a place is safe to go to and safe to be at. Do not trespass, do not climb anything, do not go anywhere at a time or in a condition you would not otherwise go. Do not scan while riding or driving. If a place looks wrong, leave; no hunt is worth it.
Hunts are made by other people. We do not visit the places in them and we do not inspect them.
Going to a station is your own decision and your own risk, and nothing here is an assurance that a place is safe.
On a collect hunt the physical object is the scarcity. A token is claimed exactly once, by whoever gets there first, and it then leaves the hunt. There is no reservation, no queue and no second copy.
A hunt runs for a period. When it ends, tokens nobody found are released back to the pool and the codes on them are retired — so a code you scan afterwards resolves to nothing at all, even though the object may still be sitting where it was hidden. That is deliberate: the paper insert is replaceable and the code is reissued for a later season.
A hunt with no closing date does not end on its own, and a hunt’s owner may close it at any time.
A photograph of a hiding place ruins a hunt for everybody who comes after, and no software can see that in a picture. Do not publish where a token is hidden — not on a hunt’s wall, not anywhere else.
On a hunt where the stations are plaques rather than hidden objects, the thing that can be spoiled is the answer. Do not post a photograph you can read a puzzle’s answer off, and do not publish the answers.
Do not try to find codes by guessing at them, scanning the range, or automating anything against the API. Codes are random and opaque for exactly this reason. Rate limits exist and evading them is not on.
Anybody with an account can author a hunt: its name, its story, its stations, its puzzles, its photographs. That content belongs to whoever wrote it. It is not ours, we did not write it, and we do not check it before it appears.
An author chooses whether their hunt is listed publicly or reachable only by a link, and whether they approve each player. There is no platform-level review of listed hunts today. If you find one that should not be there, the feedback form on the help page is the way to say so.
If you author a hunt: what you put in it has to be yours to put there, it has to be legal, and the places you send people have to be places they may go. A hunt can be closed.
A post, a caption, a photograph on a wall: you keep it. What you give us is permission to store it and to show it on this platform where you chose to put it, for as long as it is there.
Two things are permanent by design, and it is better to know before you write them. A claimed token gets one post, by whoever kept it, on that object’s own page — one post, editable for fifteen minutes after publishing and then fixed, with no way for you to delete or replace it afterwards. We can take one down where it breaks the rules, and nobody else can. And the event log behind a hunt is append-only: nothing in it is deleted.
A picture on a hunt’s wall is different. You may take your own down at any time, and you may rewrite your own caption at any time. Taking one down removes it from the wall for everybody — but the file itself stays where it was served from, so anybody already holding that link keeps it. Hidden is not unpublished.
A hunt’s owner may take any picture off that hunt’s wall, including yours, without asking. They are the person a venue complains to, so they are the person who can act.
They may not touch your words. Rewriting somebody’s caption under their own name is the platform speaking as them, so the owner can remove a picture and cannot edit it.
Anybody reading a wall can report a picture, and can block whoever posted it. Reporting sends it to the person who runs ROK! and removes nothing by itself; blocking removes that person’s pictures from your view and yours from theirs, on every hunt, immediately and without telling them. The EULA sets out both in full, along with the same two controls on a claimed token’s post.
There is a cap of six live pictures per person per hunt. Taking one of your own down makes room for another.
Nothing on a wall replies to anything. There are no comments, no threads and no reply counts, and that is a design decision rather than a feature that has not shipped yet.
Some hunts end in something to collect at a venue’s counter, redeemed with a one-time code. The venue hands it over, not us, and what is behind the counter is what is behind the counter — a reward can run out, and a venue can close or change its mind.
A redemption code is single-use and belongs to the run that earned it. Do not sell it, and do not expect a second one.
You can close your account whenever you like, from the profile screen on either client. Read what that does in the privacy policy first, because it is not an erasure: your identity links, your name, your avatar and your account details go and every session is revoked, your wall pictures come down, and your runs, claims, rewards and posts stay without your name on them.
Signing in again afterwards makes a new, empty account. There is no way back to the old one.
We can suspend or close an account that is being used to spoil hunts, to abuse the API, or to publish something that should not be published.
These terms can change; the date at the top is when they last did.
The whole thing can stop. It is one person’s project on one rented server, and there is no promise that it outlives the interest in running it. If it stops, the hunts, the walls and the posts stop with it — the word "permanent" everywhere in this document means for as long as this is running, and it cannot mean more than that.
ROK! is made and run by Vandeth THO. It is one person’s project rather than a company’s, which is why this document says "one person" wherever it would otherwise say "we".
The way to reach that person about anything in these terms is the feedback form on the help page, at rokadventure.com/help. It goes to one inbox and it is read. Allow a few days.