Powerplay rummy
Powerplay privacy: what this site collects and why
This editorial site collects only what the contact desk needs to reply. There are no user accounts, no comments and no payment processing on these pages.
Scope
A static magazine plus one chat
Public pages are static files. The contact widget can receive a name, a contact string and a message so the desk can reply. Server logs of incoming requests exist the way all hosts have logs. No analytics provider is named because this desk will not invent one.
Affiliate hop
One outbound commercial path
PLAY NOW leaves this site through /Login/playnow. After that hop, the destination's own rules apply. This privacy note does not control that destination.
Controller
Identity still being finalised
A finished privacy policy would name a controller and a contact route. Those details are being finalised and are not published yet. Until they are, treat the contact chat as the only on-site channel.
Rights
What you can ask
You can ask what message you sent through the chat. You can ask for a correction of editorial facts. You cannot ask this desk to delete an operator account. That button, if it exists, lives in the product.
Questions
Privacy questions
Do you sell data?
There is no data product to sell.
Do you take card numbers?
No.
Do you run accounts?
No.
What about cookies?
Hosting and the chat may set technical cookies. No marketing cookie list is published because none was verified as a named third party.
Where are terms?
On the terms note.
How do I reach you?
The contact chat.
What this desk will not invent
Licence numbers, bonus amounts, withdrawal minutes, user counts and testimonials are omitted when they are unpublished. Readers must be 18 or older. Online money games sit under the Promotion and Regulation of Online Gaming Act, 2025.
Logs
What a host sees without being nosy
Incoming requests usually include an address, a time and a user-agent. That is how servers work. This desk does not publish a retention day count because inventing one would be a second privacy failure.
Chat
What the widget can hold
A name, a contact string, a message. Do not paste IDs or OTPs into it. The widget is for editorial corrections. KYC does not belong there.
Third parties
After you hop
The play hop leaves this privacy note behind. Read the destination if you care what they store. We cannot summarise a policy we have not verified.
Host
What a server sees by existing
Incoming requests usually include an address, a time and a user-agent. That is how hosts work. A fake retention day count would be a second privacy failure, so none is printed.
The chat can hold a name, a contact string and a message. Do not paste OTPs or ID photos into it.
After the play hop, this note no longer governs. Read the destination if you care what they store.
Field diary
Scenes this note refuses to flatten
No accounts
Static files. No member area.
No cards
We do not take card numbers.
Logs exist
Hosts have logs. We will not invent a retention day.
Chat three
Name, contact string, message. That is the widget.
No OTP
Do not paste codes into the chat.
Hop leaves
After /Login/playnow this note no longer governs.
No named analytics
We will not invent a vendor.
Controller later
Controller identity is being finalised. The chat is the channel until then.
Delete operator
We cannot delete an operator account. See delete-account.
Ask
You can ask what you sent. You cannot ask us to unwind a deposit.