Reference

Privacy Policy for Your help123 Account

Your help123 Privacy Policy explains what we collect when you create an account, verify your phone and use the lobby from a mobile device or desktop.

Clear data purposesWallet record contextPhone verificationCookie choices
help123 Privacy Policy for Your help123 Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path matters when a Privacy Policy question affects your account or wallet status. Start from the support request route inside your help123 account and include the email or phone detail attached to the account, without sending a password or full payment credential. We use that account step to locate the right record, confirm the request is yours and avoid changing data for the wrong person. If you are in Medan or elsewhere in Indonesia, the same digital route applies where local law permits.

Team online

Account request

Use the support request route after signing in and identify the account email or verified phone number. We can then explain which personal data a Privacy Policy request concerns, ask for a suitable confirmation step and record the request against the correct account.

Wallet query

For a DANA, OVO, GoPay or QRIS record, include the transaction date and the visible reference shown in your account. Do not send a wallet PIN or complete credential. We use the reference to investigate the data record without exposing unnecessary payment details.

Access concern

If a phone verification or device sign-in blocks your policy request, mention the device path and the last successful account step. We can direct the request through account support while keeping authentication details private. Access remains subject to local law and available account checks.

DATA PRACTICES

How help123 Handles Privacy Details

We keep the Privacy Policy practical by linking each data type to a real account action: sign-in, phone verification, wallet status, lobby access or support contact.

Account data

We use your account details to create access, confirm the phone verification step and respond to requests made through the account area. We do not need a password in a support message. Keep your login details private so our records remain connected to your own account activity.

Cookies and devices

Cookies can retain a sign-in preference and help us recognise a changed browser or device path. On mobile, the same policy applies when you move from login to the lobby; on desktop, browser storage may support the same account checks. You can manage browser cookie settings.

Wallet references

A payment record may show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. We use that limited context to reconcile an account action or receipt. We do not ask you to place a wallet PIN or full credential in a support request.

Account security

Phone verification, sign-in records and device signals help us identify an unusual access attempt before account details are changed. If the account path looks different from your normal device, we may ask for additional confirmation. This protects the privacy request as well as the account itself.

Retention choices

We keep personal records for the period needed for the purpose described in the Privacy Policy, account security and applicable legal duties. A deletion request may not remove records that must be retained for those duties. We will explain the reason and the remaining retention period where available.

Changes and contact

To request a correction, access copy or deletion assessment, send the request through account support with the account email or verified phone reference. We may confirm ownership before acting. Our response will identify the relevant data category and explain any limit that depends on local law.

Privacy Policy Questions About help123

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They cover the data collected during account creation, the way cookies and device checks work, payment references, correction requests and access conditions in Indonesia. If your situation is not covered, use the account support route with your verified account detail so we can assess the request without asking for a password.

It explains how we collect account details, phone verification records, sign-in signals, device data and support messages. We use those categories to provide account access, protect the account, answer requests and connect wallet status to the right account. The stated purpose controls how each record is handled.

Yes. The Privacy Policy covers payment references and status records linked to DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account checks. When you ask about one, provide the visible receipt reference and date, never a PIN or complete wallet credential.

Sign in, open the account support route and state whether you want access to a data category or a correction. Include the account email or verified phone reference so we can confirm ownership. We may ask for another account check before disclosing or changing personal records.

Cookies and similar browser signals may remember a sign-in preference, support device recognition and help identify unusual access. The same Privacy Policy applies on a mobile browser and desktop browser. You can adjust cookie controls in your browser, although some account checks may then work differently.

Phone verification is used to confirm account access and help prevent an unauthorised person from changing account data. We may compare the request with sign-in and device signals before acting. Do not place verification codes in a support message; use the account request path instead.

We retain each category for the period needed for its stated purpose, account security or applicable legal duties. A deletion request can be limited when a record must remain for those duties. Through account support, we can explain the relevant category and any available retention detail.

The policy is written for the account and payment paths available in supported Indonesia access. Eligibility depends on local law, and the policy operates where local law permits. If you are unsure about a request from Semarang or another Indonesian location, contact support through your verified account path.