Reference

Privacy Policy For Your pencetwin Account

Our Privacy Policy explains how we collect, use and protect details connected with your pencetwin account, including phone verification, device signals and wallet records.

Clear data purposesWallet record contextAccount change requestsMobile and desktop access
pencetwin Privacy Policy For Your pencetwin Account
PRIVACY HELP ROUTES

Get Policy Help Near Account Access

A clear contact route matters when a privacy question appears beside a login or wallet status issue. We keep policy requests tied to the account details you provide, so we can locate the relevant record without asking you to send unnecessary personal data. From Yogyakarta to Jakarta, use the support path shown after account access and describe whether your request concerns a phone number, device record, cookie choice or DANA transaction reference. We may ask for an account step to confirm that the request comes from you.

Team online

Account privacy request

Use the support path available after you sign in and state the exact Privacy Policy request, such as correcting a phone number, checking stored account details or asking how a device record is used. We will use the details needed to identify your account.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrect, include the transaction reference and approximate time rather than sending unrelated documents. This lets us trace the payment record, check its account link and respond with a focused privacy explanation.

Sign-in data concern

When a mobile or desktop sign-in looks unfamiliar, tell us the device type, approximate time and account step where it occurred. We can use those clues to check access activity and explain the security action without exposing another account's details.

DATA HANDLING

What We Do With Your Account Details

Our handling process follows the same account flow you see on screen: create an account, verify the phone number, sign in, and then use the available wallet or lobby areas where local…

Account creation

When you open an account, we collect the details needed to create and maintain that account. Phone verification connects the submitted number with the sign-in process, while the Privacy Policy explains why each required field is used.

Cookie choices

Cookies can keep a session active, remember a language or preserve a security preference on the device you use. You can manage browser settings, although removing essential cookies may require another sign-in before account areas load.

Device signals

A phone, tablet or desktop browser may provide technical signals such as device type, browser details and sign-in time. We use these signals to spot unusual access patterns, not to treat every new device as a policy breach.

Wallet records

Payment references, selected rail and status can be retained when you check DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. These records help us connect a wallet event with the correct account and resolve a disputed status.

Retention periods

We keep personal data only while it supports account operation, security checks, payment reconciliation, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct account details, explain a data use, provide relevant records or remove eligible information through the support path. We may verify your phone or account step first, then confirm what action we can take.

Privacy Policy Answers For pencetwin

These questions address the privacy points most often raised before opening or using an account. Each answer stays focused on account data, device handling, wallet records and the route for asking us to make a change. If your situation is not covered, use the account support path and describe the specific record or access step involved.

It covers data connected with your account, including phone verification, sign-in activity, device signals, cookies, payment references and support requests. It also explains our purposes for using that data, how retention works and how you can ask for correction, access or removal where eligible.

Phone verification links the number you provide with your account access and helps us confirm a change request belongs to you. It may also help us investigate an unfamiliar sign-in. We use the number for those account and security purposes described in the Privacy Policy.

Yes. The policy covers payment references, selected rail, status and timing connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those details to reconcile an account event and handle a status question.

When you sign in from a phone or tablet, technical details such as device type, browser information and access time may be recorded. We use them to support session security and detect unusual patterns. The Privacy Policy does not treat a new device as proof of wrongdoing.

You can request correction through the support path after signing in. Tell us which detail is wrong, such as a phone number or wallet reference, and include only what is needed to locate it. We may confirm an account step before applying or explaining the change.

Retention depends on why the record exists. Account, security, payment reconciliation, dispute and legal records may remain while that purpose applies. Afterward, we remove the data or separate it from direct account identifiers, subject to any continuing legal or security need.

Sign in and use the account support path, then identify the topic clearly: cookies, device activity, phone verification, wallet status or a data change request. We may ask for a reference or account step so we can answer about your record without exposing another account.