Reference

surat666 Privacy Policy For Your Account

surat666 Privacy Policy explains how we collect, use and protect data when you open an account, verify your phone or reach the lobby from a mobile device.

Clear data purposesPayment status contextAccount access controlsCookie choices
surat666 surat666 Privacy Policy For Your Account
CONTACT OUR TEAM

Check Privacy Questions Through Support

A clear support path helps you ask what data we hold, why an account step is needed or how to request a correction. Use the support route connected to your account rather than sending sensitive details through an unrelated channel. Include your account identifier and a short description of the request; for payment questions, mention whether the reference relates to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We will use the details needed to locate the case.

Team online

Account data request

Ask through the account support path when you want to know which registration details, phone verification records or login events are connected with your account. We may ask you to confirm account ownership before discussing those records, so another person cannot request data on your behalf.

Payment privacy check

For a privacy question about a DANA, OVO, GoPay or QRIS reference, share the transaction context without sending a password or full security code. Our team can match the account case, check the displayed payment state and explain which record is relevant to your request.

Correction or deletion

Use support when a name, phone detail or other account field needs correction, or when you want to ask about removal. We assess the request against account security, open cases and legal duties, then explain what can be changed and what must remain stored.

DATA HANDLING

Browse How surat666 Handles Privacy

Our privacy process follows the practical steps you meet on the site: account creation, phone verification, login, wallet selection and support follow-up.

Account records

We collect details you enter during the account path, such as contact data and verification results. These records let us identify your account, complete the phone check before access and respond when you ask about a login or account field.

Device signals

When you move from login to the lobby on a phone or desktop, we may record technical signals such as browser type, device pattern and session time. We use them to investigate unusual access and maintain account security, not to request unrelated device content.

Cookie choices

Cookies can keep essential session functions working and remember a choice made during your visit. You can manage cookies through your browser settings, although removing required cookies may affect login continuity or the route from your account to the lobby.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference, amount and status record tied to the relevant account action. We use that record to reconcile the request and answer a status question without storing a wallet password.

Account protection

Phone verification, sign-in checks and case ownership checks help prevent another person from opening your account data. Keep your login details private, and contact support promptly if a device path or account event looks unfamiliar.

Storage and requests

We retain records for the period needed for account operation, security checks, dispute handling and legal duties. You can ask about access, correction or deletion through support; we may retain limited records when removal would conflict with those duties.

Find Answers About Privacy Policy

These Privacy Policy answers address the account questions you are most likely to have before using surat666 from Indonesia. They cover the data connected with access, cookies, phone verification, local payment references and requests sent through support. If your case involves a particular DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, include that context when contacting us so we can locate the relevant account event.

It covers data connected with your account, phone verification, login events, device signals, cookies, support messages and payment references. We explain why each category is used for access, security, account assistance or status checks, with eligibility depending on local law.

We may keep a payment reference, account link and status for a DANA, OVO, GoPay or QRIS request. This helps us reconcile the account action and answer your case. We do not ask for or store your wallet password through the privacy process.

Yes. Send an access request through the account support path and include your account identifier. We verify ownership before discussing records, then explain the data categories connected with your account and any limits that apply to security or legal retention.

Contact support with the account field you believe is inaccurate and the corrected detail. We may request phone or account verification before changing it. Payment references and security records may require a separate check because they document a past account event.

Yes. Cookies can support the session between phone verification, login and the mobile lobby, and may remember your selected setting. Browser controls let you remove or block them, but required cookies may affect the account path or page continuity.

We keep records for as long as needed to operate the account, review security events, resolve payment cases and meet legal duties. When you ask about deletion, we assess each category and explain whether a limited record must remain stored.

Use the support route connected with your account and state that your question concerns the Privacy Policy. Mention your account step or payment reference if relevant. Access and eligibility are handled where local law permits, including for requests from Indonesia.