Reference

jimat78 Privacy Policy for Your Account

Our Privacy Policy explains how jimat78 handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Clear data purposesCookie choicesAccount access rightsLocal wallet context
jimat78 jimat78 Privacy Policy for Your Account
HELP WITH DATA

Three Ways to Ask About Privacy

A privacy question should not leave you searching through unrelated pages. We connect account help with the support route near the cashier, so you can ask about a record, a cookie choice or a correction request while signed in. If you reach us from a mobile browser or desktop browser, include the email or phone detail linked to your account and describe the exact request. We will use that context to locate the right record without asking for unnecessary payment credentials.

Team online

Account support route

Open the support path from your signed-in account when you need a Privacy Policy answer, a data correction or help identifying which account detail we hold.

Cashier-linked help

When a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact us through the account help path beside the cashier and include the transaction status shown there.

Device access request

If a mobile browser or desktop session creates a privacy concern, tell us the device path, approximate time and account identifier so we can check the relevant security record.

DATA HANDLING

Six Practical Privacy Commitments

Privacy controls work best when they match the steps you actually take. We explain what happens around account creation, browser cookies, wallet references and sign-in protection rather than hiding those details behind…

Purpose first

We use submitted account details for access, verification, support and security tasks connected to your account. We do not describe wallet references as a reason to collect unrelated personal details.

Cookie control

Cookies and similar browser records can support sign-in continuity, security checks and session preferences. You can adjust browser settings, although some account steps may require an active session.

Account security

Clear phone verification before account access helps us distinguish your sign-in from an unfamiliar attempt. Never send a password, wallet PIN or one-time code through a support request.

Payment separation

DANA, OVO, GoPay, QRIS and bank transfer references help match a cashier event with your account. We use those records for status checks and support, not for unrelated profile purposes.

Retention checks

We keep records only for the period needed for account operation, security, payment matching or a permitted legal purpose. When no longer needed, records may be deleted or changed into non-identifying data.

Change requests

Ask us to correct eligible details by using the signed-in support route. Include the account contact detail and the change needed; we may request verification before altering a protected record.

Privacy Policy Questions About jimat78

These answers address the searches we hear most often before an account is opened or when a wallet status needs checking. For a request tied to your own record, use the signed-in support path so we can verify the account and respond to the correct person.

The jimat78 Privacy Policy covers account details, phone verification, browser and device signals, cookies, payment references, security checks, retention and requests to access or correct eligible personal data.

Yes. The Privacy Policy explains how DANA and QRIS references may be used to match a cashier status with your account, investigate a receipt and answer a payment-related support request.

You can request a correction through the signed-in support route. Tell us which account field is wrong and what it should say; we may verify your identity before making the change.

Cookies may support sign-in continuity, security checks and session preferences on your mobile or desktop browser. You can manage them in browser settings, but restricted cookies may affect some account steps.

We keep personal data for account operation, security, payment matching, support or another permitted legal purpose. When the stated need ends, we may delete the record or remove identifying details.

Use the account support path and describe the personal data request clearly. Include the contact detail linked to your account, and expect an identity check before we disclose protected account information.

Yes. Access or eligibility depends on local law, and some data requests may have different handling requirements by location. Contact support from your account for a request connected to your circumstances.