Reference

Open eka jitu Privacy Policy With Clarity

eka jitu Privacy Policy explains what we collect when you create an account, verify your phone, sign in from mobile or desktop, and use DANA, OVO, GoPay or…

Account dataWallet recordsDevice choicesPrivacy requests
eka jitu Open eka jitu Privacy Policy With Clarity
CONTACT ROUTES

Reach Us About Privacy Policy Questions

A clear contact path helps when your Privacy Policy question concerns an account record, wallet reference or device session. Start from account help or the cashier status path and include the phone number linked to your account, the date of the event and the request you want us to check. We may ask for a confirmation step before discussing personal data. If you are in Jakarta or elsewhere in Indonesia, the same request path applies; access still depends on local law.

Team online

Account data request

Use the account help path to ask which personal details are attached to your eka jitu profile. Include your registered phone number and the specific correction or access request, so we can identify the right record without asking you to send a password.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, use the cashier status path and state the transaction date. We use that detail to locate the record, explain its purpose and keep payment evidence separate from unnecessary profile data.

Device access concern

If a mobile or desktop sign-in looks unfamiliar, contact account support through the same help route and mention the device type and approximate time. We can check the session trail, advise an account-security step and avoid exposing private details before verification.

DATA PRACTICES

Switch On Better Privacy Understanding

Privacy is easier to manage when each control has a clear reason. We separate account identity, wallet references and technical session details, limit internal access to the people…

Account details

We collect the details needed to create and protect your account, including your phone number and verification result.

Wallet references

A DANA, OVO, GoPay or QRIS reference helps us match a cashier event to your account without treating the wallet…

Cookies and sessions

Cookies and similar session tools can keep your sign-in path working across the lobby and help us recognise a device…

Account security

We use phone verification, sign-in records and device signals to reduce account takeovers.

Retention choices

We keep information only for the period needed for the stated account, wallet, security or legal purpose.

Change requests

You can ask us to access, correct or question personal data by using account support and naming the record involved.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers address the questions we expect you to ask before opening an account with eka jitu. They cover the data connected to sign-in, local wallets, cookies, device changes and requests for access or correction. If your situation is different, use the account help path with the relevant date or record. Any access or eligibility question depends on local law, and we will explain the applicable route where local law permits.

The eka jitu Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, and wallet references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security and ways to request access or correction.

We use your phone number to create the account record, complete a phone verification step and help distinguish you from another person requesting account data. If you ask us to change or disclose information, we may use that same step to confirm ownership.

Yes. The Privacy Policy includes references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These references help us match a wallet event, check a status question and investigate a discrepancy without requesting unrelated personal details.

We use device type, browser signals, cookies and session timing to keep sign-in working and identify unusual account access. You can adjust browser cookie settings, but doing so may interrupt the mobile path or require phone verification again before access continues.

You can request access or correction through account support by naming the information involved and confirming the phone number linked to your account. We assess the request under local law, explain any restriction and tell you what action was taken where local law permits.

Retention depends on why the record exists. Account, wallet and security details may remain while needed for support, protection, dispute handling or a legal requirement. After that purpose ends, we delete, anonymise or restrict the record according to the applicable rule.

Use the account help path and describe the Privacy Policy concern, the relevant date and the record you believe needs attention. For a wallet issue, include the cashier reference; for a device issue, include the device type. We may verify ownership before replying.