Reference

epostoto Privacy Policy: Your DANA and QRIS Data Path

epostoto keeps your account, device and wallet data connected to clear account steps, so you can understand what we collect before opening access.

Account clarityWallet recordsMobile privacyLocal access
epostoto epostoto Privacy Policy: Your DANA and QRIS Data Path
HELP WITH REQUESTS

Get Policy Help Beside Your Account

A clear contact route matters when a privacy question is connected to a login or wallet record. From your account help path, tell us whether you need a copy of data, a correction, deletion consideration or clarification about a payment reference. Include the phone number on the account and the relevant transaction date, but never send a password or full wallet credentials. We use those details to locate the right record without asking for unnecessary data.

Team online

Account privacy request

Use the account help path to ask about phone verification, login records or stored profile details. We may ask you to confirm account ownership before discussing personal data, so a request is connected to the correct epostoto account.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction reference and date. We can check the status kept in our records without requesting your wallet password, PIN or complete financial credentials.

Policy change request

If a detail is incorrect or you want to ask about removal, send the relevant account field and your reason through the policy request path. We assess the request against account safety, transaction records and obligations that may apply where local law permits.

DATA HANDLING

How epostoto Applies This Policy

Privacy choices should match the way an account actually works, from a phone check to a wallet status update.

Account data

We use your phone number, account status and verification result to identify the correct account during login support. Phone verification is an account step, not permission to read your contacts, photo library or unrelated apps on your device.

Payment references

A DANA, OVO, GoPay or QRIS entry may show a reference, amount status and time needed to match a transaction. Bank transfer and virtual account records are handled in the same narrow way, without storing your banking password.

Cookies and sessions

Cookies and device signals help keep your session tied to the correct account and remember essential settings. Clearing browser cookies can sign you out or remove saved preferences, but it does not erase account records held for transaction or safety needs.

Account security

We use login events, device changes and verification checks to investigate unusual access. If a sign-in does not match your usual pattern, we may pause a request until ownership is confirmed. Never share your password, PIN or wallet credentials with support.

Retention period

We keep personal data only while it supports account operation, payment tracing, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it or change it so it no longer identifies you directly.

Your changes

You can ask us to correct account data, explain a processing purpose or consider deletion through the policy request path. We may retain a limited transaction or security record when removal would prevent account protection or conflict with an obligation.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or a wallet record is checked. We keep the wording practical: what data is used, which account step confirms ownership, how device sessions behave and where to send a request. If your situation is not covered, use the policy request path with the smallest useful set of account details.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It also explains retention, security checks, request handling and the conditions for access where local law permits. The policy does not give us access to unrelated apps or your wallet password.

Phone verification helps us connect a login, support request or account change to the correct account. It can also help investigate unusual access. We use the verification result for account control and do not treat it as permission to inspect your contacts, messages or other device content.

No. Our records may contain a DANA or QRIS transaction reference, status and time so we can match account activity. The same approach applies to OVO, GoPay, bank transfer and virtual account records. Do not send a wallet password, PIN or full banking credentials.

Cookies and related device signals help maintain a signed-in session and keep the correct account state on mobile or desktop. Clearing them may sign you out or remove saved settings. It does not automatically delete account, payment or security records held for stated operational needs.

Yes. Send a request through the account help path and identify the account phone number, the data field involved and the action you want. We may confirm ownership before responding. A copy or correction request is assessed under this Privacy Policy and applicable local requirements.

You can ask us to consider deletion through the policy request path. We assess whether the data is still needed for account security, payment tracing, dispute handling or a legal obligation. If some records must remain, we explain the reason and remove unrelated data where possible.

Use the account help path for profile, login or phone verification questions, and include a payment reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account checks. Share only necessary details; support will not need your password or wallet PIN to locate a record.