Reference

7nsoft Privacy Policy For Your Account

7nsoft Privacy Policy explains what we collect when you open an account, sign in from a phone, or check wallet activity through DANA, OVO, GoPay and QRIS.

Account detailsWallet statusDevice activityPolicy requests
7nsoft 7nsoft Privacy Policy For Your Account
HELP WITH PRIVACY

Where To Ask About Your Data

A clear support route matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Start from the support path linked to your account and include the phone or email used for access, the relevant date and the type of request. Do not send a full password or wallet PIN. We use the details you provide to locate the right record and keep the reply focused on your privacy question.

Team online

Privacy request

Use the account support path to ask what personal data we hold, why it is used or how a particular record connects with your 7nsoft account. Include your registered contact detail so we can check the request without asking for a password or wallet PIN.

Account correction

If your phone verification detail or contact record is wrong, tell us which field needs attention and when you noticed it. We may ask for an account step that confirms ownership before changing data connected with access to Baccarat, Egypt Book of Mystery or other lobby areas.

Wallet question

For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, share the transaction date and visible reference only. We can explain the stored payment status while avoiding requests for your wallet PIN, full bank credentials or unrelated account details.

DATA HANDLING DETAILS

How We Keep Policy Promises Practical

Privacy work is part of the account flow, not a separate page you have to decipher after a problem.

Account collection

We collect the details needed to create and maintain your account, including contact information and phone verification status. When you move from sign-in to the lobby, these records help us connect the session to the correct account without treating every device visit as a new registration.

Payment records

A wallet reference can show that a DANA, OVO, GoPay or QRIS request was submitted, matched or left pending. Bank transfer and virtual account details support the same reconciliation step. We use payment records to resolve status questions, not to request your private wallet credential.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, language choices and the page you opened on mobile or desktop. They help you return to the same account path, including the route from account access to Baccarat or Counter-Strike 2, and can be managed through your browser settings.

Security signals

We may examine device, connection and sign-in signals when activity looks unusual, such as repeated failed access attempts or a sudden change from a familiar phone. This supports account protection and may lead to an ownership check before we change contact details or discuss wallet records.

Retention choices

We keep personal data for as long as it serves account operation, payment reconciliation, security checks or a legal requirement that applies where local law permits. When you ask about deletion or restriction, we assess the request against those needs and tell you which records can be changed.

Requesting changes

To request a copy, correction or permitted removal of your data, contact us through the account support path with your registered contact detail and a precise request. We may verify ownership first, then confirm the action, any records we must retain and the reason for that limit.

Privacy Policy Answers For 7nsoft

These Privacy Policy answers address the account questions you are most likely to have before opening access from Indonesia. We explain the data connected with sign-in, phone verification, device sessions and local wallet activity in direct terms. If your situation is not covered, use the account support path and identify the specific record or request. Eligibility and access depends on local law, so we assess requests against the rules that apply to your location.

The Privacy Policy covers contact details, phone verification status, sign-in records and security signals connected with your account. We use them to provide account access, check unusual activity, match support requests and maintain the requested session on your phone or desktop where local law permits.

Yes. The Privacy Policy covers payment references and status records created when you use DANA, OVO, GoPay or QRIS. We may also retain matching details for bank transfer and virtual account requests so support can identify a pending or completed cashier record without receiving your wallet PIN.

Use the support path linked to your account and ask for a data copy. Include your registered phone or email and describe the records you want, such as sign-in activity, phone verification or QRIS status. We may verify ownership before sharing account-linked data.

You can ask us to correct an inaccurate contact or account detail through support. State the field that needs changing and provide the current detail. We may request an ownership check before making the edit, especially when the change could affect sign-in, phone verification or wallet records.

Cookies and session tools can retain sign-in state, language choices and the page path you opened. They help keep your account route consistent when you move from mobile access to the lobby, including pages for Bingo or Royal Fishing. Browser settings can limit or remove these tools.

We retain data while it is needed for account operation, payment matching, security checks, support or a legal requirement that applies where local law permits. If you request removal, we assess each record and explain what can be deleted, what must remain and why.

Start with the support route inside your account and label the request as a Privacy Policy concern. Describe the data or event involved, such as a new-device sign-in or an OVO status record. Never include your password, wallet PIN or full bank credentials in the message.