Cookie Policy

Which cookies this site sets, what each one is for, and how to turn off the ones it does not need to run.

Draft for review. The structure, the headings and the dates are real, and the wording below is a first draft written from what this product has already decided rather than an operative term: it has not been through legal review and nothing here is in force. Where a fact is not settled yet, the section that needs it says so.
Last updated 18 August 2026Effective immediately for accounts opened from this date. Effective 18 October 2026 for accounts opened before it.What changed: this is the first version, so nothing changed and the date is the date it was published.Every later version keeps the one it replaced available.
Change your cookie choice

1. What this document decides

This says which files this product asks your browser to keep, what each one is for, and which of them you can refuse without the product breaking.

The choice is made in one place, the cookie banner, and the Cookie preferences link in the footer of every page reopens it. If you came here to change something, that is the link, and you do not have to read the rest first.

2. What a cookie is here

A cookie is a small named value your browser stores for a site and sends back on the next request. This product also uses local storage, which is the same idea without the sending, and a session value that never leaves the tab.

All three are covered here. A policy that talks only about cookies while the product also uses local storage is a policy written about the wrong thing.

3. The ones that have to be set

Three items cannot be refused while you are using the product. Your session, which is what keeps you signed in and keeps someone else out. Your theme, so the page does not change appearance on every visit. And your cookie answer, because the only way to remember that you refused is to store that you refused.

Each of those has its reason beside it above. Necessary with no reason next to it is a word doing the work of an argument.

4. The ones that measure how the product is used

One group is set only after you turn it on: which screens are reached, where a flow is abandoned, and how long a page takes to draw.

It is used to find the places the product is confusing or slow. No profile is built, nothing is joined to your account, and nothing follows you to another site. Refusing it leaves the product completely usable, and nothing in it is worse for having refused.

5. What we do not set

No advertising cookie is set. No cross-site tracking cookie is set. No cookie here is shared with an advertising network, a data broker or a social platform, and none is used to build a profile of you anywhere.

That is a commitment and not a description of this month. Setting one would be a change to this document with its own effective date and its own new choice, and section 9 says what happens then.

6. How to change your choice

Use the Cookie preferences link in the footer of any page. It reopens the same banner you saw first, with your current answer showing.

A change takes effect on the next page you load. Reject is one tap, exactly like Accept, and nothing is ticked for you in advance.

7. How long each kind lasts

The session ends when you close the tab. The theme and the cookie answer last one year. Measurement items last 90 days.

One lifetime for a whole page would be one promise covering two different things. When an item expires it is set again only if the answer that allowed it is still in force.

8. The ones a third party sets

One party outside this product can set anything in your browser through our pages: Transak, the card on-ramp inside Add funds, and only on that screen, and only if you open it.

That is the whole list. Adding to it is a change to this document with its own effective date.

9. Changes to this policy

We change this policy by publishing a new version with a date. The date at the top of this page is the version you are reading, and the previous version stays reachable.

One case resets your answer instead of carrying it forward: a new category, which you have not agreed to yet. Everything else keeps the answer you already gave.

10. How to reach us about this document

Write to legal@yonder.example for anything about cookies. It is not product support and it is read by a person, and a reply is sent within five working days.

If your question is really about what we hold about you rather than about what your browser stores, the Privacy Policy is the wider answer and it is linked at the foot of this page.

A question about this document goes to legal@yonder.example, which is not product support. A reply is sent within five working days.

Categories

Popular right now

Sign in or create account

You are about to place a bet. No crypto wallet required.

By continuing you agree to the Terms and Privacy Policy. Adding funds by card requires KYC; if you fund only with crypto you can connect a wallet instead.

Add funds

Card or crypto. Your USDC is held 1:1.

Amount to add
$
Pay with
The payment widget loads here (card to USDC)

Your USDC is held 1:1 - we do not lend or invest your funds.

Minimum $10. Card payments are converted to USDC via Transak. KYC is required to add funds by card; if you fund only with crypto you can connect a USDC wallet instead.

Step 1 of 3

Pick an event you follow

Every event asks one question, with a date and a named source. You see the odds, the one-line why and how it resolves before you put in a cent.

Step 2 of 3

Back YES or NO

The odds are a live price set by what people bet. Your payout is fixed at the price you took, so being early and right is worth more. One dollar minimum.

Step 3 of 3

Get paid when it resolves

It resolves against the source it named, and what was read is published with the result. Until then your money is held 1:1, never lent and never moved.