Reference

Privacy Policy For Your food66 Account

food66 Privacy Policy explains how we handle the details you provide when you open an account, verify your phone, access the lobby and use wallet options in Indonesia.

Account clarityWallet dataDevice accessContact requests
food66 Privacy Policy For Your food66 Account
HELP WITH PRIVACY

Get Policy Help Before Account Access

A direct support request gives you a practical way to ask about the Privacy Policy before you open an account or while you use the lobby.

Account request Use the account contact path when you want to ask what personal details are…
Wallet record For a DANA, OVO, GoPay or QRIS privacy question, provide the payment reference rather…
Device access If a mobile browser or desktop session appears unfamiliar, contact us with the device…
DATA HANDLING DETAILS

What You Can Ask Us To Change

We keep this Privacy Policy tied to actions you can take: ask what data we hold, request a correction, question a payment record or ask how a device…

Data collected

We may handle account contact details, phone verification results, login activity, device signals and payment references for DANA, OVO, GoPay…

Cookie choices

Browser cookies or similar storage can help keep a session working and remember a choice made on the site.

Account security

Phone verification and session checks help us distinguish your account access from an unfamiliar sign-in.

Payment records

A payment reference can connect a wallet or bank action with the correct account status.

Retention questions

You can ask how long a category of account, device or payment data is retained.

Change requests

Send a clear request when your phone, email or other account detail needs correction.

Privacy Policy Answers For food66

These Privacy Policy answers address the account and wallet questions we expect you to ask before using food66 in Indonesia. Each answer stays focused on personal data, access, security, retention and contact requests. If your situation is unusual, use the support path with a specific account step or payment reference so we can respond to the right record.

It covers data connected with your account, phone verification, login sessions, device access, support requests and payment references. That includes activity involving DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes when those details are needed to provide access or check account security.

Phone verification helps us confirm an account access request and reduce confusion when a session or wallet action looks unfamiliar. We use the result for account security and access checks. If you want to ask about a specific verification record, contact us privately with your account detail.

Use the private account contact path and state which detail is wrong, such as your phone or email, plus the corrected value. We may confirm that you control the account before making a change. The correction process depends on local law and the record involved.

Yes. The policy covers payment references and status details used to connect DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity with your account. Send a reference, not a password or wallet PIN, when asking us to check a payment record.

We may use device signals and cookie storage to keep a session working, remember a site choice and identify an unfamiliar login. The exact data depends on your browser path. You can ask which device or cookie detail relates to a reported access issue.

You can submit a deletion request through the account contact path. We first verify the request and then assess the records involved, including security and payment records. Whether deletion is available depends on local law and any retention duty connected with the account.

Contact us through the support path and identify the policy topic, account step, device type or payment reference involved. Keep passwords, wallet PINs and one-time codes private. We use your description to route the request and explain the applicable Privacy Policy section.