Reference

tailwindcss Privacy Policy for Your Account

The tailwindcss Privacy Policy explains what we collect when you open an account, check wallet status, or move from login to the lobby.

Clear collection purposesWallet record controlsCookie choicesAccount access requests
tailwindcss tailwindcss Privacy Policy for Your Account
HELP WITH PRIVACY

Three Ways to Ask About Your Data

A clear contact route helps when your Privacy Policy question concerns a phone number, wallet reference, cookie choice, or account record.

Account data request Use the account support route to ask what personal data is linked to your…
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the transaction date, status shown…
Correction or removal Ask us to correct inaccurate personal data or review a removal request through the…
DATA HANDLING

How tailwindcss Applies This Privacy Policy

Privacy depends on practical controls, not just a page of legal wording. We separate account identity from payment references where the service allows, limit internal access to people who need a record…

Account details

We use the phone or account details you provide to create access, verify ownership, and respond to account requests. If a detail changes, tell us through support rather than opening a second profile. We may keep a request record to show how it was handled.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account records are handled as transaction references for status checks and account matching. We do not need your wallet PIN or banking password for a support request. Share only the reference details visible in your account.

Cookies and devices

Cookies can keep your session active and remember choices made in the browser. Device and browser signals can help us spot an unusual login. You can adjust cookie settings in your browser, although some account functions may require essential session cookies to work.

Account security

We may ask for phone verification before giving account-specific data or changing sensitive details. This step helps prevent a third party from taking over a profile through a support request. Do not share your password, wallet PIN, or verification code with anyone contacting you.

Retention choices

We keep personal data for the period needed to provide the requested service, resolve disputes, protect account security, or meet a legal duty. A removal request may not erase records that must remain for those reasons. We explain the applicable reason when a request cannot be completed.

Your requests

You can ask for access, correction, or review of eligible personal data by using the support path connected with your account. Describe the request clearly and include a safe account identifier. Where local law permits, we assess it and may request proof that you control the account.

Privacy Policy Questions About Your Account

These answers focus on the questions we expect you to have before opening an account or sending a wallet status request. If your situation is specific, refer to the full Privacy Policy and contact support through the account path. Access and eligibility depends on local law, including the rules that apply to your location.

The Privacy Policy covers account and phone details, verification events, login and device signals, cookie choices, support messages, and payment references. It explains why we use each category, how long records may remain, and how you can request access or correction where local law permits.

Phone verification helps us confirm that you control the account before we discuss personal data or change sensitive details. It also supports account security when a login or support request looks unusual. We will not ask you to disclose a password, wallet PIN, or verification code.

Yes. The Privacy Policy covers DANA and QRIS references used to match a payment status with the correct account. It also covers OVO, GoPay, bank transfer, and virtual account references. These records are used for status checks, support, security, and applicable legal duties.

Use the support path inside your account and ask for an access request. State the registered phone number or another safe account identifier, then describe the records you want checked. We may verify account ownership before sharing personal data, and the outcome depends on local law.

You can request correction of inaccurate account data or ask us to review removal of eligible records through support. We may retain some information for account security, dispute handling, or legal duties. Where local law permits, we explain the reason if a request cannot be fulfilled.

Essential cookies can keep your login session and account path working, while other cookies may remember browser choices or help us identify unusual access. You can adjust browser settings or available cookie controls. Removing essential cookies may require you to sign in again or limit account functions.

The policy describes how we handle data for the Indonesia account and wallet paths, including DANA, OVO, GoPay and QRIS references. Access or eligibility depends on local law. If a local rule gives you additional rights, contact support and identify your location for a relevant response.