Reference

timezone55 Privacy Policy For Your Account

Our timezone55 Privacy Policy explains what account, device and wallet details we collect, why we use them and how you can request help.

Account dataWallet recordsCookie choicesSecurity requests
timezone55 timezone55 Privacy Policy For Your Account
REQUEST A CHECK

Get Policy Help Near Your Cashier Path

A clear support route helps you ask what data we hold, correct an account detail or question a wallet record without repeating your full payment credentials.

Account privacy request Use our account help path to ask for a copy, correction or clarification of personal details connected with your timezone55 account. We may request a phone verification step before discussing account-specific records.
Wallet record check For DANA, OVO, GoPay or QRIS questions, send the payment reference and approximate date shown in your cashier history. We can trace the record without asking for your wallet password or secret security code.
Login data concern If a device path, login event or phone verification entry looks unfamiliar, contact support through the account route and describe what you saw. We can review the relevant access record and guide the next security step.
HANDLING YOUR DATA

Inside timezone55 Privacy Controls

Privacy choices should be practical, so we connect each request to the account step where the data appears.

Account details

We use the contact and verification details you submit to create your account, confirm ownership and respond to requests. Check your profile before contacting us so a correction request identifies the exact field that needs attention.

Cookies and device signals

Cookies and device signals can remember a session, support security checks and help us identify unusual login behaviour. Your browser controls some cookie choices, while required security storage may remain active for account protection.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with its status and time. We use these records to match cashier activity, resolve disputes and avoid duplicate handling.

Account security

Phone verification and sign-in signals help us check that an account request comes from its owner. Never send a password or wallet PIN to support; describe the issue and use the account security path.

Retention approach

We keep personal records for as long as needed for account operation, security checks, dispute handling or applicable legal duties. When a record is no longer needed for those purposes, our handling process moves it toward removal.

Changes and contact

You can ask about access, correction, deletion or a policy change through support. Include your account contact and the request type, but leave out wallet passwords; we may verify ownership before releasing or changing records.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and payment questions we hear most often from people using timezone55 in Indonesia. They explain the practical route for checking data, changing details, understanding cookies and raising a security concern. If your request involves a specific account record, use the support path and provide only the minimum details needed to locate it. Access depends on local law.

The timezone55 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use these records, how we protect account access, how long records may be retained and how you can request a change.

Contact us through the account help path and ask for a copy of the personal data linked to your account. Include your account contact, identify the request clearly and complete any ownership check we ask for before records are released.

Yes. The Privacy Policy includes payment references and status details connected with DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account activity. We use those records to match a cashier event and investigate a payment question without requesting your wallet password.

You can request a correction through support by naming the account field that is wrong and providing the updated detail. We may verify phone ownership first, particularly when the change could affect login, account recovery or payment status records.

We use cookies and related device signals to keep a session working, remember selected preferences and support unusual-login checks. Browser settings can control some cookies, but storage needed for account security may continue while you use the service.

Use the account security support route and describe the unfamiliar login, device path or phone verification event, including its approximate time. Do not send a password, wallet PIN or full payment secret; we will verify ownership and explain the next step.

You can submit a removal request through support, and we will assess which records can be removed. Some account, payment or security records may need to remain for operational or legal reasons. Any outcome depends on local law and the request details.