Slots / Mobile
Your account data on yv77 stays within defined collection boundaries — what we collect, why we collect it, and how you can review or remove it are all laid out here. Access to these controls depends on your local law and eligible region.
This page sets out the categories of information yv77 collects when you open and use an account: registration details, device identifiers, wallet transaction references from Nagad and Upay, and session activity logs. We do not sell your data to third parties.
yv77 collects only what is needed to run your account and process wallet activity. Below are the four main categories, what each one contains, and why it is held.
When you open an account, we record the name, contact details and verification credentials you supply. This is the foundation for account recovery, support identity checks and wallet ownership confirmation. Nothing beyond what you enter is added to this record without your action.
Every deposit and withdrawal processed through Nagad, Upay, bKash or Rocket generates a transaction reference. We store that reference number alongside the date, amount and channel so you can reconcile your account wallet history at any time from the transaction log.
We log the device type, browser version and session timestamps when you access the platform. This data is used to detect unusual login patterns and to ensure mobile access from your registered device matches the account record. No personal browsing history outside yv77 is collected.
When you contact support, the conversation thread and the issue category are retained. This lets follow-up agents see the full context without asking you to repeat yourself. You can request deletion of resolved support logs through the same contact route you used to raise the issue.
yv77 gives you practical routes to inspect, correct or request deletion of the data we hold. Each path is accessible from within your signed-in account area or via the published support contact. The steps below describe where each control sits and what it covers.
Your wallet page inside the signed-in account area shows a timestamped log of every Nagad, Upay, bKash and Rocket transaction reference we hold. You can filter by date range and export the visible rows for your own records.
To receive a full export of the personal data tied to your account, submit a request through the support contact route published on the contact page. We will process the request and respond within the timeframe stated in the published policy document.
If your registered contact details or verification credentials have changed, update them from the account settings section. For fields that are locked after verification, raise a correction request via support with the relevant document so the team can action it properly.
Cookie preferences are managed through the consent panel that appears on first visit or through the privacy settings link in the site footer. Functional cookies required for login session stability cannot be disabled, but analytics and preference cookies can be turned off at any point.
If something in this Privacy Guide is unclear, or if you want to action a data request, the routes below are the ones published on the yv77 contact page. Use the channel that matches your query type.
The live chat widget visible in the signed-in account area connects you to the support team directly. For privacy queries, open the chat and select the account or data category so the agent has the right context from the start.
Send detailed data access or deletion requests to the support email address listed on the published contact page. Include your registered account identifier and the specific data category you are enquiring about so the team can locate your records without delay.
Several privacy actions — updating contact details, adjusting cookie preferences, downloading your transaction log — are available directly inside your account settings without needing to contact the team. Check this path first for routine data review tasks.
The commitments in this Privacy Guide are not abstract statements. Each one maps to a specific account behaviour, a support route, or a published document you can verify from within your signed-in session.
The full privacy policy is accessible from the site footer without logging in. It is dated and versioned so you can see when it was last updated. Any material change to data handling practice is reflected in a new version before that change takes effect.
Transaction references from Nagad, Upay, bKash and Rocket are stored exactly as issued by those providers. We do not modify reference numbers. If a transaction reference in your account log does not match your mobile wallet history, support can investigate using both records side by side.
Your account data and transaction history are not sold or rented to third parties. Where a technical service provider processes data on our behalf, that relationship is documented in the privacy policy under the relevant section on data processors.
Data rights available to you — including access, correction and deletion — depend on your local law and the eligible regions where yv77 operates. The published policy states which rights apply in which contexts. Where a right is not available in your region, the policy explains why.
These definitions cover the core vocabulary used in the yv77 Privacy Guide. Understanding these terms helps you read the published policy accurately and know exactly what each data right or category refers to before you raise a support request.
The data controller is the entity that decides why and how personal data is collected and used. In this context, yv77 is the data controller for information you supply when opening and using your account.
Data processing covers any operation performed on personal information — collecting it, storing it, retrieving it, sharing it with a processor, or deleting it. Every interaction with your account involves some form of data processing as defined here.
A transaction reference is the unique identifier issued by Nagad, Upay, bKash or Rocket when a payment completes. Storing it links your wallet activity to your account record and supports reconciliation or dispute resolution.
Cookies are small data files placed on your device by the site. This guide covers which cookies yv77 uses, their purpose, and how to adjust cookie preferences through the consent panel in the site footer.
A data subject access request — often called a DSAR — is a formal request for a copy of the personal data an organisation holds about you. Submit one through the support email route published on the contact page.
Data retention describes how long we keep your information after your account becomes inactive or is closed. The privacy policy states specific retention periods for account records, transaction logs and support interaction history.
These are the questions we hear most often from members reviewing the Privacy Guide. Each answer points to the specific account route or published document where you can verify the information or take action. Availability of certain rights depends on your local law and eligible region.
Send a data access request to the support email listed on the contact page. Include your registered account identifier and specify that you want a full data export.
Yes, subject to your local law and eligible region. Submit a deletion request through the support email or live chat and specify which data categories you want removed.
Transaction references from Nagad, Upay, bKash and Rocket are stored in your account wallet log and are not sold or shared with third parties for marketing.
Open the cookie consent panel from the privacy settings link in the site footer. Analytics and preference cookies can be switched off there at any point. Functional cookies that maintain your login session are required and cannot be disabled without affecting your ability to stay signed in.
On account closure, yv77 stops active data collection tied to your session. Existing records — including transaction references and support logs — are retained for the period stated in the published privacy policy before scheduled deletion. You can request the exact retention timeline through the support contact route.
The privacy policy document in the site footer is dated and versioned. Any material change is reflected in a new version published before the change takes effect.