Reference

Open Your Privacy Choices

pejuang138 keeps account, device, payment and cookie data in one privacy flow so you can understand what we collect before you open an account.

DANA data contextOVO wallet checksGoPay payment recordsQRIS transaction logs
pejuang138 Open Your Privacy Choices
CONTACT ROUTES

Check Privacy Help Channels

Fast privacy contact paths matter when you need to correct a phone number, ask about payment records, or understand cookie use on a shared device. Our support team handles privacy questions every day through live chat, email and account message, with Bahasa Indonesia and English responses available. Send your request from the account email when possible so we can match it to your profile without asking for extra data.

Team online

Live chat

Use live chat from the account menu between 09:00 and 23:00 WIB for privacy questions about login records, device alerts, DANA references, or cookie settings. We may ask you to confirm your registered phone before changing account data.

Email privacy desk

Email privacy requests with your username, registered phone ending, and the data topic you want checked. Do not send full wallet PINs, card photos, or one-time codes; our team never needs those to answer privacy matters.

Account message

Send a message after you sign in when you want a record tied directly to your profile. This path helps us confirm the account step involved, such as password reset, QRIS payment status, or cookie preference.

DATA CARE

Browse Our Privacy Controls

Specific controls make a privacy policy useful. We separate sign-in data, wallet references, device checks, cookie choices, support history and retention steps so each request can be handled by the right team.

Account data

Your account profile can include username, phone number, email, password status, language choice and verification steps. We use these details to manage login access, answer your privacy request, and confirm that account changes come from you.

Payment references

DANA, OVO, GoPay and QRIS activity creates transaction references, timestamps and status labels in our wallet records. We use those details to match deposits, check withdrawal questions, and respond when you ask about stored payment data.

Device signals

When you sign in from Chrome on Android, Safari on iPhone, or a desktop browser, we may log device type, IP range, session time and browser signals. These logs help us spot unusual access and protect your account.

Cookie choices

Cookies remember session status, language preference, login flow and basic site measurement. You can clear them through your browser settings, and some features may ask you to sign in again after cookies are removed.

Retention periods

We keep records only for account operation, payment tracing, dispute handling and legal needs that apply to us. When a record is no longer needed for those purposes, we remove it or reduce it where practical.

Change requests

Ask us to correct profile details, update contact data, or explain how a privacy decision was made. For security, we match the request to your registered email, recent login step, or support history before acting.

Explore Common Privacy Questions

Privacy questions usually appear at practical moments: opening an account, changing a phone number, clearing cookies, checking DANA activity, or signing in from a new device. These answers explain how we handle those moments without asking you for more data than needed. If your question involves access or eligibility, local law decides availability and we apply that rule to the account involved.

We collect the details you provide during account creation, such as username, phone number, email and password status. We also record the account step completed, so privacy requests can be matched without exposing unrelated wallet or session data.

We store transaction references, timestamps, status labels and related account records needed to match payments. We do not need your wallet PIN, one-time code, or full app login details, and support will not ask for them.

Contact us through live chat, email, or account message with the data you want corrected and a matching account identifier. We confirm the request through your registered email, phone ending, or recent account step before updating anything.

Device and browser logs help us recognise sign-in patterns, spot unusual account access and troubleshoot privacy requests. For example, Android Chrome and desktop Safari sessions may show different cookie behaviour, so we record enough to investigate.

Yes. You can clear cookies through your browser settings, such as Chrome Settings > Privacy and security > Clear browsing data. After removal, you may need to sign in again and reset language or session choices.

We keep privacy-related support messages while they are needed to answer your request, prove the action taken, or meet record needs that apply to the account. Older records are removed or reduced when no longer required.

Only staff who need the request for account, wallet, security or support handling can access it. We limit internal access by role, and we avoid sharing unrelated details when a question can be answered with a narrower record.