Reference

Open tokyo 404 Privacy Policy Clearly

tokyo 404 Privacy Policy explains what we collect when you open an account, check wallet status or access the lobby from your phone.

Policy accessWallet data clarityAccount controlsLocal-law wording

Explore Our Lobby Read FAQ

Browse How Policy Covers Wallet Records

tokyo 404 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide during account creation, including your phone number and verification status, plus records created when you check a balance or request a wallet action. We may receive transaction references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account routes

1
so we can match a receipt to your account. Device type, browser signals, login time and pages opened can help us protect access and keep the account path working on mobile. We use this material for account operation, security checks, support replies and legal duties where
2
applicable. We do not describe access as universal: it depends on local law. If a policy change affects how a named payment rail is handled, we will place the updated wording on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Contact Us About Your Privacy Choices

A direct privacy question should not get lost beside a cashier issue.

DATA PRACTICES

Check Your tokyo 404 Data Controls

We keep the policy practical by linking each data category to an account action you recognise.

Account details

We use your phone number and verification result to connect you with the correct account during access checks. If either detail changes, contact us through the account route and ask for a correction rather than opening a second account.

Wallet activity

A DANA, OVO, GoPay or QRIS reference can be stored with an account action so we can reconcile a receipt or investigate a wallet status question. We do not need your wallet PIN or private wallet password for that check.

Device signals

Your mobile browser or desktop browser may provide device type, session time and basic access signals. We use these details to identify unusual account activity and to keep a phone verification step attached to the right session.

Cookies

Cookies can remember a session choice and help us see whether a page loads correctly. You can adjust cookie settings in your browser, although restricting them may require another login or make some account pages work differently.

Retention

We keep records only for the period needed for the stated account, support, security or legal purpose. When a record is no longer needed, our handling follows the deletion or anonymisation process available for that data category.

Change requests

You may ask us to correct account data, explain a wallet reference or clarify a policy use. Send the request from the contact path with your registered phone detail; we may verify ownership before changing or releasing anything.

Browse Privacy Policy Answers For Your Account

These answers focus on the questions you may have before opening an account or sending a privacy request. We keep the examples close to the actual account flow: phone verification, mobile access, wallet references and support checks. If your situation falls outside these examples, contact us through the account path and mention the relevant Privacy Policy section. Requests and access remain subject to local law.

It covers account details, phone verification, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records, how long they may remain and how to request a change.

We use your phone number to create and identify your account, then connect the verification result to the correct login session. This helps us answer an access or Privacy Policy request without confusing your account with another account using a similar wallet reference.

Yes. The policy covers transaction references and status details that may be linked to your account when you use DANA or QRIS, as well as OVO, GoPay, bank transfer or virtual account routes. We do not ask for your wallet PIN.

Use the account support route and include your registered phone number, the request type and the relevant Privacy Policy section. We may complete an ownership check through phone verification before explaining the record or correcting details.

The policy may cover your browser type, device category, session time and basic access signals from a mobile or desktop browser. We use these details to support login checks, identify unusual activity and understand why an account page may not load correctly.

Yes. Your mobile browser provides its own cookie controls, and you can adjust them in the browser settings. Restricting cookies may sign you out, ask for phone verification again or change how account and Privacy Policy pages behave.

It can. Access and eligibility depends on local law, and some requests may require identity confirmation or follow a locally applicable retention duty. We will explain the relevant step when you contact us rather than treating every request as identical.

Open tokyo 404 Privacy Policy Clearly

Contact Us About Your Privacy Choices

Check Your tokyo 404 Data Controls

Account details

Wallet activity

Device signals

Cookies

Retention

Change requests

Browse Privacy Policy Answers For Your Account

01 What does the tokyo 404 Privacy Policy cover?

02 Why does tokyo 404 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS data?

04 How can I request a copy or correction of my data?

05 What device data does tokyo 404 collect?

06 Can I change cookie settings on my phone?

07 Does local law affect privacy requests or account access?

Related Pages