Reference

Legal clarity for your viking55 account

viking55 Legal explains how account access, wallet records, policy requests and local eligibility work before you open an account.

Account termsWallet recordsPolicy requestsLocal law
viking55 Legal clarity for your viking55 account
POLICY CONTACT

Get help with a Legal request

A clear contact path helps when a Legal question concerns your account, wallet record or access status.

Account access Use the account support route when phone verification, login details or an access decision needs clarification. Include your account identifier and the wording shown on screen so we can connect your request to the relevant Legal rule.
Wallet record For a DANA, OVO, GoPay or QRIS record, send the transaction reference, date and method through the cashier support path. We use those details to check the account ledger without requesting your wallet PIN.
Policy change If you want a correction, access question or policy request recorded, state the precise change you are asking for. We will use the account contact route and may request details that confirm you control the account.
DATA PRACTICE

How Legal controls protect your records

We handle Legal matters through defined account and record practices rather than informal promises. Phone verification connects an account to its access request, payment references help us trace wallet activity, and browser…

Account details

We use the details attached to your account to identify access requests and match policy questions. Keeping your phone number and account fields current helps us separate your request from another account with similar payment details.

Cookie controls

Cookies can keep a browser session connected while you move from login to the lobby. You can manage cookie settings in your browser; changing them may require another login or affect how the account page remembers your session.

Payment records

A receipt from QRIS, DANA, OVO, GoPay, bank transfer or a virtual account gives us a reference for checking a wallet entry. Share the reference and date, while keeping PINs and one-time codes private.

Account security

Phone verification is required before account access, and your login details should remain private. If you notice an unfamiliar session or account change, stop using that session and contact us through the account support path.

Record retention

We retain account and transaction records for the period needed to operate the account, check payment status and meet applicable policy duties. A retention question should include the account identifier and the record type you mean.

Change requests

To request a correction or ask how a Legal rule applies, contact us through the account route with a short description and supporting reference. We may ask for confirmation before changing account-linked details.

Answers before you open an account

These Legal answers cover the questions we expect you to ask before creating or using an account. They explain access, records, cookies, payment references and contact steps without replacing the policy terms that apply to your account. Where eligibility or local access is discussed, the position depends on local law.

It covers account ownership, phone verification, wallet records, cookies, security requests, record retention and policy contact steps. It also explains that access to the account or specific lobby areas depends on local law, so you should check your local position before opening an account.

Yes. Legal terms allow us to connect a payment reference with the account path used for DANA, OVO, GoPay or QRIS. If a record needs checking, send the method, date and reference through support, never your wallet PIN or one-time code.

Phone verification helps us confirm that an access request belongs to the account holder. It is part of the Legal account process before access, and it also gives our support route a clearer way to match a security or policy request.

Yes. Send the requested correction through the account contact path and explain which field or record is wrong. We may ask for account confirmation before making a change, because Legal controls require us to protect account-linked details from unauthorised edits.

Cookies may keep your browser session connected between login and account pages. You control them through your browser settings, although removing them can require another login or change session behaviour. A cookie question can be sent through the same policy contact route.

We keep records for the period needed to operate account access, trace payment status and meet applicable policy duties. The exact period can depend on the record type and local requirements. Ask us with your account identifier if you need a retention clarification.

Access and eligibility depends on local law. We may use account or location details when a policy check is required, and you should only open or use an account where local law permits. Contact us if a location message needs clarification.