Reference

jerami4d Privacy Policy For Your Account

Our Privacy Policy explains how jerami4d handles account details, wallet records and device signals when you open the lobby from Indonesia.

Account clarityWallet recordsDevice controlsCookie choices

Explore Our Lobby Read FAQ

How Wallet Data Is Used

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

This Privacy Policy describes the data we receive when you create an account, complete phone verification, sign in, contact support or use the cashier path. We may handle your name, phone number, login events, device details, transaction references and security checks so we can connect the

1
correct account to a request. DANA, OVO, GoPay and QRIS may return payment status or reference data; bank transfer and virtual account records can identify the matching transaction. We use these records for account security, payment reconciliation, fraud checks and required retention. We do not describe
2
access as universal: where local law permits, you can use the account path shown on our site. The policy applies to the jerami4d website and its cookies, not to a separate wallet provider’s own practices.

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

CONTACT PATHS

Privacy Questions, Directly Handled

A clear contact path helps when you want to ask about a record, cookie or account request. Use the support contact displayed inside your jerami4d account area and include the phone number linked to your profile. We can then match your request with the right account or payment reference without asking you to send a password.

Team online

Account privacy request

Ask about account data through the support contact shown after login. Include your registered phone number and the request type, but never send your password or one-time verification code.

Wallet record check

For DANA, OVO, GoPay, QRIS or bank transfer records, provide the transaction reference and date. We use those details to locate the relevant payment entry without exposing unrelated account activity.

Cookie question

If a cookie or device signal concerns you, mention the browser and device path used to open the site. We will explain the available account or browser action for that request.

DATA CONTROLS

Account Security And Data Choices

We keep this policy practical by linking each data purpose to a visible account action or support request.

Data handling

We handle registration details, phone verification results, login events, device signals and payment references for account operation, security checks, support responses and transaction reconciliation.

Cookies

Cookies can help preserve sign-in state, remember necessary settings and identify unusual access. Your browser controls provide a route to remove or restrict them, although some account steps may then need repeating.

Account security

Phone verification before account access helps connect a session to the correct profile. Keep your password private, and contact support if a login event or device signal looks unfamiliar.

Retention

We retain account, security and transaction records for the period needed for the stated purpose, account protection and applicable obligations. A retention question can be sent through the account support path.

Change request

You can ask us to correct an account detail by naming the field and confirming the registered phone number. We may request extra verification before changing information tied to wallet activity.

Third-party records

DANA, OVO, GoPay, QRIS, banks and virtual account providers maintain their own records. Questions about their handling may also require contacting that provider through its own support route.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account actions you are most likely to take before opening access or checking a wallet record. We keep the wording tied to jerami4d, Indonesian payment references and the device path you actually use, so you know which request belongs with us and which belongs with a payment provider.

It covers account details, phone verification, login events, device signals, cookies, support requests and transaction references connected with our website. Separate wallet or bank providers follow their own privacy terms.

We use your phone number to create and identify the account, complete phone verification before access and help match a support request. It also helps us separate your profile from another account.

Yes. It explains how we handle payment references and status data returned for DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity. The wallet provider controls its own separate records.

Use the support contact shown inside your account and name the detail that needs correction. Include your registered phone number, then complete any identity check required before we change account-linked data.

Yes. Contact us through the account support path and mention your browser and device. We can explain necessary sign-in cookies and available browser controls, though restricting them may require repeated access steps.

We keep transaction, security and account records for as long as needed for their stated purpose, account protection and applicable obligations. You can ask support about a particular record using its reference.

Yes. Account access and any related request depend on local law. Where local law permits, use the account support route to ask about your data, wallet reference or cookie preference.

jerami4d Privacy Policy For Your Account

Privacy Questions, Directly Handled

Account privacy request

Wallet record check

Cookie question

Account Security And Data Choices

Data handling

Cookies

Account security

Retention

Change request

Third-party records

Privacy Policy Questions From Indonesia

01 What does the jerami4d Privacy Policy cover?

02 Why does jerami4d need my phone number?

03 Does the Privacy Policy include DANA and QRIS records?

04 How can I request a correction to my account data?

05 Can I ask jerami4d to explain cookie use?

06 How long does jerami4d keep transaction data?

07 Does Privacy Policy access depend on local law?

Related Pages