← STRKWORLD

Privacy

This page is the early-access waitlist for STRKWORLD. It is deliberately small, and so is the amount it keeps about you. Last updated 11 October 2026.

What we store

When you submit the form, one row is written to our database:

• The public Starknet address your wallet reported, in a normalised form.
• The name of the wallet you connected, such as Ready or Xverse.
• The link to your X post, and the X handle taken from that link.
• That you clicked the Follow button. This is self-reported; we do not ask X.
• A review status, and a short note a reviewer may add.
• The time the row was created and the time it was last changed.
• A salted hash of the IP address the request arrived from — the IP joined with a secret salt and put through SHA-256. It exists only so a rate limit is possible and so a flood of signups from one place can be counted. The address itself is never written down anywhere, and the hash cannot be turned back into it without the salt, which is not in our code.

A row can also be created without the form: a reviewer may add a Starknet address by hand to grant early access to a wallet that never signed up. Such a row holds only that address, its review status, a note the reviewer may add, the times above, and a marker that it was added this way — no wallet name, no post link, no X handle, and no IP hash, because nothing of the sort was ever reported to us.

If you use the bridge on the Quantum Bunker page

The Quantum Bunker page has an optional bridge that swaps a token you hold into STRK on Starknet, through the NEAR Intents 1Click service. It moves funds only when you approve the transfer in your own wallet.

A completed bridge puts the receiving Starknet address on this waitlist, the same list the form writes to, marked as having come from the bridge and still reviewed by hand. Your browser sends us only the one-off deposit address 1Click gave you; we then ask 1Click ourselves what happened to it, and store:

• The Starknet address the STRK was delivered to, as a waitlist row — with a review status, a count of how many bridges it has completed, and when the last one completed. If that address is already on the list, nothing about its existing row changes but the count and that time.
• The name of the Starknet wallet you connected on that page, if you connected one.
• The one-off 1Click deposit address, and the memo if your chain needs one. It is kept so the same bridge is never counted twice and so one still in flight can be checked again.
• Which token you sent (its 1Click asset identifier, such as the USDC on Arbitrum one) and the amount, as text, plus the swap's status and the times we first saw and last checked it.
• The value of the swap as 1Click itself reports it: the US dollar value of what you sent, the US dollar value of the STRK delivered, and how much STRK that was. These are the figures 1Click returns with the swap's status, stored as numbers so the total bridged can be added up on our side. They are not a price we calculate and we store no price feed.
• Nothing else from the bridge. Not the address you sent from, not your refund address, not the transaction hash, and no IP hash — a bridge row is written from our own call to 1Click, not from your request.

A bridge that is refunded or fails puts nobody on the list. If you would rather not be on it, ask us to remove the entry as below.

If you sign in to the Drive

The Drive is a driving mini-game on a preview host. Signing in to it asks your wallet for one signature over a message our server composes, and nothing else — no transaction, no approval, and never a seed phrase, recovery phrase or private key.

Signing in stores your Starknet wallet address on this list, the same list the form writes to, with a review status and the times above, and a marker that it came from the Drive. If the address is already on the list, nothing about its existing row changes. No wallet name, no post link, no X handle and no IP hash are stored by a sign-in, because nothing of the sort is reported to us.

Playing then stores two kinds of thing about your driving, and only these two:

• Your top speed, in whole kilometres per hour, and when it was reached. The figure is measured by our own server from the positions your car publishes — we do not take the number your browser displays — and only the highest one is kept, so a later, slower run never replaces it. It is kept once for each character you drive, as well as one overall best for your entry: eight numbers at most, each the highest that character has reached, and which character a run was in is the one part of this your browser tells us.
• That you found the hidden bunker, when you found it, and which point on the world's grid it stands at. Written once, the first time; later visits change nothing.

We also keep a record of each of those measurements as it was made, so a figure on a row can be traced back to the run it came from. It holds the address, the figure, and the two times — no IP address, no IP hash, and nothing that identifies the connection it arrived on. These records are not kept indefinitely: we delete any that are more than thirty days old, and we keep at most the two hundred most recent for any one address. The top speed and the bunker find on your own entry are not affected by that — they are part of the entry, not part of this record.

Nothing else about a session is stored. Not where you drove, not how long for, not who else was in the room, and not anything your browser told us about itself. These figures are self-reported in the sense that matters: our server measures them rather than trusting your browser, but it cannot tell a person from a program, so they are a leaderboard and are never used to decide anything about your entry.

What we do not store

• No email address. There is no email field on this site.
• No tracking cookie, and no cookie at all from this site's own pages — the form, this page, the terms and the Quantum Bunker set none, for tracking or for anything else. There is one exception and it is not this site's: signing in to the game, or to the Drive, sets a session cookie. It is set by the game's server, not by these pages; it is marked HttpOnly and Secure, so no script can read it; it carries your wallet address, the times the session was issued and expires, and a random number naming that one sign-in, signed so none of it can be altered; and it exists for one reason, which is to avoid asking your wallet to sign again on every page you open. The game's expires after twelve hours and the Drive's after two, and neither is used to track anything.
• No analytics, no tracking pixel, no advertising tag, and no third-party script. The fonts are served from this site rather than from a font provider, so looking at this page sends your IP address to nobody but us.
• No request log. The server prints one line when it starts and nothing per visit, because a log of this page would be a list of who looked at it.
• No raw IP address, no browser user agent, no referring page.

Why we keep it

To run the early-access list: we review signups by hand and grant access one wallet at a time. A reviewer sees the row through a token-protected admin page. The game itself only ever asks whether a given address is approved, and the answer it gets is one bit.

The list is not sold, rented, published, or shared with anyone for their own purposes. It is kept while the early-access list is in use.

No keys, no funds

Connecting a wallet to the waitlist shares your public address and nothing else. The waitlist never asks you to sign a message or approve a transaction, never asks for a seed phrase, a recovery phrase or a private key, and never moves funds. It holds no keys and sends no transaction. Entering the game is the one place a signature is asked for: a wallet that has been granted early access signs one message to prove it is yours, which is a message and not a transaction — it moves no funds and approves no spending. Joining the waitlist never asks for it. The Quantum Bunker page has an optional bridge that does move funds, only when you approve the transfer in your own wallet. What a completed bridge stores here is set out above.

Removing your entry

Send a direct message to @strkworld on X with the address you submitted and we will delete the row. The same account is the contact for any question about this page or for a security report.