| Stage | What happens | Your control |
|---|---|---|
| Collection | A contact message or a technical request reaches the site | You decide what to send; you can adjust browser settings |
| Use | The information helps us reply, keep the site running or check reported errors | Ask how a specific piece of information is used |
| Sharing | Service providers we rely on may handle a limited amount of it | Ask who receives it and why |
| Storage | Records are kept only as long as there’s a real reason to | Ask how long something is kept |
| Deletion | Records are erased or anonymised when they’re no longer needed | Ask for removal, subject to legal exceptions |
Who This Policy Covers
This policy applies to people who read our articles and people who get in touch with our editorial team. It explains what personal data we collect from them, how we store it and what we do with it. If we ever add user accounts to the site, we’ll update this page to spell out what that feature collects and why.
Jaya9 itself, payment companies, and any other sites we link to collect data in their own ways. This policy doesn’t cover them; authorize what they do or control it in any way. If you’re in Bangladesh and plan to share personal information with any of those services, read their current privacy notice first.
Stage One: Collection
Information can reach us in two ways. Some you send on purpose, and some is generated automatically when your browser loads a page. The difference matters, because you can read every article here without ever sending us anything personal.
Information You Provide
If you write to the editorial team, your message may include some of the following:
- a name or nickname so we know how to address you
- an email address we can reply to
- your question, correction or the page you’re referring to
- a screenshot or file you decide to attach
You choose what goes into the message. Anything beyond what’s needed for us to understand and answer it can simply be left out.
Information Received Automatically
Whenever your browser requests a page, it can pass along your IP address, browser and device type, operating system, preferred language, the pages you open, the time of your visit and the page you came from. Some of these details may end up in server logs, which help us fix technical problems and block abusive traffic.
Cookies and Similar Identifiers
Cookies are small files your browser stores. What a cookie does depends on that particular cookie, not on what it’s called. The categories below are listed for clarity. Their presence here doesn’t mean every type is active on this website.
| Category | Typical purpose | Visitor choice |
| Essential | Keep basic site functions and security working | Some may be needed for the site to run |
| Functional | Remember display or language preferences | Clear or block them in your browser settings |
| Analytics | Count page visits and measure technical performance | Use any consent controls the site offers |
Stage Two: Use
We only use information when there’s a clear reason to. For an editorial site, that means answering messages, improving what we publish, keeping the site working properly and meeting any legal obligations. The fact that other websites process data for other purposes doesn’t mean we do.
Here’s what that looks like in practice:
- Replying to enquiries: we read your question and use the address you gave to answer it.
- Correcting articles: we look into a reported mistake without publishing the sender’s details unless there’s a reason to.
- Maintaining operation: we check errors, suspicious requests and outages.
- Understanding readership: we review visit patterns, but only where measurement tools are actually switched on.
- Meeting legal duties: we keep or disclose information when a valid legal requirement applies.
Information collected for one of these reasons isn’t quietly reused for something unrelated.
Legal Grounds for Processing
Whether processing is lawful depends on what’s being done and which law applies to it. Occasionally the basis is consent, which applies to optional things you agree to. Occasionally it’s a legitimate operational interest, such as reasonable security or site maintenance. And sometimes it’s a legal obligation that requires records to be kept or handed over. These bases are distinct, and one shouldn’t be passed off as another.
In Bangladesh, the Personal Data Protection Act of 2026 sets the framework for working out which requirements apply to each kind of processing. Exactly what applies depends on the Act’s provisions and on when they take effect. This policy is meant to tell visitors how we handle their data. It isn’t a professional audit of our systems.
Stage Three: Sharing
Like most websites, this one may rely on outside companies for hosting, sending emails, protecting against attacks and measuring traffic. Any provider should receive only the data it needs to do its job. A hosting company, for example, may see technical request logs, while an email service may handle the details from a contact message.
We won’t name a company as a recipient unless we’ve confirmed it actually provides a service to this site. Agreements with providers must include proper safeguards and limits on how they can use the information.
Disclosure Required by Law
If an authorised body makes a lawful request for information, we may have to comply. We may also need to keep records connected to a genuine security incident or legal matter. Before disclosing anything, we check that the request meets the relevant legal requirements and share no more than it actually calls for.
Some providers may store data on servers outside Bangladesh or have support teams abroad. Cross-border processing raises fair questions about who can access the data, what contractual safeguards are in place and how well the data is protected in the other country. Each transfer should therefore be assessed under the relevant Bangladeshi law. It shouldn’t be assumed to be always safe or always forbidden.
Stage Four: Storage and Protection
Different records stay useful for different lengths of time. A message might be needed while we look into a correction, and a technical log might only help with an error for a short while. Neither should be kept forever without a reason. Legal requirements, security investigations or genuine disputes can sometimes justify keeping something longer.
Security Measures
Real protection takes more than a privacy statement. It can include encrypted connections, limited staff access, regular software updates, access reviews and watching for unusual traffic. The exact setup depends on the site’s hosting and tools, so we don’t claim any particular encryption standard or monitoring product here.
You can help protect your data too:
- send only what’s needed for an editorial question
- blur or crop out personal details before attaching a screenshot
- never send login details or financial records
- use a device you trust when sharing contact information
These small precautions mean that even if something did go wrong, very little sensitive information would be at risk.
What Happens in Case of a Breach
If we suspect a data incident, the first step is to assess it: what information was involved, whether anyone got unauthorized access, and what can be done right away to contain it. That might mean restricting access, fixing the weakness, and keeping evidence for an investigation.
Where the law requires it, we notify the people affected and the relevant authorities. The timing and method of notification depend on the specific incident and the applicable rules, so we cannot promise a fixed deadline here.
Stage Five: Deletion
Once information is no longer needed, it should be deleted or anonymized where that makes sense. A request from you can also prompt us to check whether there’s still a good reason to keep something. The answer may be different for everyday emails than for records we’re legally required to keep or need for security reasons.
Your Rights at Every Stage
Depending on the law that applies to a particular record, you may be able to ask for access, correction, deletion, or restricted processing, withdraw your consent; or object to certain uses. These rights have limits, though. Identity checks, legal obligations, and other people’s rights can all affect how a request is handled.
How to Submit a Request
Send your question through the site’s contact form and explain clearly what it’s about. If it concerns an earlier message, mention the email address or message involved. Please don’t send identity documents straight away unless we ask for them.
We usually handle a request in three steps:
- We work out which data or activity the request relates to.
- We check whether we have enough information to verify safely that the request comes from you.
- We review which rights apply and then reply or take the appropriate action.
If we need anything more from you along the way, we’ll ask. We won’t hold your request back without telling you why.
Children and Age Restrictions
This site covers gambling-related topics and is meant for adults, not children. We will never ask for personal information about your children. If we receive information we believe belongs to a minor, we review it as soon as possible and delete it unless the law requires us to keep it. If you have concerns, contact us through the Contact Us page.
Policy Updates
How a site handles privacy can change when the site itself changes or when the companies supporting it do. When we make a significant change to this policy, we’ll explain clearly what’s different and show the date of the latest revision at the top. That way you can check the current terms before sending us anything else. Depending on the type of processing and the law that applies, a major change may also require extra notice or fresh consent.