Reference

formasiqq Privacy Policy for Indonesia Accounts

The formasiqq Privacy Policy gives you a clear record of what we collect when you verify your phone, access the lobby or use DANA, OVO, GoPay and QRIS.

Phone verification recordsWallet transaction referencesCookie controlsData request path
formasiqq formasiqq Privacy Policy for Indonesia Accounts
CONTACT OUR TEAM

Three Paths for Privacy Requests

A privacy request starts from the screen connected to the record you want us to check. Use the account help path for profile data, the cashier support path for DANA or QRIS references, and the phone verification screen for number corrections. Tell us whether you seek access, correction or deletion, then provide enough account detail for us to confirm that the request belongs to you without sending wallet credentials.

Team online

Account data request

Open the help path inside your account and identify the profile fields or activity period involved. We confirm account ownership before preparing a copy or applying an eligible change.

Payment record query

Use the support path beside the cashier when a DANA, OVO, GoPay or QRIS reference is involved. Include the transaction time and reference, but never send wallet passwords.

Phone number correction

Head to the phone verification screen when your registered number is wrong or outdated. Our account checks must be completed before we replace a number linked to access controls.

OUR HANDLING CONTROLS

Six Controls Around Your Account Data

Account data stays connected to a defined purpose rather than being collected without context. We separate profile records, payment references, cookie settings and lobby activity so requests can be handled against the…

Data collection

We record details needed to create and secure your account, including your verified phone number, identifiers and access events. Cashier activity adds transaction references and status records, not your wallet password.

Cookie choices

Cookies keep your session active, remember selected settings and help us detect unusual access. Where controls are available, you can adjust optional cookies through your browser while necessary session cookies remain active.

Account protection

Phone verification connects access changes to the registered number. We also use device and sign-in records to investigate unusual activity before processing sensitive profile corrections or data requests.

Payment references

DANA, OVO, GoPay and QRIS transactions create references used for receipt matching and status checks. We share required transaction fields with payment processors while wallet authentication stays on their systems.

Retention decisions

We keep each record only for its operational or legal purpose, which may include account security, payment reconciliation and dispute handling. Different record categories can therefore have different deletion dates.

Correction requests

You can ask us to correct inaccurate profile data through the account help path. We verify your identity first and may retain an audit record showing that an authorised change occurred.

Seven Privacy Policy Answers Before Account Access

Clear answers help you decide what account data you are prepared to provide. These questions cover phone verification, DANA and QRIS records, cookies, lobby activity, correction requests and retention after closure. They also show which account or cashier path to use when you contact us. Read the formasiqq Privacy Policy before opening an account, then return to it whenever your device, wallet or registered phone number changes.

Yes. The Privacy Policy covers transaction references, payment status, time records and account matching for DANA, OVO, GoPay and QRIS. Your wallet provider separately handles its authentication credentials.

It describes profile fields, your verified phone number, account identifiers, device and browser data, IP address, cookie choices, access events, payment references and activity records connected to your account.

Open the account help path, specify the data categories or date period you need, and complete the ownership check. We may ask for account details needed to prevent disclosure to another person.

Yes, where the change can be verified. Start from the phone verification screen and complete the account checks. We may preserve an audit record of the authorised correction for security purposes.

We use cookies for active sessions, saved settings, security checks and service measurement. Your mobile browser provides controls for optional cookies, although disabling necessary session cookies can interrupt account access.

Retention varies by record purpose. Payment references may remain for reconciliation or disputes, while security and profile records remain as required for account operation, legal duties and verified request handling.

You can submit a deletion request through the account help path. We assess it against applicable duties and may retain limited records needed for payment reconciliation, security incidents, disputes or legal requirements.