These guidelines describe how user information may be handled when people interact with this website and the functions connected to it. They cover what may be processed, why, how long it may be held and what control users retain. This is an independent editorial project, so nothing here should be read as the official privacy policy of the Jaya9 operator, which publishes its own separately.
Our Approach to Personal Data
The approach rests on three commitments. Information serves defined purposes rather than general ones, security is treated as a practical requirement instead of a slogan, and the reasons behind processing are stated openly.
| Commitment | What it looks like |
| Defined purposes | Data used for stated reasons, not repurposed |
| Minimal collection | What is unnecessary is not gathered |
| Security attention | Reasonable protection for what is held |
| Transparency | Reasons described rather than implied |
| No onward sale | Personal information is not sold |
Users Covered by This Policy
The document may apply to three groups.
- Visitors who read pages and do nothing further
- Users of account-related functions, where such functions exist
- People who send messages through a contact form
The amount of information generated differs enormously between them. A reader opening two pages produces technical data alone. Someone writing in supplies what they chose to include. Where a platform account is involved, that platform’s own policy governs it, and this document does not stand in its place.
Personal Information Categories
Several categories may arise depending on what a person does.
Information Submitted by Users
Where registration or a contact form exists, a person may supply a name or username, an email address, a phone number, a date of birth, a country of residence or the text of a message. The form shown at the time determines what is asked for, and anything not present on it is not required.
Confirming identity, age or ownership of a payment method may involve documents or supporting data. Material of that kind belongs exclusively inside a secure interface built for it. It should never be attached to an ordinary message, and any request for it through chat, email or a form is a sign of fraud rather than of process.
Payment and Transaction Details
Where payment functions apply, records may include an amount, a currency, a date, a status, a method and a transaction reference. Full card numbers and the secret credentials of a payment account are not held as ordinary data, since those remain with the payment provider handling the operation.
Technical Data From Browsing Activity
Loading a website transmits technical information automatically:
- An IP address, in general form rather than as an identifier of a person
- Device type and basic characteristics
- Browser and operating system
- Language settings
- Pages visited and the time of activity
- The referring source
Location inferred from an IP address describes a broad area. That a visit came from Bangladesh is a different fact from where a reader physically is, and this kind of data does not establish the second.
Purposes of Using Personal Information
| Purpose | What it covers |
| Account support | Where account functions apply |
| Security | Detecting misuse, fraud and abuse |
| Handling requests | Considering and answering messages |
| Preventing violations | Identifying activity that breaks the rules |
| Site improvement | Fixing faults and refining how pages work |
Each purpose reflects an operational need. None involves advertising profiles or passing personal information to anyone for their own marketing.
A cookie is a small file your browser keeps so a site can carry information across pages. Session cookies keep a visit coherent and support any sign-in function, preference cookies retain settings such as language, and analytics cookies measure how pages perform and where faults appear.
Analytics measurement, where it happens, is carried out by an external provider under that provider’s own policy. No particular provider is named here, since such arrangements change and naming one that has been replaced would mislead readers rather than inform them.
Your browser controls all of it, allowing stored cookies to be viewed, deleted and restricted by site. Private browsing usually discards them when the window closes, and settings apply per browser and per device rather than universally.
What changes when they are blocked:
- Sign-in and session behaviour becomes inconsistent
- Saved preferences reset at every visit
- Analytics stops, with no effect on what you can read
Refusing analytics costs a reader nothing at all. Refusing session cookies costs functionality, which is worth understanding before switching everything off at once.
Operating a website involves outside companies for hosting, technical support, payment infrastructure where relevant, security and maintenance. Where information reaches such a provider, it should be limited to what that provider’s task requires.
No unconfirmed company is named here. Any provider involved processes what it receives under its own terms, outside this site’s control, and rights you hold over that information operate against them alongside us.
Situations Where Data May Be Disclosed
Information may be disclosed where a lawful request is made by an authorised body, where disclosure protects users, or where fraud is being investigated or prevented.
No unconditional promise is offered that data will never be provided to authorities. Such a promise cannot be honoured by anybody operating a website, and offering it would be a comfortable lie rather than a commitment.
Storage Period and Protection Methods
How long information is kept depends on what it is and why it was collected. Technical and error logs are held for the period needed to investigate faults, then cycle out. Correspondence is retained while a matter is open and afterwards only where a reason exists.
No month count appears here, because the honest answer depends on the systems in use.
Protection uses standard measures. Encrypted connections for traffic, access limited to those who need it, software kept current so known weaknesses close, and monitoring for unusual activity. Offering a guarantee of absolute security would be dishonest, so none is offered.
User Control Over Personal Data
Depending on circumstances and the requirements that apply, several rights may be available, including access, correction, deletion, restriction of processing and withdrawal of consent.
These are not uniform in every case, so requests are assessed against the situation rather than approved automatically.
Updating Personal Information
Where a detail can be changed through available settings, that route is fastest. Where it cannot, a request through the contact channel is the alternative, and confirming that the request comes from the right person is part of handling it.
Removing Stored Information
Deletion can be requested. Certain records may still be retained where security, fraud prevention, an unresolved matter or a continuing obligation requires it, which is why complete immediate erasure is not something any site can honestly undertake.
Managing Consent Decisions
Where consent supported a specific use, such as optional messages or non-essential cookies, it can be withdrawn at any point. Withdrawal applies from then onward and does not reverse processing already completed on a lawful basis.
Requests travel through the contact channel. State the subject and what you want done, and leave out passwords, codes, documents and payment details entirely, since none of it is needed and nobody legitimate would ask.

