Reference

Privacy Policy For Your adipati55 Account

Our Privacy Policy explains how adipati55 handles the details you provide when you open an account, verify your phone, enter the lobby and request wallet activity through DANA…

Clear data purposesPhone verification contextIndonesia wallet recordsCookie choices
adipati55 Privacy Policy For Your adipati55 Account
CONTACT PATHS

Privacy Questions Reach Our Support

A clear contact route helps when a privacy request is connected to a login or wallet record. From your account area, use the support path beside the cashier flow and include the phone number linked to your profile, the relevant date and the request you want us to check. We use those details to locate the correct record without exposing another account. If you are in Surabaya or elsewhere in Indonesia, the same account-based path applies where local law permits.

Team online

Data access request

Ask us to identify the account data connected with your adipati55 profile. Include your verified phone number and the account step involved, such as phone verification, login or a QRIS receipt, so we can match your request carefully.

Correction request

If your account name, phone detail or wallet reference is inaccurate, tell us what needs changing and why. We may ask you to complete the same phone verification step used for account access before applying a correction.

Status and privacy help

When a DANA, OVO, GoPay or QRIS record is part of your question, send the payment reference and approximate time through the support path beside the cashier area. We can then separate a privacy request from a general status check.

DATA PRACTICES

Six Ways We Handle Your Records

Our privacy approach follows the actual account journey rather than treating every detail alike. Phone verification supports account access, device signals help us recognise a returning session, and payment references let us…

Account details

We use the details you enter during account opening to create your profile and connect later requests to the right account. Your phone number is particularly important because the phone verification step helps us distinguish your access from an unverified attempt.

Device signals

When you move from login to the lobby on a mobile browser, we may record basic device, browser and session signals. These help us identify unusual access patterns and keep a returning session connected to the account you verified.

Cookies

Cookies can remember selected settings and support the session that follows login. You can manage cookie controls in your browser, although changing them may affect account access, saved preferences or the way the privacy page displays on your device.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be linked to the related account request, status and time. We use that trail to investigate a mismatch, rather than requesting your full wallet history when a single receipt can answer the question.

Account security

We use phone verification, session checks and access records to reduce unauthorised account activity. Keep your verification details private, sign out on shared devices and contact support if a login record or device session does not look familiar.

Retention requests

We retain records only for the account, security, support or legal purpose described in this policy and then remove or anonymise them when that purpose ends, where permitted. You can ask us to explain the retention of a particular account record.

Privacy Policy Questions From Indonesia

These answers address the questions we expect you to ask before opening an account or sending a data request. Each answer stays tied to the adipati55 Privacy Policy, including account access, Indonesian wallet references, cookies, device records and the route for asking us to inspect or change information connected with you.

It covers account details, phone verification, login and 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 and how to ask about access, correction or retention.

Phone verification helps connect account access to the person who entered the phone detail and helps us investigate unusual login activity. We may use the verification status when you request support about a session, wallet reference or account correction, where local law permits.

Yes. The Privacy Policy covers the reference, status and timing connected with a DANA, OVO, GoPay or QRIS request, along with bank transfer and virtual account references. We use those details to trace the relevant account event, not to request unrelated wallet history.

Use the support path beside the cashier area and state that you want an account data access request. Include your verified phone number, the record or date concerned, and a safe way to receive our reply. We may confirm account ownership before disclosing connected records.

Yes, you can request correction of an inaccurate account detail, phone record or payment reference. Tell us which field is wrong and provide the relevant account step. We may repeat phone verification before making a change so one account is not altered by another person.

Cookies can remember session and preference details when you move from mobile login to the lobby. Browser controls let you change cookie settings, but blocking required cookies may interrupt sign-in or remove saved choices. The Privacy Policy explains their role without changing your account rights.

We keep each record for the account, security, support or legal purpose that requires it, then remove or anonymise it when that purpose ends where permitted. Ask through support about a specific login, phone verification or QRIS record if you need a retention explanation.