Reference

Privacy Policy for India accounts

Our Privacy Policy explains how we collect, use and protect the data linked to your stkamta account, from account opening details to UPI, Paytm and PhonePe records.

Account data useCookie choicesUPI record carePrivacy contact path
stkamta Privacy Policy for India accounts
DATA HELP

Contact routes for privacy requests

If you want to ask about your data, correct account details, or raise a privacy concern, contact us from the email linked to your account.

Account email Send your request from the email address attached to your account, and include your…
Live chat path Use live chat for quick privacy routing, such as asking where to send a…
Payment query For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction reference rather…
ACCOUNT SAFETY

Data care around Speed Baccarat sessions

Privacy controls sit beside account security, payment checks and session monitoring. When you open Speed Baccarat, India Gold, Football Strike or other rooms, we record technical data needed…

Data we collect

We collect account details, contact data, device signals, IP address, session logs, wallet records and support messages.

Why we use it

We use data to create your account, confirm sign-ins, process local payments, answer support requests, protect the wallet and comply…

Cookies and device data

Cookies help remember sign-in status, language choice and basic lobby behaviour.

Payment privacy

UPI, Paytm, PhonePe and Google Pay records are used to match your wallet activity with your account.

Retention approach

We keep account and payment data for as long as needed for service, legal, security and dispute reasons.

Request handling

You can ask to access, correct, restrict or delete data where the law allows.

Privacy questions before you join

These answers explain how our Privacy Policy works in daily account use, including payments, cookies, access requests and changes to your data. They are written to help you decide what to share before you open an account.

We ask for details needed to create and protect your account, such as contact data, sign-in credentials and checks required for access. Extra data may be needed for payments or security if your activity requires it.

We use local payment records to match deposits and withdrawals with your wallet, trace failed transactions and resolve disputes. We avoid asking for full screenshots when a transaction reference can handle the privacy task.

Yes, you can ask us to correct data linked to your account when it is inaccurate. We may request proof before changing sensitive details, especially when the change affects payments, access or account recovery.

Cookies help with sign-in, language settings, security checks and basic session flow. We do not need cookies to read private messages outside our service, and you can manage many cookie settings through your browser.

We may keep some records when legal duties, payment disputes, security checks or account investigations require retention. If deletion is limited, we explain the reason and reduce use where the law allows.

Your request is handled by staff who need access to answer it, verify your identity or apply the requested change. We do not share privacy requests across wider teams without a work reason.

We may update this Privacy Policy when our data practices, payment flows or legal duties change. The current version stays on this page, and major account-impacting changes may be shared through account contact channels.