Reference

fast55 Privacy Policy For Your Account

fast55 Privacy Policy explains how we handle the details linked to your account, including phone verification, device access and wallet records from DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextRequest path included
fast55 fast55 Privacy Policy For Your Account
PRIVACY SUPPORT

Get Policy Help Beside Cashier

A clear support route helps when your Privacy Policy question concerns a wallet reference, phone verification or a device session.

Account data request Use the account support path to ask which personal details are connected with your fast55 profile. Include your account phone number so we can check identity before discussing records.
Wallet record question If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference looks unfamiliar, send the transaction date and visible reference through support. Do not share your wallet PIN.
Device access concern For a sign-in or session you do not recognise, contact support from the account route beside the cashier. We can check the device session and guide the next account-security step.
DATA HANDLING

How We Handle Your Policy Choices

Privacy work follows the same account path you use to reach the lobby: we connect a request to your verified account, check the relevant records and explain the result in plain English.

Account details

We use details such as your phone number and account identifiers to create access, confirm that a request comes from you and respond to policy questions. We do not need your DANA, OVO or GoPay PIN.

Wallet references

A payment record can contain a rail name such as QRIS, a bank transfer reference or a virtual account reference. We use that trail to reconcile account status, not to request private wallet credentials.

Cookies and sessions

Cookies and device session signals can help keep your sign-in path consistent between the account page and lobby. You can adjust cookie controls in your browser, although some account functions may then need another sign-in.

Account protection

Phone verification is part of account access because it helps us distinguish your request from an unauthorised attempt. Never send a password, wallet PIN or full payment credential through a support message.

Record retention

We retain account, security and payment-reference records for as long as needed to operate the service, resolve disputes and meet legal duties. The period can differ by record type and local-law requirement.

Changes and contact

Ask for a copy, correction or deletion through the account support route beside the cashier. We may request verification first, then explain what can be changed and which records must remain stored.

Privacy Policy Answers For fast55

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the practical path for data requests, device sessions, cookies and account verification, while keeping eligibility wording tied to local requirements. If your situation is not covered, use the account support route beside the cashier and describe the record you want us to locate.

The fast55 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use payment-rail names, visible references and status details to match an account action or resolve a receipt question. We do not ask for your DANA or QRIS PIN, and wallet credentials should never be sent to support.

Yes. Where local law permits, use the account support route beside the cashier and ask for the personal details connected to your profile. We may confirm your phone number or another account detail before sharing records.

Send a correction request through account support with the field you believe is wrong and the accurate replacement. We check the request against your verified account, update eligible records and explain any legal or operational reason a field cannot change.

We keep records for the period needed for account operation, security checks, dispute handling and legal duties. Retention can differ for phone verification, device sessions and payment references, so support can explain the category relevant to your request.

Yes. It covers technical signals from the browser or mobile device used for sign-in, including session details that help protect account access. Cookie controls remain available in your browser, though changing them can require another login.

Use the account support path beside the cashier and state whether your concern involves account data, a wallet reference, a cookie or an unfamiliar device session. Include only safe identifying details, never a password or wallet PIN.