Reference

Open kinghills privacy terms with clarity

kinghills Privacy Policy explains what account data we collect when you open the lobby, verify your profile, use cookies, or pay through UPI, Paytm, PhonePe and Google Pay.

Account data useCookie choicesUPI recordsPrivacy requests
Explore Lobby Read FAQ
kinghills Open kinghills privacy terms with clarity
CONTACT ROUTES

Check privacy contact paths before changes

Privacy questions often need context, so we keep contact paths separate from lobby support.

Privacy email Write to our privacy desk from the email on your account.
Chat handoff Use live chat only to ask where a privacy request should go.
Document checks If we need proof that the request is yours, we ask for a limited…
HANDLING STEPS

Browse our data handling steps

We write this policy around the account moments where data is created: joining, logging in, setting cookies, adding wallet funds, requesting a payout, and speaking with support.

Data we collect

We collect data you provide directly, such as name, mobile number, email, date of birth, KYC files and payment references.

Cookie controls

Cookies help us keep you signed in, remember language choices and measure page errors.

Account security

Wallet and profile changes use checks such as one-time codes, device checks and unusual activity alerts.

Retention periods

We keep account records only for business, security and legal needs, then delete or anonymise them when retention is no…

Partner access

Service partners may process hosting, analytics, payment routing, identity checks or support tools for us.

Your requests

You can ask for a copy, correction, deletion or restriction of your personal data where the law gives that right.

Discover privacy answers before you join

These answers explain the privacy choices you can make before and after you join. They focus on account data, cookies, payment references and request handling on kinghills.club. If your question involves access to the service itself, remember that eligibility depends on local law and is available where local law permits. Keep your request narrow and we can answer faster without asking for extra documents.

We collect the details you submit, such as name, mobile number, email, date of birth, password data and KYC files. We also record sign-in logs, device signals and security events tied to your account.

We store payment references, transaction status, amount, time and wallet provider labels so we can match payments with your account. We do not need your full banking password or UPI PIN.

Cookies keep your session active, remember basic preferences and help us see page errors. If you clear cookies, some sign-in or verification steps may repeat because the browser no longer holds the session token.

Yes. Send the correction request from your linked email or mobile number and point to the record that is wrong. We verify the request before updating profile, KYC or payment records.

You can request deletion where law allows. We remove or anonymise data that is no longer needed, but some records may stay for tax, fraud prevention, dispute handling or other legal duties.

Only teams and partners who need the data for account operation, security, support, payments, analytics or legal duties receive it. We do not sell your personal data to third parties.

We keep request logs long enough to prove how we handled the privacy action and to meet legal record needs. When that need ends, we delete or anonymise the log.

Related Pages

FAQ About Us Crazy Fruits Space Wars