766ok App Privacy Policy: Data Security and Cookie Rules

Card data tokenization and 766ok App

Card data is not stored directly; 766ok App tokenization is used, so secure references replace sensitive numbers, reducing checkout risk, and old data is not leaked when the session refreshes

Many Bangladesh users fund accounts with bKash or Nagad, so the payment flow is logged separately; for Dhaka, Chittagong, and Sylhet users, this process works the same way, though the verification steps may differ

PCI limit and 766ok Login verification

The verifications during 766ok Login are kept within PCI limits, meaning the full cardholder data is not shown, only the minimum required signals are seen, keeping account access and session security intact

In this setup, event logs may be stored for up to 30 days; if suspicious attempts are detected, the system stops the session, and may require extra verification in a later step

• Full card number is never exposed
• Login events are tracked separately
• Unauthorized sessions are detected quickly

Processor list and 766ok Register

During 766ok Register, the data sent is explained in plain language; if a payment processor is used, their own policies apply; for Bangladeshi users, information related to bKash, Nagad, and Rocket is shown in separate documents

Before creating an account you will see what data will be verified, how long it will be kept, and why records may be updated; this transparency is the core part of the policy

Quick points to note

1. Session identification data stored temporarily
2. Payment reference stored for a limited time
3. New device may require extra verification

Chargeback data and 766ok Download

During 766ok Download or App update, device identification data may be collected; in chargebacks or disputes, this record is used to verify, helping detect errors and enabling the support team to decide quickly

If the mobile network is weak, the system also retains requests that drop mid-way; in many areas of Bangladesh, 3G or less-stable connections, this risk log is very useful

Wallet data and cookie controls

If wallet-type data is present, it is kept in a separate table; cookies are used only for session, language, and quick navigation. You may block cookies from browser settings, but some features may be slower

In this section, tracking limits are kept very low, not profiling, but secure access and user preferences are prioritized here

Your rights and 766ok App settings

You can view, modify, and restrict data in the 766ok App settings; profile updates, session management, and notification controls are separated

If you want to delete data, the support team starts the process after verification; typically the request proceeds in two steps: identity verification, then account review

• Request a copy of data
• You can correct incorrect
• You can limit unnecessary cookies

For more details, our Terms And Help Page There you will find security, session, and account rules together

Contact Support

If you have questions about privacy, data protection, or cookies, write to support; responses are quick during Dhaka office hours, and explanations are provided in the Bangladeshi users' language

If there are separate issues with 766ok Login or 766ok Register, also check the relevant page; reading the 766ok App Privacy Policy is the easiest safe start