Reference

gagakjitu Privacy Policy Explained

gagakjitu Privacy Policy sets out what we collect, why we use it, and how you can ask about your account data before opening an account.

Account dataDevice recordsWallet activityCookie choices
gagakjitu gagakjitu Privacy Policy Explained
CONTACT PATHS

Where Privacy Questions Go

A clear contact route helps you raise a privacy question without searching through the lobby.

Account help Use the account-help route for questions about your phone number, verification record, login history…
Receipt matching For a privacy question linked to DANA, OVO, GoPay or QRIS, keep the payment…
Data requests Ask through the privacy contact route when you want to see, correct or question…
HANDLING DETAILS

How We Manage Your Data

Privacy decisions are easier when the handling steps are visible. We separate account identity details from routine device signals, use wallet references to check a specific transaction, and limit internal access to…

Account records

We use the account details you submit, including the phone verification record, to connect access requests with the correct account. This helps us distinguish a genuine account question from an attempt to change another person’s details, while keeping the Privacy Policy relevant to the data you supplied.

Device signals

When you move between a mobile browser and desktop, we may receive technical signals such as browser type, session timing and device identifiers. We use them to examine access issues and unusual account activity, not to treat a device label as your identity by itself.

Cookies

Cookies can keep a session working and help us understand whether a page request belongs to an active account. Your browser settings provide controls for cookie storage, although changing them may affect login continuity or the route from account access to the lobby.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be retained with an account action so we can check a receipt or wallet status question. We do not need a full payment story for every request; send the specific reference that relates to your concern.

Retention choices

We keep records only for the period needed for the stated account, security, transaction or legal purpose. If you ask why a record remains, identify the data type and account step involved; we will assess the request against operational needs and requirements that depend on local law.

Correction route

If your phone detail, account name or device record is inaccurate, contact us with the current and corrected value. We may ask for an account check before changing it, because a correction must not interrupt phone verification or attach wallet activity to the wrong account.

Privacy Policy Questions Answered

These Privacy Policy answers address the questions most often raised before account access: what data is collected, how cookies work, how wallet references are handled and how to request a change. We keep the answers tied to the account steps you can see, including phone verification and cashier status checks. If a matter depends on regional rules, access depends on local law.

The Privacy Policy covers account details, phone verification, device signals, cookies, wallet references and requests to see or correct data. It explains why each category may be used and how to contact us. Access or eligibility depends on local law, including the rules applying to your location.

We use phone verification to connect account access with the person completing the account step and to investigate login questions. The record can also help us prevent an unauthorised change to account or wallet details. If it is wrong, use the correction route described in this Privacy Policy.

Yes. It covers transaction references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. These details help us match a receipt to the correct account when you ask about a wallet event or cashier status.

Use the privacy contact route and state that you want to see the personal data linked to your account. Include your account identifier and the categories you want checked, such as phone, cookie or device records. We may verify account ownership before responding to the request.

You can request a correction when a phone detail, account value or device record is inaccurate. Tell us which field is wrong and provide the replacement value through the stated account-help route. We may complete an identity check before making changes to protect your account.

Retention depends on the purpose of the record, such as account security, receipt matching, support or a legal requirement. The Privacy Policy does not treat every device or wallet reference alike. Ask us about a specific category, and we will assess its continued need under local law.

Cookies can support session continuity as you move from phone login to the lobby and may record preference or technical events. Your browser controls cookie storage. If you remove or block cookies, you may need to repeat an account step or encounter a different access path.