Reference

samudrabet Privacy Policy For Your Account

Our Privacy Policy explains what samudrabet collects when you open an account, use DANA or QRIS, and move between the lobby and cashier.

DANA RECORDSQRIS RECORDSCOOKIE CONTROLSACCOUNT REQUESTS
samudrabet samudrabet Privacy Policy For Your Account
PRIVACY CONTACT

Get Privacy Help Before Account Access

A clear contact path matters when your account details do not look right. We route privacy questions through account help, with the cashier path available when your request concerns a DANA, OVO…

Account help Ask us to check a profile detail, login record, or verification entry through account help. We may ask for a matching account detail before discussing private data, and we never need your password.
Cashier privacy route Use the cashier path when a privacy question concerns DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records. Share the reference and date, while keeping card, wallet, and login secrets private.
Correction request Tell us which account field needs correction and what it should say. We compare the request with the account step used to create or verify your profile before changing the stored record.
DATA HANDLING

How We Handle Account Data

We keep this policy practical: data is tied to an account action, a security check, a support request, or a payment reference.

Account creation

When you open an account, we record the details needed to create your profile and communicate with you. A clear account path helps us connect later login, verification, and privacy requests to the right record.

Cookie choices

Cookies can remember session preferences and help us understand whether a login request belongs to the same browser. You can manage browser cookie settings, although changing them may affect account access steps.

Login security

We examine device and session signals around login activity to identify unusual access. If a security check interrupts your account path, contact account help rather than sharing a password or one-time code.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records may show a reference, amount status, and timing. We use those details to match a cashier event, not to request unrelated wallet credentials.

Retention period

We keep account, support, security, and transaction records for the period needed for service operation, fraud checks, disputes, or legal duties. When that need ends, we delete, aggregate, or restrict the record.

Change requests

You can ask us to correct eligible account data, explain its use, or request deletion where local law permits. We verify ownership first, then confirm what action we can take and why.

Privacy Policy Questions About samudrabet

These answers address the privacy searches we hear most often before an account is opened. They explain the account step, payment records, device behaviour, and contact route in plain terms, while keeping every request subject to local law and the identity checks needed to protect your data.

The Privacy Policy covers account details, verification data, login and device records, cookies, support messages, and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We need selected details to create your account, confirm that a login belongs to you, answer support requests, and match cashier records. We do not ask for your password when handling a privacy request.

Yes. It includes the reference, status, and timing connected with QRIS, DANA, OVO, and GoPay activity, plus bank transfer and virtual account records where those details are needed to check an account event.

Cookies can preserve session choices and help connect a browser with a current login. You can adjust cookie settings in your browser, but blocking some cookies may interrupt account access or verification steps.

You can contact account help to ask what eligible data we hold or to correct an account field. We first verify ownership, and the request is handled where local law permits.

We retain records for operational, security, dispute, or legal needs. This can include account activity, support messages, and payment references; when the need ends, we remove, aggregate, or restrict them.

Use the cashier privacy route and provide the payment reference and date, without sending a password or wallet secret. For access or eligibility questions, the answer depends on local law.