Reference

one55 Privacy Policy for Your Account

Your account details, wallet status and device choices stay connected to a clear Privacy Policy on one55.

Account clarityWallet contextCookie choicesPhone verification
one55 one55 Privacy Policy for Your Account
ASK OUR TEAM

Get Privacy Help Beside Your Account

A clear contact route helps when you want to understand a record, correct an account detail or ask why a wallet status appears in your history.

Account contact Send your privacy question through the contact route connected with your account. Include the email or phone detail used for verification, and we can locate the relevant record without asking you to share a password or wallet PIN.
Wallet query For a DANA, OVO, GoPay or QRIS record, include the date, amount reference and displayed status. We use those details to check the one55 transaction entry while avoiding a request for your full wallet credentials or security code.
Access concern If a new phone or browser changes your account access, tell us which device path you used and when the issue appeared. We can review the sign-in event and explain the privacy or security reason without exposing another account's data.
HOW WE HANDLE IT

Privacy Controls You Can Use

We treat privacy as an account process you can question, not a hidden setting. The sections below explain the practical controls around records, cookies, account security, retention and change requests.

Collected account data

We use the details you submit for account creation, phone verification, sign-in recovery and support. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account help us match a wallet event to your account without collecting unrelated financial activity.

Device and session signals

A phone, tablet or desktop browser may provide session time, device type and security signals. These details help us spot an unfamiliar sign-in or repeated access pattern; they do not give us the contents of other apps, messages or files on your device.

Cookie preferences

Cookies can keep your selected language, account session and page settings available between visits. You can manage cookie controls in your browser, though restricting some cookies may require another sign-in or remove saved preferences from the Privacy Policy page.

Account protection

We may ask for phone verification before account access or when a security check is triggered. Never send us your password, wallet PIN or one-time code. If a login attempt was not yours, contact us through the account route and mention the device used.

Retention choices

We keep account, security and transaction references for as long as needed for service records, dispute handling, fraud checks or legal duties. When a record no longer serves those purposes, we delete it or limit its use under the rules that apply.

Change or deletion request

You can ask us to correct a wrong phone detail, clarify a stored record or request deletion where local law permits. We may verify account ownership first, then explain any record that must remain for security, payment reconciliation or a legal requirement.

Privacy Policy Answers For one55

These answers address the searches we hear most often about the one55 Privacy Policy. Each response stays focused on your account records, device access, cookies, wallet references and the steps available when you need a correction or explanation.

The one55 Privacy Policy covers account details, phone verification, sign-in and device signals, cookie preferences, support records and payment references. It explains why we use each category, how long records may remain, and how you can ask for access, correction or deletion where local law permits.

No. We use a payment reference and displayed status to reconcile activity involving DANA, OVO or GoPay, but you should never send a wallet PIN or one-time code to us. The Privacy Policy does not change your wallet provider's own handling of those credentials.

A device type, browser session and sign-in time can help us identify an unfamiliar access attempt. The Privacy Policy explains this security use. We do not use that signal to read files, messages or content inside other applications on your phone, tablet or computer.

Use the contact route connected with your account and identify the detail that needs correction, such as a phone number or email address. We may verify ownership before changing it. Our Privacy Policy allows correction requests, subject to security checks and applicable law.

You can request deletion through the account contact route where local law permits. We may need to retain limited account, security or transaction references for dispute handling, payment reconciliation or legal duties. We will explain the reason if a record cannot be removed immediately.

Cookies may remember your sign-in session, language and page settings. You can adjust them in your browser, but restricting necessary cookies may cause another login or remove saved choices. The Privacy Policy explains these uses without linking cookies to unrelated activity on your device.

Send the concern through the contact route connected with your account and include a short description, the relevant date and any displayed reference. Do not include your password, wallet PIN or one-time code. We can then review the record and explain the next step.