Home / Privacy
Privacy note for casinoclubin.com readers
No member accounts. Logs, optional messages, a disclosed hop. Controller identity not yet published.
Privacy files fail by copying a SaaS template onto a static site. This one stays with what the lab actually does: serve pages, take optional messages, and offer a hop. Gaps in controller identity are stated. Retention months are not invented.
A privacy note for a site with no accounts
casinoclubin.com does not offer logins, comments, newsletters or payments. The data story is therefore small: request logs on a host, optional messages you send to the editorial form, and the fact of a sponsored hop if you choose it.
Small is not zero. Logs exist in hosting land. This note will not pretend otherwise.
It will also not invent a retention month we cannot defend.
What you type on purpose
The contact form asks for a name, a way to reach you, and a message. Use a channel you accept being stored by that form's operator stack.
Do not send passwords, OTP, card numbers or identity scans. We do not need them and should not hold them.
If you send them anyway, treat that as an accident and rotate the secret.
Logs we do not decorate
Incoming requests typically show IP, time, path and user agent to a host. This desk does not publish a full packet story because it does not operate a custom analytics palace.
No named third-party analytics vendor is claimed.
If that changes, this note must change on a date.
Cookies and local storage
A static site may still set cookies at the host or CDN layer. This desk does not describe a first-party marketing cookie we designed, because we did not.
Menu state is not a tracking graph.
If a future feature needs a cookie, name it here before it ships.
The affiliate hop
PLAY NOW is a first-party path that redirects. The destination will have its own privacy file. Read that file on that host. We do not reprint it.
We do not control what that host stores after the hop.
Skipping the hop skips that extra file.
Children
18+. This lab is not for children. If a child submitted the contact form, say so and we will delete that message if we can find it.
We cannot police every reader. We can refuse to dress the site as a toy.
Parents should use device tools.
Controller gap
A finished privacy file would name a controller and a postal address. Those details are being finalised and are not published. Inventing them would be a different kind of error.
The gap is uncomfortable and correct.
When they exist, they land here with a date.
Your asks
Access, correction, deletion of what this lab actually holds (usually a contact message). Use /contact/.
We cannot delete an operator wallet. We cannot delete a CDN log we do not control.
Honesty about scope is the whole note.
Questions readers send
Do you create user accounts?
No. This is a static editorial site.
What data do you see?
Ordinary server logs for requests, plus whatever you type into the editorial contact form. No complete inventory of hosting-provider logs is claimed.
Do you run a named analytics suite?
No named analytics vendor is claimed.
What happens if I follow PLAY NOW?
You leave this site. The destination's own rules apply. This lab does not control them.
Who is the controller?
Controller identity and a postal address are not yet published. That gap is stated rather than filled with a costume name.
How do I ask for a correction of personal data?
Use /contact/ and describe the URL and the data. If we do not hold it, we will say so.
If you need an operator privacy file, you are on the wrong host. If you need this lab's scope, it is small and should stay small.
Small is not zero, and zero would be a lie
Pages, optional messages, a hop. Host logs may exist.
That is small and not zero. Zero would be a lie.
A retention month we cannot defend would be a lie. A costume controller address would be a lie.
A named analytics palace we do not run would be a lie. Do not send secrets to the form.
Rotate them if you did. Children should not write here.
Operator wallets are another note. Hop destinations have other files.
If scope grows, this file grows on a date. Silent growth would be a costume.
Readers who wanted a software-company novel met a static site. The mismatch is honest.
We will not fill it with borrowed clauses from a product we are not. Small should stay small.
Help us keep it small by not using this host as a drop box.
Scope limits said one more time without a costume month
We serve pages. We may receive optional messages. We offer a hop. We do not run member accounts. That is the scope.
We do not claim a named analytics palace. We do not claim a retention month we cannot defend. We do not invent a controller address.
Host-level logs may exist. That possibility is why this file does not say zero data. Small is not zero.
The hop has another host's file. Read it there. We will not reprint it and get it wrong.
Children should not use the lab. If a child wrote to the form, tell us. Device tools still matter more.
Operator wallets are out of scope. Delete-account is the other note.
If scope grows, this file must grow on a date. Silent growth would be a costume.
If you needed a long software-company novel, the mismatch is the honest part of a static site.
What we ask you not to send
Passwords, OTP, CVV, UPI PIN, identity images, selfies for KYC, and other people's data. The editorial form is the wrong box for all of that.
If you sent a secret by accident, rotate it where it lives. Then tell us to delete the message if we can find it.
If a child submitted a message, say so. We will delete what we can find. Device tools still matter more than our form.
If you want an operator file deleted, that is the delete-account note, not this one. We cannot see operator wallets.
If you want a hop destination to delete data, that is their file. We do not reprint it and we do not control it.
Small scope stays small only if readers do not treat this host as a drop box for secrets.
What would force this note to change
A named analytics vendor. A first-party marketing cookie we designed. A published controller name and postal address. A newsletter. Any of those would require a dated rewrite.
Until they exist, claiming them would be a costume. Claiming a retention month we cannot defend would be a costume.
Host logs may exist outside our custom design. We will not pretend to operate a palace we do not operate.
If the contact stack changes vendors, the vendor's file matters. We should name that change when it happens.
If PLAY NOW redirect behaviour changes, the hop paragraph should move. The public HTML still must not print the external destination.
Readers who need a long software-company privacy novel are on a static site. The mismatch is the honest part.
Small, not zero, not a costume month
Pages, optional messages, a hop. Host logs may exist. That is small and not zero. We do not claim a named analytics palace, a retention month we cannot defend, or a costume controller address. Do not send secrets to the form. Rotate them if you did. Children should not write here. Operator wallets are another note. Hop destinations have other files.
If scope grows, this file grows on a date. Silent growth would be a costume. Readers who wanted a software-company novel met a static site. The mismatch is honest. Help us keep scope small by not using this host as a drop box.
Small is not zero. Do not send secrets. Do not invent a month. If scope grows, date the growth. A static site will not grow a software-company novel to look complete.
The contact form asks for a name, a way to reach you, and a message. Use a channel you accept being stored. Do not send passwords, OTP, card numbers or identity scans. If a child submitted a message, say so and we will delete what we can find.