Jaya9 Privacy Practices & User Information

Privacy Practices and User Information
The following is a description of how user information may be processed as part of using this website and any other activities associated with it. It identifies the types of data that may be gathered, the reasons why, how long they will remain available for use, and how users can manage the processing of their data. This is an independent editorial endeavour and does not represent the official privacy statement of the publisher of Jaya9, who produces their own.
Understanding How Information Is Used
The guiding premise is limited purpose. The information is used for certain objectives relating to the operation of the site, its security and its improvement and not for purposes unrelated to these.
| Principle | What it means |
| Limited purpose | Data serves a stated function, not a general one |
| Minimal collection | What is not needed is not gathered |
| Security | Reasonable protection for what is held |
| Transparency | The reasons are described rather than implied |
| No sale of data | Personal information is not sold to anybody |
Scope of Personal Data Protection
The three types of visitors covered by this policy are those who view pages without interacting, those who use account features if available, and those who submit messages via the contact form.
The results of each group vary significantly. When someone opens up two different pages on a computer screen, he/she only generates technical data. However, when someone sends a message through the system, he/she can send as much or little information as they wish. Finally, if the system is used for accounts (such as bank accounts), the company or organization providing access will have its own policies for managing those accounts. These policies are not part of this document.
Information Categories We May Collect
We may include other categories based on what you really do. There is no profile kept about a reader, and so this is not a profile established about a reader.
Data From Account Creation
When you provide your details during a registration or profile creation process, you will typically be asked to provide your name/username, email address, phone number, date of birth, and country of residence. The specific information requested is determined by the form used to collect it; therefore, you only need to provide what the form asks for.
Data Used for Verification Purposes
When confirming your identity, your age, or if you own the payment method used; you may need to provide supporting documentation or validation information. This type of documentation is only to be uploaded into a secure system designed for this purpose. Do not attach this documentation to standard messages. If you are asked to upload it via chat, email, or a contact form, consider the request to be fraudulent.
Financial and Activity Information
Where payment functions are used, records may cover the amount, the currency, the date, the status of an operation, the method chosen and a transaction reference. That differs from storing a full card number or the credentials of a payment account, which stay with the payment provider rather than being held as ordinary data.
Activity records, where they exist, may cover interactions with functions and the queries raised about them.
Automatically Generated Technical Information
Any page you load will send technical facts without anybody typing:
- An IP address used in the generic form and not to identify a person
- Basic display characteristics and device type
- Browser & Operating System
- Language preferences
- Pages opened and time of visit
- The source that directed you
An IP address gives a rough idea of location, showing a large area. Knowing a visitor is from Bangladesh does not tell us where a reader is physically located, and such data does not establish the latter.
Reasons Behind Data Processing
| Purpose | What it covers |
| Delivering functions | Making pages and features work |
| Account support | Where account functionality applies |
| Security | Detecting abuse, fraud and misuse |
| Handling messages | Considering and answering what you send |
| Improvement | Fixing faults and refining how the site behaves |
Each of them has a legitimate purpose behind it. None of them can use it for profile promotion or selling information.
Cookies are small files kept by your browser, letting a page recall something from the page before it. Three purposes apply.
Session cookies hold a visit together across pages and support any sign-in function. Preference cookies remember settings such as a language choice. Analytics cookies measure how pages are used and where technical problems occur.
Analytics measurement, where used, is handled by an external provider under that provider’s own policy and terms. No specific provider is named here, since such arrangements change and naming one that has been replaced would mislead.
Control sits in your browser, which lets you inspect stored cookies, delete them and restrict which sites may set them. Private browsing usually discards them when the window closes, and settings apply per browser and per device.
What changes if you block them:
- Session functions, including any sign-in, may stop working consistently
- Saved preferences such as language reset on each visit
- Analytics collection stops, with no effect on your reading
Blocking analytics costs a reader nothing. Blocking session cookies affects functionality, which is the trade-off worth knowing before changing everything at once.
Operating a website involves external companies for hosting, technical support, analytics and security. Where information reaches them, it should be limited to what their specific task requires.
No unconfirmed organisation is named here. What can be said is that such providers process what they receive under their own terms and policies, which sit outside this site’s control, and that any rights you hold in relation to that data operate against them alongside us.
Disclosure for Safety and Legal Reasons
Information may be disclosed where a lawful request comes from an authorised body, where disclosure is needed to protect users, where fraud is being investigated, or where the rights and security of the site are at stake.
No blanket promise is offered that data will never reach authorities, because such a promise could not be honoured by anybody operating a website.
Keeping and Protecting Personal Data
Retention depends on the type of information and the purpose it serves. Technical and error logs are held for the period needed to investigate problems and then cycle out. Correspondence is kept while a query is being handled and afterwards only where a reason exists.
Putting a specific number of months on it would be invention, because the answer depends on the systems doing the storing.
Protection combines ordinary measures. Traffic is served over an encrypted connection, access is restricted to those who need it, and software is kept updated so known weaknesses are closed. Nobody running a website can truthfully promise total security, so no such promise appears here.
Privacy Rights Available to Users
Depending on circumstances and applicable requirements, several rights may be available.
Reviewing Personal Information
You may ask what information relating to you is held and request correction of anything inaccurate. Where a detail can be edited directly through available settings, that route is faster. Where it cannot, a request through the contact channel is the alternative, and confirming that a request comes from the right person forms part of handling it.
Asking for Data Deletion
Deletion of specific information can be requested. Some records may still be retained where security, fraud prevention, unresolved disputes or continuing obligations require it, so immediate erasure of everything is not something any site can honestly promise.
Changing Privacy Preferences
Where consent underpinned a particular use, such as optional messages or non-essential cookies, it can be withdrawn. Withdrawal applies going forward and does not reverse processing already carried out on a lawful basis before the request.
Requests of any kind go through the contact channel. To be handled quickly, a request should include:
- The subject of the request
- The contact you are writing from
- A clear statement of what you want done
Never include passwords, verification codes, identity documents or payment details in the message. None of it is needed, and nobody legitimate will ask for it.