Reference

pedia77 Privacy Policy for Your Account

Our Privacy Policy explains how pedia77 handles the account, wallet and device details connected with your access to the lobby.

Account dataWallet statusCookie choicesAccess requests
pedia77 pedia77 Privacy Policy for Your Account
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact route matters when you want to understand a record or correct an account detail. We keep privacy questions separate from general lobby requests, so you can explain the issue without sending payment credentials or a full wallet password. Use the contact route shown in your account area and include the email or phone detail attached to your pedia77 account. We will use that reference to locate the relevant record.

Team online

Account contact

Send a Privacy Policy question through the account contact route and identify your registered phone number. We can then match the request to your account without asking you to share a wallet PIN.

Wallet record

For a DANA, OVO, GoPay or QRIS record, include the payment reference and approximate date. We use those details to check status while limiting the personal data included in your message.

Access concern

If a login or phone verification issue affects your privacy request, tell us which device path you used. A mobile browser or desktop session detail can help us check access safely.

DATA HANDLING

Inside pedia77 Privacy Controls

We handle this policy area through defined account steps rather than broad promises. Phone verification helps connect access requests to the right account, while session checks help us spot activity that does…

Collected details

We may handle your account identifier, phone verification result, contact messages, device session details and payment references from DANA, OVO, GoPay, QRIS or bank transfer.

Cookie controls

Cookies help remember sign-in and preference choices across a mobile browser or desktop session. You can adjust browser controls, although removing necessary cookies may affect account access.

Account security

We use phone verification, session checks and access records to protect your account. Never place a wallet PIN, password or full payment credential inside a support message.

Retention timing

We keep records only for the account, security, support or payment purpose that requires them, subject to unresolved requests and applicable local requirements.

Correction requests

You can ask us to correct an inaccurate contact or account detail. Include the registered phone number and the specific field you want changed so we can verify the request.

Data questions

For a copy, explanation or deletion request, use the account contact route and describe the record involved. We may need an account step before disclosing personal data.

Privacy Policy Questions Before Access

These answers address the privacy searches we hear most often before an account is opened or a wallet is connected. They explain the practical steps around data, cookies, payment references and account requests, so you can decide how to proceed where local law permits.

It covers account details, phone verification, device sessions, cookies, support messages and payment references connected with pedia77 access. It also explains why we use those records and how you can contact us about them.

Yes. The Privacy Policy covers DANA and QRIS references used to match a cashier request with your account. We need the transaction reference to check status, but you should never send a wallet PIN.

Phone verification helps us connect an access or data request to the correct account and identify unusual sign-in activity. The verification result is handled as an account security record under this Privacy Policy.

We may record technical session details from the mobile browser or desktop path you use, including security events and cookie choices. These details help maintain access and investigate activity that does not match your account.

You can contact us through the account route to request an explanation, copy or correction where applicable. Include your registered phone number and describe the record; we may verify account ownership first.

Retention depends on why the record exists, such as account security, support, payment checking or an unresolved request. We remove or stop using records when that purpose no longer requires them, subject to applicable requirements.

Use the contact route shown inside your account and label your message as a Privacy Policy request. Add the relevant account detail or payment reference, but leave out passwords, wallet PINs and full credentials.