Reference

star303 Privacy Policy For Your Account

The star303 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and contact our support route.

Account dataWallet recordsCookie choicesPolicy requests
star303 star303 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you control the details connected with your account. Send a request through the policy contact form when you need a copy, correction or explanation; include your account email and the subject of your request, but do not send a wallet password or one-time code. If a DANA or QRIS reference appears in your message, we use it only to locate the relevant record and answer the privacy question.

Team online

Policy contact form

Use the contact form linked from this page for a Privacy Policy request. Tell us whether you want access, correction, deletion or a processing explanation, then include the account email used for your star303 sign-in.

Account access route

If you cannot reach your account after phone verification, contact us through the account help path rather than sending credentials in chat. We may ask for account details that help confirm the request belongs to you.

Wallet record query

For a privacy question about DANA, OVO, GoPay, QRIS or a bank transfer reference, name the payment rail and approximate date. Keep the full wallet number, password and verification code private.

DATA PRACTICE

Six Practical Privacy Commitments

We keep this policy tied to the actions you take, rather than describing data in vague terms.

Account details

We may collect your account email, phone verification result, sign-in activity and selected account settings. These details help us identify the right account when you ask to view or correct records connected with your access.

Device signals

Your browser or phone can provide device and session signals such as sign-in time, operating system and security events. We use them to spot unusual access and help protect the account without reading unrelated files on your device.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account transaction can leave a reference, amount status and timestamp in our records. We use that data to match a payment question, not to request your wallet password.

Cookies

Cookies can keep a session active, remember a language or help us understand which policy page was opened. You can adjust cookie controls in your browser, although blocking necessary cookies may interrupt sign-in or phone verification.

Retention

We retain account, security, support and payment records only for the period needed for the stated purpose, account protection or applicable legal duties. A deletion request is assessed against those duties before we confirm what can be removed.

Change requests

To request a copy, correction, restriction or deletion, use the policy contact form and identify your account email. We may verify ownership before acting, then explain the result and any reason a record must remain.

Privacy Policy Questions For star303

These answers address the policy questions we hear before an account is opened or a wallet is connected. They explain what to send, how we verify a request and why some records may remain available for a period. If your situation is not covered, use the policy contact form and mention the account step or payment reference involved.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, request verification and access conditions where local law permits.

The phone verification result helps us confirm that the person requesting account access or a data change is connected with the account. We record the verification outcome and related security event, not your private device files or unrelated phone content.

Use the policy contact form and provide the account email used for sign-in, plus a clear request for access. We may ask for an additional account check before sending details, so a copy is not disclosed to the wrong person.

Yes, send a correction request through the policy contact form and state which account detail is inaccurate. If the request concerns a DANA, QRIS or bank transfer reference, include its date and status while keeping passwords and verification codes out of the message.

Cookies can support sign-in continuity, language settings, security checks and policy-page measurement. Your browser controls can block or remove them. Necessary cookies may still be needed for account access, phone verification and keeping a secure session active.

You can submit a deletion request through the policy contact form. We first confirm ownership and check whether security, payment reconciliation or legal retention duties require part of the record to remain; we then explain the result in the reply.

The policy is written for access from Indonesia, including Semarang and Makassar, where local law permits. Local requirements can affect access, retention or available rights. Contact us with your account location if you need the applicable condition checked.