Reference

Open lipgloss Privacy Policy Before Account Access

lipgloss Privacy Policy explains what we collect when you create an account, complete phone verification and browse from a mobile browser or desktop.

Clear data purposesWallet-aware handlingPhone verification contextCookie choices
lipgloss Open lipgloss Privacy Policy Before Account Access
PRIVACY HELP

Contact Us About Your Privacy Policy Questions

A clear support path helps when a Privacy Policy request is harder to identify than a normal account question.

Account request For a copy, correction or deletion request under our Privacy Policy, contact us through the support path shown after account access. Include your registered contact detail and the specific record you want us to locate.
Wallet reference If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, add the receipt reference and date. We use those details to separate a wallet-status query from a request about personal data.
Device concern When a mobile browser or desktop sign-in looks unfamiliar, tell our support team which device path you used and when it appeared. We can explain the account-security step without asking you to share a password.
DATA PRACTICE

Explore Privacy Controls For Your lipgloss Account

We handle Privacy Policy requests through the account context that created the data, which helps us avoid sending personal records to the wrong person.

Collected account data

We may hold the contact details you submit, phone verification status, sign-in records and preferences connected with your account. These fields let us identify your profile and respond to a Privacy Policy request without relying on a public name alone.

Cookie handling

Cookies and similar browser storage can remember a session or help us understand a device path. Your browser settings provide a control point, although changing them may affect sign-in continuity or the way account pages load.

Account protection

Phone verification and device signals help us notice an unusual access pattern. We do not ask for your password in a support reply. If a sign-in concern involves a mobile browser, describe the device path rather than sending secret credentials.

Wallet records

Payment references can appear beside account events when DANA, OVO, GoPay, QRIS, bank transfer or a virtual account is used. We use the reference to check status and resolve a receipt question, not to request your wallet password.

Retention choices

We keep records only for the stated account, security, reconciliation or support purpose and assess when they are no longer needed. A deletion request may have limits where a record is required for an unresolved account or legal duty.

Your request route

Ask for access, correction, objection or eligible deletion through the support route inside your account. Tell us which data category you mean, such as phone verification or QRIS status, so we can check identity and respond accurately.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the account and wallet questions we expect from people in Indonesia. They explain the practical route for checking stored data, changing a detail or raising a device concern before you open an account. If your situation is not covered, use the support path connected to your profile and describe the exact record or event.

The lipgloss Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support requests and payment-status references. It explains why we use each category, how retention is assessed and how you can request access, correction, objection or eligible deletion.

Use the support route inside your lipgloss account and ask for access to your personal data. Include the contact detail linked to the account and name the category you need, such as phone verification, cookie records or a QRIS status reference.

Yes. The Privacy Policy covers payment references connected to account activity, including DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records. We use these references for status checks, receipt questions and account reconciliation rather than wallet-password access.

You can ask us to correct inaccurate account details through the support route shown in your profile. State which field is wrong and provide the contact detail used for phone verification. We may check identity before changing data linked to account access.

On a mobile browser, cookies or similar storage may keep a session active and help connect security events to your account. Browser controls let you clear or restrict them. Removing necessary storage can require another sign-in or affect page loading.

You may request eligible deletion through the account support path. We first verify the request and identify the records involved. Some data may remain where needed for account security, wallet reconciliation, unresolved support matters or a requirement that depends on local law.

The available rights and any limits depend on local law. We apply the Privacy Policy to requests from Indonesia and explain the relevant next step after checking your account context. Send the request through support with the data category and contact detail involved.