App / Casino
f999one handles your information with care — from the details you enter at registration to the payment records tied to your Nagad or Rocket wallet. This policy explains what we collect, how we use it, and what choices you have, with access subject to your local law and eligible regions.
When you open an account with us, we collect the details you provide directly — your name, contact information, and the payment identifiers linked to your chosen method, such as your Nagad or Rocket mobile number. We also collect data generated by your activity: session records, device type, and browser signals that help us keep your account secure and functioning properly. We do not sell your personal data to third parties. Information is shared only where it is required to operate the service — for example, passing a transaction reference to Nagad or Rocket so a transfer can be completed — or where we are required to do so by a competent authority under applicable law. Data we hold is kept only as long as your account is active or as long as legal retention obligations require. When retention is no longer necessary, records are removed from our systems following our standard deletion schedule. If you use bKash as a payment method, the same principles apply: only the reference data needed to process your transaction is passed to the payment provider, and we do not store your full wallet credentials on our servers. All processing is subject to your local law and the eligible regions in which this service operates.
This policy covers information we collect and process directly through f999one. It does not extend to services or websites operated by third parties, even where a link from our site leads there. Understanding the boundary helps you know exactly who is responsible for each piece of your data.
Data entered during registration, login and account verification falls inside this policy. We control how that information is stored, used and eventually removed when your account closes or retention periods expire.
Payment references passed to Nagad, Rocket or bKash to complete a transfer are covered here up to the point of handoff. Once your transaction is in the payment provider's system, their own privacy terms govern that record.
Browsing signals, session duration and device type collected while you navigate our lobby are within scope. We use these to maintain session integrity and improve how the site loads on mobile — no behavioural profiles are sold.
Game content delivered by studios in our lobby, external links and any service not operated by f999one falls outside the scope of this policy. Check each provider's own terms for how they handle data on their side.
You have practical choices over the information we hold. The account settings area shows the profile details you submitted at registration — you can review them there and submit a correction request if anything is inaccurate. For transaction records tied to Nagad or Rocket, the history visible in your wallet section reflects what we have logged on our side. If you believe a record is wrong, raise it through the support route and we will check it against the relevant payment reference. You can ask us what data we hold about you. Submit your query via the contact route listed in the support section of this policy and we will respond with a summary of the categories of data we have on file. Where applicable law gives you the right to request deletion, you can make that request the same way. We will assess it against any retention obligation that applies and confirm the outcome. Availability of these rights depends on your local law and eligible regions.
Open the account settings page to see the profile and contact details we hold. Check that the information matches what you intended to submit at registration.
If a name, contact number or linked payment identifier is wrong, raise a correction request through support. We will verify against your original submission and update accordingly.
You can request a summary of the data categories we have stored for your account. Send the request through our published contact route and we will respond within the timeframe required by applicable law.
Where your local law permits a deletion request, submit it to our support team. We will confirm whether a legal retention obligation prevents immediate removal and advise on the expected timeline.
If you have a question about how your data is handled, need to correct a record or want to understand what we hold, use one of the routes below. We only list channels that are published and active on the site — no invented contact details or response windows.
Open the chat widget from any page while you are signed in. Describe your privacy question and the agent will log it or escalate to the right team. Availability depends on current site status.
Send your data or policy query to the email address published in the site footer. Include your registered contact number and a short description of the record or request involved.
The Help section inside your signed-in account lists common policy questions and the step to start a formal data request. Start there before contacting support to check if your query is already answered.
Our data handling covers four areas: what we store, how long we keep it, who can see it, and how you can request a change. Each area has a defined process rather than an open-ended commitment, so you can verify the practice through your account rather than relying on a general claim.
We use session cookies to keep you signed in and to track which pages load correctly on your device. Persistent tracking cookies are limited to what is necessary for the site to function. You can manage cookie preferences through your browser settings at any time.
Access to your account data on our side is restricted to authorised team members working on account support or compliance. We do not give game studios or payment providers access to your full profile — only the reference data needed to complete your specific transaction.
Account records are held while your account remains open and for any additional period required by applicable law. Once both conditions are met, records are removed from active systems. Payment references linked to Nagad or Rocket follow the same schedule.
To update contact details, correct a linked Rocket or bKash number, or close your account and request data removal, sign in and use the account settings page first. If the change you need is not available there, submit it via the support email published in the footer.
These are the questions we hear most from account holders about how their data is managed. Each answer reflects the actual practice described in this policy rather than a general statement.
No. We pass only the transaction reference to Nagad or Rocket to complete a transfer. Your full wallet credentials stay within the payment provider's system. We store only the reference identifier needed to match the transaction to your account record.
Send a data inquiry to the support email address in the site footer. Include your registered contact number. We will confirm the categories of data on file for your account and respond within the period required by applicable law in your region.
Yes, where permitted by your local law. Submit a deletion request through live chat or the support email. We will check whether any retention obligation prevents immediate removal — such as a legal or compliance requirement — and confirm the outcome and timeline.
Only authorised support and compliance staff can access your profile data. We share payment references with Nagad, Rocket or bKash only to process your specific transaction. Game studios in the lobby do not receive your personal account details.
We use session cookies to keep you signed in and to verify that pages load correctly on your device. We do not use open-ended behavioural tracking cookies. You can review and adjust cookie settings through your browser at any time without affecting your account access.
The policy governs how we handle data for all accounts we operate. Access to our service depends on your local law and eligible regions. Where local law grants you specific data rights beyond what is described here, those rights are not diminished by this policy.