Reference

tamubet Legal: Know Your Account Rights

tamubet Legal gives you a clear place to check account duties, data choices and access conditions before you open an account.

Account termsData choicesLocal access
tamubet tamubet Legal: Know Your Account Rights
CONTACT ROUTES

Where To Raise A Legal Request

A written request is easier for us to resolve when it points to one Legal topic. Use the account support route first, then include the payment rail or account step involved so our team can identify the right record without asking you to repeat the same explanation.

Team online

Account policy question

Open the support link from your signed-in account and name the Legal clause you are asking about. Include your phone verification status so we can match the request to the correct account record.

Wallet record query

For a DANA, OVO, GoPay or QRIS concern, attach the payment reference and date through the cashier support path. We use those details to separate a policy question from a status mismatch.

Change request

Ask us to correct an account or data detail through the available support channel inside your account. State the old value, the requested change and why the record should be amended.

DATA PRACTICE

How tamubet Handles Your Records

Legal also sets out how account records are used during access, payment checks and policy requests.

Data use

We use account details for access control, phone verification and matching a wallet or bank transfer record to the request you submit. We do not need unrelated personal details for a policy question.

Cookie choices

Cookies can support sign-in continuity and page settings on your device. Check your browser controls before accepting them, and contact us if a cookie choice affects your access to the Legal page.

Account security

Keep your phone details private and do not share account credentials through a payment message. If you notice an unfamiliar access event, use the signed-in support route and describe when it occurred.

Record retention

Some account, payment and request records may need to remain available for a defined operational or legal period. Ask support which record category your request concerns and what action can be taken.

Correcting details

You can request a correction when your name, phone status or account detail is inaccurate. Send the affected field and supporting context through the account contact path rather than creating a second account.

Policy contact

For a Legal request, identify yourself through the account route and quote the relevant page wording. This lets us confirm ownership before discussing account data or applying a permitted change.

Legal Questions Before Account Access

These Legal answers cover the checks you are most likely to make before opening an account or asking us to change a record. If your question involves a specific DANA, OVO, GoPay, QRIS or bank transfer reference, include it in your support request.

It covers account conditions, access wording, data handling, cookies, security, record retention and policy contact routes. It also explains why phone verification and payment references may be needed.

Service access depends on local law and your location. Check the rules that apply to you before opening an account, and do not continue where local law does not permit access.

Phone verification helps us connect an account request to the person controlling the account before access or a data change. It also reduces confusion when a wallet or bank record is queried.

Use the support route inside your account, identify the field that is wrong and describe the correction requested. We may ask for account context before changing a stored record.

A DANA or QRIS reference may be used to match a wallet request with the correct account record. Include its date and reference when asking about a Legal or status matter.

Yes. Send a retention question through the account contact path and name the record type, such as phone verification, wallet status or bank transfer. We can then address the relevant category.

Open the support contact route from your account and quote the policy wording or event date. Add your account identifier, then keep the submitted reference for any follow-up.