Reference

happympo Privacy Policy For Your Account

happympo Privacy Policy explains how we use the details you provide when opening an account, confirming your phone, or checking DANA and QRIS activity.

Account dataWallet recordsCookie choicesPhone checks
happympo happympo Privacy Policy For Your Account
ASK OUR TEAM

Check Privacy Help From Your Account

A privacy question should have a clear route, especially when a login or wallet record looks unfamiliar.

Account request Send an access, correction, or deletion request through the support path connected to your account. We may ask for an account detail to confirm that the request concerns your profile.
Wallet record If a DANA, OVO, GoPay, or QRIS reference needs checking, share the transaction reference rather than wallet credentials. We use the reference to trace the relevant account event.
Device concern For an unfamiliar phone, browser session, or login alert, tell us the device path and approximate time shown in your account. We can then review the security event with you.
HOW WE HANDLE IT

Explore How happympo Protects Account Data

We treat privacy as an account process rather than a decorative page. The same records that help us check a phone verification step or a wallet status can also help us resolve…

Data handling

We use contact details, verification events, device signals, and payment references for stated account, security, support, and legal purposes. We do not need your DANA or QRIS wallet password to check a record.

Cookie controls

Cookies can keep your sign-in path and selected settings available across pages. Your browser can restrict or clear them, although some account functions may then require another sign-in.

Account security

Phone verification, login signals, and device details help us identify unusual access. Never send a one-time code or wallet password in a support message, even when asking about privacy.

Retention period

We keep personal records for the stated purpose, account protection, dispute handling, or a legal requirement. When a record no longer needs to be retained, our process addresses its removal.

Change requests

You can ask us to access, correct, or remove eligible personal details through account support. Include the requested action and the phone number connected to your profile.

Policy contact

For a Privacy Policy question, use the support route shown after account access. Describe the data category, such as cookies, device history, or wallet references, so we can respond precisely.

Browse Privacy Policy Answers For DANA Users

These Privacy Policy answers address the account and payment questions you may have before opening access. We keep each response practical, from phone verification and cookies to QRIS references and requests for a copy of your data. If your situation is not covered, contact us through the account support path.

It covers account details, phone verification, device signals, cookies, support records, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

No. We may retain a payment reference or account status needed for support, but your wallet password and one-time code should remain with you and the relevant payment provider.

Open the support route from your account and request access to your personal data. Include your linked phone number and the categories you want checked, such as cookies or device events.

Yes, you can request a correction through account support. State which detail is wrong and provide the updated value; we may verify account ownership before making a change.

Cookies can retain sign-in continuity and selected settings when you use a mobile browser. You can clear or restrict them in your browser, but another sign-in may be required.

We retain information for its stated account or security purpose, support and dispute handling, or a legal requirement. When retention is no longer needed, our process addresses removal.

Use the support path shown inside your account and describe the relevant category, such as phone verification, device access, cookies, or an OVO transaction reference. Access depends on local law.