Data We Collect
Two categories. Data that arrives automatically when a page loads. Data that visitors send voluntarily through the contact form.
Automatic technical data includes IP address, browser type and version, operating system, device type, screen resolution, referring URL, pages visited, and time spent on each page. This is standard server-level logging. Every website with analytics receives this type of data. None of it is used to build individual profiles or to identify specific visitors by name.
Contact form data includes whatever the visitor types into the form. Typically a name, an email address, and a message. The email is needed to send a reply. The name is used for addressing the response. The message contains whatever the visitor chose to write.
Cookies are small text files placed by the browser. The site uses functional cookies that help the site operate correctly and analytics cookies that help count visitors without identifying them individually. No advertising cookies. No tracking pixels from ad networks. No cross-site behavioural profiling.
Data We Do Not Collect
The site does not ask for and does not store:
- Passwords to any platform. One-time passwords or verification codes. UPI PINs or bank account numbers. Credit or debit card details. Aadhaar numbers. PAN numbers. Identity documents of any kind. Cryptocurrency wallet seed phrases or private keys. Screenshots of wallets, transactions, or account dashboards.
- If any of this information is included in a contact form submission, the team deletes the message without processing the request and notifies the sender. No editorial team member will ever ask for login credentials, payment details, or identity documents. Any communication claiming to be from this site and requesting such information should be treated as fraudulent.
How We Use Data
The uses are narrow and specific.
- Contact form data is used to reply to the message. If a visitor reports an error in an article, the team reads the message, checks the claim, fixes the article if needed, and sends a reply to the provided email. The data is not added to a mailing list. Not shared with marketing partners. Not used for any purpose beyond handling the specific communication.
- Technical data is used in aggregate. Which pages get the most traffic. Which devices visitors use most often. Which articles have high bounce rates, suggesting the content isn’t meeting expectations. These numbers inform editorial decisions about what to write next and what to improve. Individual records are not examined one by one. The analysis looks at patterns across thousands of visits, not at single sessions.
- Security and spam prevention. Technical data helps identify and block automated abuse — bots submitting spam through the contact form, scraping tools extracting content at scale, or traffic patterns consistent with denial-of-service activity. These protective measures run in the background and do not affect normal visitor experience.
Cookies and Tracking Preferences
The site uses two types of cookies. Functional cookies keep the site working correctly — remembering language preferences, maintaining session state. Analytics cookies help count unique visitors and page views without requiring any identifying information. One anonymous browser is distinguished from another anonymous browser. That’s the extent of it.
No advertising cookies run on this site. No retargeting. No cross-site tracking. No data sold to ad networks.
Visitors can manage cookies through their browser settings. Most browsers allow blocking all cookies, blocking third-party cookies only, or clearing cookies on exit. Disabling cookies entirely will not prevent the site from loading, though certain preferences may not persist between visits.
For visitors who prefer maximum privacy, incognito or private browsing mode prevents cookies from persisting after the browser window closes. This works on all major browsers across mobile and desktop.
Third-Party Services
The site uses a small number of external services to function.
Analytics. A standard analytics tool processes aggregated traffic data. The tool receives technical data (IP, browser, pages visited) and returns statistical summaries. No individual-level profiles are built.
Hosting and content delivery. The site runs on hosting infrastructure operated by a third party. That provider processes server logs as part of normal operations. The provider’s own privacy policy governs their handling of that data.
Anti-spam. The contact form uses spam protection to filter automated submissions. This service may process IP addresses and form interaction patterns to distinguish human submissions from bots.
CMS and security plugins. The content management system and any security plugins used on the site operate under their respective developers’ privacy policies. Updates are applied regularly to maintain security.
Each of these services has its own data handling practices. The site selects services that align with minimal data collection principles, but cannot control or guarantee the internal practices of third-party providers. Visitors concerned about specific services can contact the editorial team through the form for clarification on which tools are currently in use.
Security Measures
The site operates over HTTPS. Data transmitted between the visitor’s browser and the server is encrypted in transit. This covers page loads, form submissions, and any other interaction.
Access to the site’s administrative systems is restricted to editorial team members. Each has individual credentials. Login activity is logged. The content management system, plugins, and server software receive regular updates. Known vulnerabilities in any component are patched as updates become available.
Anti-spam protection filters automated contact form submissions. Rate limiting prevents abuse of the form and other interactive elements. Regular security reviews check for configuration issues, outdated dependencies, and signs of unauthorized access. External scanning tools supplement internal checks.
Despite these measures, no online system is fully immune to all threats. Vulnerabilities in third-party software, infrastructure-level attacks, and sophisticated social engineering remain possibilities that no site can eliminate entirely. The site maintains current best practices and responds to emerging threats as they are identified. But promising absolute security would be inaccurate, so it is not promised.
Data Retention
Contact form messages are retained in the editorial inbox for the duration of the communication and a reasonable period afterward for reference. Messages are not archived indefinitely. Requests for deletion of previously submitted messages are handled through the contact form.
Technical data from server logs is retained according to the hosting provider’s standard policy. Analytics data is stored in aggregate form and does not contain individual-level identifiers.
Visitor Rights
Visitors who have submitted data through the contact form can request a copy of what is stored. They can request deletion. Both requests are handled through the same contact form. The team verifies that the request comes from the person whose data is in question before acting.
Visitors who have not submitted any data through the contact form have no individual-level data stored by the site. Their visits are reflected only in aggregate analytics, which cannot be traced back to a specific person.
Changes to This Policy
The privacy policy may be updated. The current version is always available on this page with the date of last revision noted at the top. Continuing to use the site after an update constitutes acceptance of the revised policy.
Contact
Questions about data handling, requests for data access or deletion, and concerns about privacy practices are accepted through the contact form. Including the word “privacy” in the message helps with routing.