Reference

How We Protect Your Privacy at cair33

We built our privacy framework around the way you actually use your account — from DANA deposits to withdrawal requests and everything between.

Data Collection TransparencyAccount-Level EncryptionPayment Info HandlingYour Rights Explained
cair33 How We Protect Your Privacy at cair33
DATA HANDLING FRAMEWORK

How cair33 Manages and Secures Your Information

Privacy is not a single checkbox — it covers collection, storage, use, sharing, retention and deletion. Below are the six pillars of our approach, each describing a concrete practice rather than a vague promise. We apply these consistently whether you access us from Surabaya on mobile or from desktop anywhere else in eligible regions.

Data Collection

We collect only what we need: name, contact details, payment wallet IDs for DANA, OVO or GoPay, and device identifiers. We do not request unnecessary personal documents beyond what identity verification requires at the account level.

Cookie Usage

Our site uses cookies to maintain your logged-in session and remember display preferences. Analytics cookies help us understand traffic patterns — they do not track you across unrelated websites. You can clear cookies from your browser settings at any time.

Account Security

Passwords are hashed and never stored in plain text. Transaction confirmations pass through OTP or PIN verification on your registered device. If we detect a login from an unfamiliar location, we flag it and may ask you to re-verify via SMS.

Data Retention

Transaction records tied to DANA, OVO or GoPay deposits stay on file as long as local compliance obligations require. Marketing preference logs and session data have shorter retention windows and are purged on a scheduled cycle.

Third-Party Sharing

We share data only with payment processors (to complete your transaction) and infrastructure providers (to host the platform securely). No personal data is sold or passed to advertisers. Contractual obligations bind those partners to comparable data-handling standards.

Your Rights and Requests

You may request a copy of the data we hold on you, ask for corrections to inaccurate details, or instruct us to delete your account data. Contact our support team through live chat or email — we aim to respond within a reasonable timeframe.

PRIVACY CONTACT PATHS

Reach Us About Your Data

If you have a question about how your personal information is handled — or want to submit an access, correction or deletion request — we have dedicated channels for privacy-related queries. Our support team in Indonesia can assist directly through the routes below.

Team online

Live Chat

Open the chat widget from any page on the site. Let the agent know your query relates to privacy or data access. They will escalate to the data team if the request involves account records, transaction history or identity documents you previously submitted.

Email Channel

Send your privacy request to our support email. Include your registered username and a brief description of what you need — whether that is a data export, correction of personal details, or a full deletion request after account closure.

Account Settings

Some privacy actions are self-service. Log in, open your profile section, and you can update your phone number, change your email, or revoke marketing communication consent without waiting for agent assistance.

Common Questions About Your Data and Privacy

Real questions we receive from account holders about how their information is treated. Each answer addresses the privacy angle directly.

We collect your full name, email, phone number and a password you set. If you deposit via DANA, OVO or GoPay, the wallet reference for that transaction is also stored so we can match it to your account for withdrawal verification later.

No. We never ask for your e-wallet password or PIN. We only receive a transaction confirmation token from the payment provider once a deposit or withdrawal is processed. Your wallet credentials stay entirely within the DANA, OVO or GoPay app on your device.

Open live chat or email our support channel. State that you want a personal data export and provide your registered username. Our data team compiles the relevant records — profile info, transaction history, communication logs — and delivers them in a readable format.

Yes. Submit a deletion request through live chat or email. Once verified, we remove your profile and personal details. Certain transaction records may be retained where local law requires, but they are no longer linked to an active profile or accessible externally.

We use session cookies to keep you logged in and analytics cookies for site performance monitoring. You can disable or clear cookies through your browser settings — though doing so may log you out or reset display preferences until you log in again.

We do not sell or share your personal data with advertisers. The only parties who receive any data are our payment processors (DANA, OVO, GoPay) to handle transactions, and hosting infrastructure providers who are contractually bound to keep your data confidential.

Passwords are hashed using a one-way algorithm before storage. Even our internal team cannot see your actual password. If you forget it, the reset process sends a verification code to your registered phone number or email — a new hash is then created.

Inactive accounts retain their data until you request deletion or until a scheduled retention period expires. We may send a reactivation reminder to your email. If you prefer earlier removal, contact support and we will process a deletion request for you.

Log in, go to your account profile settings and update the field directly. For security, a confirmation code is sent to the old contact method before the change is finalised — this prevents someone else from redirecting your communications without your knowledge.

Yes. Whether you access cair33 through a mobile browser or save the site to your home screen, the same data-handling rules apply. Device identifiers collected on mobile follow the same retention and deletion practices described in this policy.