Reference

congor4d Privacy Policy For Your Account

Our Privacy Policy shows how congor4d handles the details connected with your account, including phone verification, login activity, DANA and QRIS records, and device signals.

Account dataWallet recordsCookie choicesAccess requests
congor4d congor4d Privacy Policy For Your Account
CONTACT PATHS

Where Privacy Questions Go First

A clear contact route helps you resolve a privacy question without repeating your account story. Use the support link beside your account and include the email or phone detail attached to your profile, plus the subject of your request. For a wallet question, add the DANA, OVO, GoPay or QRIS reference rather than sending a password or full payment credential. We will use the details you provide to locate the relevant record and explain the next step.

Team online

Account support link

Send a Privacy Policy question from the account support path so we can match your request with the correct phone verification record and avoid asking for unrelated personal details.

Wallet record query

For DANA, OVO, GoPay or QRIS questions, share the receipt reference and date shown on your record. We use those details to check status without requesting your wallet password.

Access request

Ask to see, correct or remove eligible account details through the same support route. We may first confirm account ownership before discussing private records or making a change.

SIX DATA CHECKS

How We Handle Your Account Records

Our privacy process follows the account actions you take, rather than treating every detail the same way.

Phone verification

Before account access, we use the phone detail you submit to confirm the account path. If that detail changes, contact support so we can explain the ownership check required for an update.

Login and device signals

Browser type, device indicators and sign-in activity can help us identify an unusual session. These signals support account protection and are reviewed alongside the account event that created them.

Cookie choices

Cookies can keep a session open or remember a setting on your browser. You can clear browser storage through device settings, although doing so may require another account sign-in.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt with an account event. We do not need your wallet password for that check.

Retention checks

We keep account, contact and transaction records for the account, security or dispute purpose stated in this Privacy Policy, then assess whether continued storage remains necessary.

Changes and contact

You may ask what personal details we hold, request a correction, or ask about deletion where available. We confirm ownership first and explain any local-law reason for retaining a record.

Privacy Policy Answers For congor4d

These questions focus on the privacy points you may want settled before opening an account. Each answer connects the policy to a real account step, device action or Indonesian wallet record, while access remains where local law permits.

The Privacy Policy covers account creation, phone verification, sign-in activity, cookies, support messages, device signals, and records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

Phone verification helps us confirm account ownership before access or a data change. It also gives our support path a matching account detail when you ask about login or stored records.

Yes. The Privacy Policy covers references connected with QRIS, DANA, OVO and GoPay activity. We use a receipt reference and date to check a record, not your wallet password.

Use the support link attached to your account and ask for an account data access request. Include your profile phone or email so we can confirm ownership before sharing private details.

You can request a correction through the account support path. Tell us which detail is inaccurate and provide the replacement; we may confirm your account before changing the stored record.

Cookies may retain a session or browser setting. Clearing them through your device or browser can remove that local storage, but you may need to complete account access again.

You can ask about removal through support, and we will check the relevant record. Some account, security or transaction details may need continued retention when local law requires it.