Reference

Privacy Policy for your 4ddig account

4ddig places your account data, wallet records, device signals and cookie choices in one Privacy Policy, so you can see what we collect before you open an account.

Account data explainedCookie choicesUPI privacy contextPaytm and PhonePe records
4ddig Privacy Policy for your 4ddig account
CONTACT ROUTES

Three privacy contact paths

Privacy questions should reach the team that can check account records, wallet logs and cookie settings without moving you through unrelated queues.

Privacy email Use the privacy email when you want a copy of your account data, a correction, or a request about cookies. Include your registered email or mobile number so we can locate the right record.
Account helpdesk Contact account support when a privacy issue affects login, device access, UPI receipt matching, or withdrawal checks. We separate privacy handling from gameplay questions so your request reaches the right queue.
Data request form Send a structured request if you want deletion, restriction, or a change to stored profile details. We confirm identity first, then tell you what can be changed under applicable law.
POLICY CONTROLS

Six privacy controls we operate

Our privacy work sits close to account operations because a data choice can affect login, wallet checks, live table access and support records.

Account data

We collect profile details, login records, device signals and session history to run your account and protect access. Your password is handled through security controls, and support will never ask you to share it.

Payment privacy

UPI, Paytm, PhonePe and Google Pay records are used to match deposits, verify withdrawals and handle disputes. We store only the fields needed for account checks and payment reconciliation.

Cookie choices

Cookies help keep your session active, remember basic preferences and measure page use. You can adjust browser settings, though some account and security functions may not work correctly without required cookies.

Access controls

Only staff roles that need account, payment or support records can view those records. Access is logged, limited by task, and checked when privacy requests or account security alerts are raised.

Retention periods

We keep data for as long as needed to run the account, meet legal duties, resolve payment queries and protect against misuse. Older records are reduced or removed when retention reasons end.

Change requests

You can ask us to correct profile details, update contact data, restrict certain use, or delete records where the law allows. We confirm identity before acting on any account-level change.

Seven answers on your privacy choices

These answers focus only on privacy choices for your 4ddig account: what we collect, why we collect it, how payment records are handled, and how you can contact us. Some outcomes depend on identity checks, payment duties, fraud-prevention needs and local law. Where a request affects access, we explain the next step before making account changes.

We collect the details needed to create and protect your account, such as contact data, login records, device signals and verification status. We also keep support messages when they relate to privacy or account access.

Payment records help us confirm deposits, match withdrawals, answer wallet queries and investigate disputed transactions. We use only the data needed for those checks, such as transaction references, timing and account matching details.

Yes, you can contact us with the email or mobile number linked to your account. We may verify your identity first, then provide account data that can be shared under applicable law.

You can ask us to correct contact details, profile fields or other stored records. Deletion may be limited where we must keep payment, security or legal records, but we will explain the reason clearly.

Cookies help keep you signed in, remember simple settings and measure how pages work. Some cookies are needed for security and account flow, while optional analytics can be controlled through browser settings.

When you open games such as Turbo Blackjack, Fire Strike or Aviator, service partners may receive limited technical data needed to run the session. We do not send more account data than the service requires.

Use the privacy email, account helpdesk or data request form with your registered contact detail and the action you want. Avoid sending passwords or full payment identifiers in the first message.