Scope of This Policy
This policy applies to data that may be processed when you visit this website and when you contact the editorial team.
It covers normal website use, technical operation, security-related processing, and editorial communication.
If you follow a link to a third-party site, that external resource operates under its own privacy rules, not this editorial policy.
Technical and Usage Data We May Receive
Depending on how the site is used, collected information may include:
- device type;
- browser type;
- operating system version;
- interface language;
- referrer information;
- aggregated page views;
- technical error events;
- IP address and log data, where needed to protect the site.
This information is used in a limited and practical way. In many cases, it is processed as technical or aggregated data rather than as direct personal profile data.
Data We Do Not Ask You to Send
The editorial team does not need and does not ask you to send:
- passport or other identity documents;
- payment details;
- UPI information;
- passwords;
- confirmation codes;
- seed phrases;
- private keys;
- third-party account credentials;
- your full phone number as a required detail;
- your home address as a required detail.
These details are not needed for an editorial reply. If such information is sent by mistake, the editorial team does not need it and will not ask for it again.
Cookies, Preferences, and Similar Technologies
This site may use cookies and similar technologies for basic functions, interface preferences, and aggregated analytics.
For example, these tools may help remember language settings, support normal site behavior, or provide general usage patterns in summary form.
Users can manage these settings in their browser. If cookies are disabled, some preferences may not be saved and some parts of the site may work differently.
Third-Party Tools for Security and Metrics
The site may use external tools for spam prevention, basic analytics, abuse protection, and technical stability.
Those tools operate under the rules of their respective providers. The editorial team tries to use only integrations that are necessary for site security, performance, and limited measurement of usefulness.
This notice does not list provider names unless their use is formally fixed and stable.
Why We Process Limited Data
Limited data may be processed for the following purposes:
- keeping the site operational;
- maintaining security;
- protecting the site from automated abuse;
- diagnosing technical errors;
- understanding which materials are useful to readers;
- replying to messages sent to the editorial team.
The site does not sell data. It does not use data to push betting or financial services. It is not connected to payments, because the site does not handle them.
Retention and Minimization
Technical logs are kept only for a limited period that is reasonably necessary for security, abuse review, and investigation of suspicious activity.
Editorial correspondence may be kept for as long as needed to respond, maintain correction history, and improve the materials.
Aggregated data may be stored longer in a de-identified form where that helps with site stability, editorial review, or long-term understanding of content usefulness.
These are guiding principles rather than fixed deadlines. Exact retention periods may vary depending on technical, security, and legal needs.
Security Practices
The site uses basic security measures intended to reduce risk and protect normal operation.
These measures may include:
- HTTPS / SSL;
- restricted access to administrative areas;
- minimized access rights;
- regular updates;
- reasonable protection of editorial email and infrastructure.
At the same time, no website can guarantee absolute security. This site aims to reduce risk, not to promise zero risk.
Your Privacy Requests
You may use the contact page to send a relevant privacy request. This may include a request to delete correspondence, clarify what data relates to your message, or ask another reasonable question about privacy and editorial communication.
To protect against misuse, the editorial team may ask for the minimum information needed to confirm the request. It will not ask for your password, OTP code, banking information, or third-party account credentials.