Reference

Privacy Policy for send 4d Accounts

Our Privacy Policy explains how send 4d handles the details connected with your account, phone verification, device session and wallet status.

Account detailsWallet referencesDevice sessionsYour access choices
send 4d Privacy Policy for send 4d Accounts
HELP WITH YOUR RECORDS

Get Clear Answers About Privacy

Questions about the Privacy Policy should reach our account help route with enough detail for us to locate the right record.

Account privacy request Ask us what account details, phone verification records or login events are connected with your send 4d profile. Include the contact detail on the account so we can assess your request without exposing records to an unknown person.
Wallet record question Send a question about a DANA, OVO, GoPay or QRIS reference when a payment receipt does not match your account history. We use the reference and account step supplied by you to trace status without asking for an unnecessary wallet password.
Access correction path Contact us when your name, phone detail or account record needs correction. We may ask for a phone verification step before changing access-related information, because a privacy request must not expose or alter another person’s account.
OUR DATA PRACTICE

What We Keep And Why It Matters

We handle Privacy Policy requests through the same account controls that protect your login and payment history.

Account details

We collect the details needed to create and maintain your account, including contact information and the result of phone verification. That information helps us distinguish an authorised account step from an attempted change made without your permission.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show whether a payment request reached the correct account. We use transaction status data for matching and support checks, not as a request for your wallet PIN.

Mobile cookies

Cookies and related session tools help keep your mobile browser connected during login and account navigation. They can remember a session signal or security preference, while your browser settings provide controls for removing or restricting cookies.

Device security

We may record device and browser signals, such as session timing and connection details, to identify unusual access. This can apply when you move from a phone to a desktop before opening a lobby page such as Auto Roulette Live.

Retention choices

We retain personal records only while they support account access, payment reconciliation, security checks, dispute handling or applicable local requirements. When a record no longer serves one of those purposes, we assess it for deletion or de-identification.

Change requests

You can ask us to correct account details, explain the data linked to your profile or clarify a retention question through our privacy contact route. We may verify your phone before acting, and access remains where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect from someone checking send 4d before opening an account. They focus on personal records, wallet references, device sessions, correction requests and access conditions rather than describing unrelated service features. Each answer points back to a practical account or contact step, so you know what to include when asking us for help.

It covers account details, phone verification, login and device session records, cookies, payment references and contact requests. It also explains retention, security checks and how you can ask for access or correction where local law permits.

Phone verification helps confirm that a request to open, access or change an account comes from the person connected with that account. We may use its result as a security record without treating it as permission to collect unrelated phone content.

Yes. The Privacy Policy covers DANA and QRIS transaction references, as well as OVO, GoPay, bank transfer and virtual account status details. We use these references to match payment activity and investigate receipts, not to request your wallet password.

We may record browser, device and session signals such as access timing, connection details and security events. These records help us assess unusual login activity when you move between a mobile browser and desktop, including before opening a game page.

You can contact us to request a correction to account information, contact details or a linked payment reference. Include the account contact detail and explain the change. We may complete phone verification before altering access-related records.

We keep records while they support account access, payment reconciliation, security checks, dispute handling or applicable local requirements. We then assess whether continued retention is needed. A retention question can be sent through the privacy contact route.

Use the account privacy request route and include the subject of your question, such as cookies, device sessions, phone verification or a QRIS receipt. We use the supplied account detail to identify your request and respond where local law permits.