Server logs, one outbound click, no invented controller.

What arrives

A request hits the server. Logs can include an address, a time, and a path. No newsletter box sits on these pages.

The outbound click

PLAY NOW uses a first-party route that redirects. After that hop, another organisation's rules apply. Read them there.

What is not claimed

No named analytics vendor. No retention period we cannot defend. No controller identity that has not been published.

A static site is a small data story

There is no account table. There is no comment box. There is no newsletter. The remaining story is logs and one outbound hop. That smallness is the policy, not a missing chapter we forgot to write.

Logs as ordinary plumbing

Servers see addresses and paths. We do not claim a fancy retention cathedral. We also do not claim logs never exist. Honesty sits in the middle.

After you click PLAY NOW

You leave this publication's control. The destination has its own rules. Read them. This policy cannot speak for them.

Controller identity being finalised

A finished privacy page would name a controller and a contact. Those details are not published yet. Inventing them would be a new kind of lie. The gap stays visible.

Your correction rights in practice

If a page states a fact about you that is wrong, use the widget. If you want an operator to erase an account, that is delete-account and customer care, not this policy.

What a request looks like on a static host

A browser asks for a file. The server answers with HTML, CSS, a script, or an image. That exchange can leave an address, a time, a path, and a user-agent string in an ordinary log. There is no comment table behind it and no newsletter box waiting for an email. The smallness is the point of the policy, not a missing chapter.

People who expect a twenty-page controller annex will be disappointed. This publication does not run accounts. Inventing a retention cathedral would be a second kind of fiction. We describe the pipes that exist.

The outbound hop in slower words

PLAY NOW uses a first-party path on this domain, then a server redirect. After the hop, another organisation sees the request. Their cookies, their logs, their KYC, their wallet. This policy cannot speak for them and will not pretend to. Read their text after you leave, or do not leave.

The hop is also the disclosed money path. That belongs in about and in terms. Here it matters because it is the only intentional outbound click the chrome invites.

What we refuse to name without evidence

No analytics vendor is named because none is claimed. No six-month retention is named because none is defended. No data-protection officer is named because the controller identity is not published. Empty names are better than decorative names.

If those facts later exist, they should be written with a date. A future reader should be able to see when the gap closed.

Children, logs, and why 18+ is also a data line

The site is written for adults. It should not be used by children. Logs may still record a request from a device a child can reach. That is a household problem as much as a policy problem. Keep the bookmark off a shared child profile.

Corrections about you

If a sentence states a fact about a living person that is wrong, send the URL and the correction. Operator account erasure is a different job and lives on delete-account. Do not send passports to a writer to 'speed a policy'.

Third-party fonts and the browser

The type is loaded from Google Fonts with a small weight set. That request is made by your browser to a third party. If you block it, the site still reads in a system sans. Blocking is allowed. We will not pretend the font request does not exist.

What a future login would change

If this publication ever grew accounts, this policy would have to grow with them. It has not. Do not read today's static story as a promise that a future login would be designed. Read it as a description of what ships today.

How long this note stays honest

As long as the site stays static and the outbound hop stays the only commercial door. If either fact changes, the policy is stale the same day.

Fonts, logs, and other quiet third parties

Your browser may call Google Fonts for Manrope. That is a third-party request. Blocking it still leaves the site readable. We will not pretend the call does not happen.

Cloudflare may sit in front of the host. That is infrastructure, not an analytics product we named. We do not claim a dashboard we do not have.

If accounts ever appear

This policy would have to grow. It has not. Do not read today's static story as a design for a future login. Read it as a description of what ships now.

A future login that reused this thin policy would be a failure. Write that down so a future editor cannot 'save time'.

Your correction, not your passport

Send a URL and a wrong line. Do not send a passport to prove you care. We should not hold it and we cannot complete KYC.

Operator erasure lives on delete-account. Different building.

Children and shared profiles

The writing is for adults. A child-profile bookmark is a household mistake. Logs may still record the request. Keep the bookmark off that profile.

18+ is a data line as well as a legal line.

How long the small story stays true

As long as the site stays static and the hop stays the only commercial door. If either changes, the policy is stale the same day.

Stale policies are worse than short ones. Short and true beats long and decorative.

What we will not add for symmetry

A fake officer, a fake postal box, a fake six-month clock. Symmetry is how privacy pages become fiction.

Empty controller identity is ugly and correct until it is published.

After you leave through PLAY NOW

Their rules apply. Read them. Come back here only for our sentences, not for their wallet.

We cannot un-click the hop for you.

Small and true

Logs and one hop. No accounts. No newsletter. If that feels too small to be a policy, good. Small policies that match the pipes beat large policies that invent pipes.

Third parties we will name when we must

Fonts. Maybe a CDN. We will not name an analytics vendor we do not use. We will not name a controller we have not published. Naming for symmetry is fiction.

Stale the same day

If accounts appear or the hop changes, this note is stale immediately. A future editor who reuses it to save time is failing in a way we already wrote down.

Passports are not proof of care

Do not send them here. We should not hold them. Operator KYC is a different building. Corrections about our sentences need a URL, not a document.

After the hop

Their policy, their wallet, their KYC. Come back here only for our sentences. We cannot un-click for you and we will not pretend we can.

Match the pipes

Small pipes, small policy. Invented officer names would be larger and falser. Wait for publication of a controller, then date it.

Do not send documents here

URL and wrong line only. Passports belong to operator KYC, not to a writer.