Reference

ajototo Privacy Policy For Your Account

Our Privacy Policy explains how ajototo handles the details linked to your account, device and wallet activity before you open the lobby.

Account detailsDevice activityWallet recordsYour requests
ajototo ajototo Privacy Policy For Your Account
REQUESTS MADE CLEAR

Where To Ask About Account Data

A direct support route helps you act on this Privacy Policy without guessing which team should receive your request. Start from the signed-in account area when you can, because the account step lets us connect your request to the correct profile. If login or wallet status stalls, use the support path shown near account and cashier controls. Send only the details needed to identify the issue; never include a wallet password. We can then check a payment receipt, account record or device-access question with less back-and-forth.

Team online

Account request

Use the support path inside your signed-in account to ask for a copy, correction or clarification of personal details. We may ask you to complete phone verification before discussing account-specific records, so the request reaches the right profile.

Wallet record

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the date, amount reference and payment rail name rather than a password. We use those details to check status while limiting the information shared in your message.

Access concern

When a login, device or verification concern appears, tell us what changed and whether you still control the registered phone. We can review the account-security trail and explain the next step through the available support route.

SIX DATA CONTROLS

Six Controls Around Your Account Data

Privacy protection works best when each account action has a clear data purpose.

Phone verification

Before account-specific access is discussed, we may use the registered phone verification step to confirm that you are asking about…

Login signals

We record practical sign-in signals such as device type, browser session and access time to identify unusual activity.

Cookie choices

Cookies can keep a signed-in path working and help us understand whether a page session has continued.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a payment status to the correct account.

Retention checks

We retain account, security and payment references only for the period needed for account operation, dispute handling and legal duties.

Change requests

You can ask us to correct an account detail, explain a data use or discuss removal through the signed-in support…

Privacy Policy Questions About ajototo

These Privacy Policy answers address the questions we expect you to have before opening an account or checking an existing record. We keep the wording practical: what we collect, why wallet references appear, how you request changes and what happens when you use a different device. If your situation is not covered, use the account support path and mention the relevant payment rail or verification step so we can direct the request accurately.

The ajototo Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and the ways you can request access or correction.

We use your phone number to create and protect the account path, complete the required verification step and connect support requests to the correct profile. If you ask about account data, we may confirm control of that registered number before sharing or changing personal details.

No. Our Privacy Policy describes payment references and status records, not wallet passwords. A DANA or QRIS reference can help us match a receipt to your account, while OVO, GoPay, bank transfer and virtual account checks use the transaction details available to our payment process.

Sign in, open the account support route and state whether you want a copy, correction or explanation. Include the registered phone or a relevant payment reference, but do not send a password. We may verify your account first and will handle the request according to local requirements.

We may record device type, browser session, access time and related security signals when you sign in from another phone or computer. Under this Privacy Policy, those details help us identify unusual access and protect your account; they are not a request for unrelated files or content.

We keep records while they are needed for account security, payment matching, dispute handling or legal duties. After that period, we remove them or reduce identifying detail where practical. The exact period can vary by record type and by requirements that apply where local law permits access.

Yes. You can ask support how cookies and device signals were used, and you can request a correction or discuss removal through the signed-in account route. Browser cookie controls are also available, but restricting them may end a session or require another phone verification step.