Reference

Privacy Policy For Your fatcai Account

Our Privacy Policy explains how fatcai collects, uses and protects details linked to your account, including phone verification, wallet status and device access.

Account clarityWallet recordsCookie choicesSupport requests
fatcai Privacy Policy For Your fatcai Account
HELP WITH PRIVACY

Contact Us About Policy Requests

A direct support route helps you ask what we hold, why we use it or how to correct an account detail.

Account support Use the signed-in support path for a Privacy Policy request about your phone number, verification record, session history or account access. We first match your request to the account step you name, then explain the available correction or access route without asking you to post private details publicly.
Wallet checks If your request concerns DANA, OVO, GoPay or QRIS data, attach the relevant receipt reference rather than a full wallet password or PIN. We use the reference to locate the payment record, check its status and answer the Privacy Policy question connected to that transaction.
Policy contact For a copy of your stored account details, a correction request or a question about retention, contact us through the support route during 09:00–23:00 Western Indonesia Time. We may verify ownership before releasing account-linked details, which keeps the request tied to you.
DATA HANDLING DETAILS

What We Do With Your Account Data

We keep this Privacy Policy connected to the account actions you actually take. A phone verification event, wallet status check or sign-in from a new device can create a record because each…

Account details

We use your account details to create access, complete the clear phone verification step and respond to requests tied to your account. We limit support conversations to the details needed for the question, and we do not ask you to send a password, wallet PIN or full authentication code.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt to an account request. We use these records to check status, resolve a mismatch and support account administration; the reference is not a request for your private wallet credentials.

Cookies and sessions

Cookies can keep your sign-in session and selected settings working across the page. We also use session data to identify a broken login path or repeated sign-in attempt. You can manage cookies in your browser, although switching them off may require you to sign in again.

Device protection

When you move from a mobile browser to desktop, device and access signals can help us spot an unusual session and protect your account. They support security checks around login and phone verification; they are not a substitute for your password, and you should close shared-device sessions.

Retention approach

We keep each category only for the period needed for its stated purpose, account support, dispute handling or applicable requirements. A wallet receipt may need a different retention period from a cookie record. Ask support which category applies and we will explain the available retention response.

Changes and access

You can request access to account-linked data, ask us to correct inaccurate details or raise a question about use through signed-in support. We verify the request before making changes, and eligibility for a particular request depends on local law and the account details available to us.

Privacy Policy Answers For fatcai

These Privacy Policy answers address the account questions you are most likely to have before opening or using fatcai in Indonesia. We cover the data connected with phone verification, wallet references, cookies, device sessions, correction requests and contact steps. The practical rule is simple: use the signed-in support route, share only the details needed to identify your request, and ask us to explain any record you do not recognise. Account access remains subject to local law.

The Privacy Policy covers account details, phone verification, sign-in sessions, cookies, device signals, support messages and payment references. It explains why DANA, OVO, GoPay, QRIS, bank transfer or virtual account records may be used when we check a receipt or resolve an account request.

Sign in and use the support path to request account-linked data. Include the phone number connected with your account and describe the category you want, such as verification or wallet references. We verify ownership first, then respond according to the Privacy Policy and local requirements.

Yes, you can ask us to correct an inaccurate account detail through signed-in support. State what appears wrong and what should replace it, but do not send your password or wallet PIN. We may complete an ownership check before applying a change to your record.

Yes. The Privacy Policy explains that DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account records, can help us match a receipt to your account. We use the reference for status checks and support, not as a request for wallet credentials.

Cookies can retain a sign-in session and selected settings, while session records help us investigate a broken login path. You can change cookie controls in your browser. If you block them, you may need to sign in again or repeat a phone verification step.

Retention varies by category and purpose. A payment reference used for a receipt check may be retained differently from a cookie or session record. Ask support about the category involved, and we will explain the applicable period or response where local law permits.

Use the signed-in support route between 09:00 and 23:00 Western Indonesia Time every day. Describe the Privacy Policy concern and include a relevant account step or receipt reference. We may verify ownership before discussing private details or changing an account record.