Reference

7dewa Privacy Policy for Your Account Data

Our 7dewa Privacy Policy shows how we handle the account details connected with Speed Blackjack, Sweet Bonanza 1000 and local wallet steps.

Clear data purposesWallet contextMobile access choicesPolicy request path

Explore Our Lobby Read FAQ

Your Privacy Choices Around Wallet Access

7dewa Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy describes how we receive, use and retain account data when you create an account, verify your phone or contact support about a wallet status. We may use account identifiers, contact details, device signals and transaction references to connect your session with services such

1
as DANA, OVO, GoPay, QRIS, bank transfer and virtual account. These records help us check that an account request and payment instruction match, without treating every device as a permanent identity. We use cookies or similar browser storage for session continuity, preferences and basic security checks.
2
We do not describe access as universal: availability depends on local law, and you should check your own eligibility before proceeding. If a policy update changes the purpose of data use, we will make the revised wording available through the account or policy path. You can
3
ask us to explain, correct or remove eligible data through the support route described below.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Get Clear Answers Before Account Access

Privacy questions should not slow down a phone verification or wallet check. We keep a direct support path for requests about your personal data, cookie choices and the records linked to your account. Open the support route from the account area and include the email or phone detail connected to your profile, so we can identify the request without asking for unnecessary payment credentials.

Team online

Data request

Ask us to explain the personal data connected with your account, why we use it and which service step prompted its collection. Include your account contact detail for a focused response.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, contact support through the account path. We can examine the linked record without asking you to send a wallet password or PIN.

Device concern

Tell us when a mobile browser keeps an old session, repeats a cookie prompt or blocks phone verification. We can direct the privacy request to the account step involved.

HOW WE HANDLE DATA

Practical Controls From Login To Retention

We keep this policy practical by connecting each data purpose to an account action you recognise.

Account details

When you open an account, we use the contact details and verification data you provide to create the profile, confirm…

Payment references

A DANA, OVO, GoPay or QRIS transaction reference can be linked to an account action such as a deposit check.

Cookie controls

Cookies and browser storage can keep a session active, remember a selected setting and support security checks.

Login protection

We examine session and device signals when an account is opened or accessed, helping us spot an unusual login pattern.

Retention approach

We retain account, support and transaction records only for the period needed for the stated service, security, dispute and legal…

Changes and contact

To correct a detail, ask about deletion or question a policy purpose, use the support path from your account area.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet is connected. We explain the practical route for data requests, device sessions, cookies and payment references, while keeping access wording tied to where local law permits.

It covers account details, phone verification, device and session signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps.

We use phone verification to confirm account ownership before access and to help address account requests. It also gives support a clearer way to match a privacy question with the correct profile.

Yes. The Privacy Policy applies when you use a phone or tablet browser, including session cookies and device signals used for continuity and security. Clearing browser storage can require another account check.

We may receive a transaction or status reference for a DANA or QRIS step, then link it to the relevant account action. We do not ask for your wallet PIN as part of a privacy request.

Yes. Use the support path in your account area and state which detail needs correction. We may ask for a matching account contact detail before changing the record, so the request reaches the right profile.

Retention depends on the purpose: account support, security checks, transaction tracing, disputes and legal duties can require different periods. We remove or handle records through the applicable retention process when they are no longer needed.

You can contact us through the account support path with your question about data handling or eligibility. Access depends on local law, so you should confirm that the service is available to you before proceeding.

7dewa Privacy Policy for Your Account Data

Get Clear Answers Before Account Access

Data request

Wallet record query

Device concern

Practical Controls From Login To Retention

Account details

Payment references

Cookie controls

Login protection

Retention approach

Changes and contact

Privacy Policy Answers For Your Account

01 What does the 7dewa Privacy Policy cover?

02 Why does 7dewa need my phone verification data?

03 Does the Privacy Policy apply on a mobile browser?

04 How are DANA and QRIS details handled?

05 Can I request a correction to my account data?

06 How long does 7dewa keep personal data?

07 Can I ask about Privacy Policy access in Indonesia?

Related Pages