Visitor Data and Safety
Data We Collect
Two types. Automatic technical data from page loads. Voluntary data from the contact form.
Technical data arrives whenever a page opens. IP address. Browser type and version. Operating system. Device type. Screen size. Which page was loaded. How long the visit lasted. Where the visitor came from — search engine, link from another site, or direct URL entry. This is standard server-level logging. Every website with analytics collects the same kind of data.
Contact form data includes whatever the visitor types in. Usually a name, an email address, and a message. The email is there so a reply can be sent. The name helps address the response. The message contains the actual question or correction.
Cookies sit in a third category. Small text files placed by the browser. The site uses functional cookies for basic operations and analytics cookies for counting visitors. No advertising cookies. No retargeting. No cross-site tracking.
Data We Do Not Collect
The site does not ask for and does not store:
- Passwords to any platform or service. One-time passwords, verification codes, or OTPs. UPI PINs. Bank account numbers. Credit or debit card details. Aadhaar numbers. PAN numbers. Identity documents or scans. Cryptocurrency wallet seed phrases or private keys. Screenshots of wallets, transactions, or account dashboards. KYC materials of any kind.
- If any of this shows up in a contact form message, the team deletes the message without acting on the request and tells the sender to use a secure channel instead. No member of the editorial team will ever ask for credentials, payment data, or identity documents. Any communication claiming to be from this site and requesting such information is fraudulent.
How We Use Data
Contact form data goes toward answering the message. A visitor reports an article error. The team reads it, checks the claim, fixes the article if needed, and replies to the email provided. That’s the entire use case. No mailing lists. No promotional emails. No sharing with marketing partners.
Technical data gets looked at in aggregate. Which articles draw the most readers. Which pages have high bounce rates. Which devices most visitors use. These numbers shape editorial decisions. The analysis looks at patterns across thousands of visits, not at individual sessions.
Security and spam filtering. Technical data helps spot automated abuse — spam bots hitting the contact form, scrapers pulling content at scale, traffic patterns that look like attacks. These protections run in the background and don’t affect normal visitors.
Error correction. When a visitor reports a problem with a specific page, the technical data for that page can help the team reproduce and diagnose the issue. Browser type, device, screen size — all useful for troubleshooting display problems.
Cookies and Tracking Preferences
Two types of cookies on this site. Functional ones that keep things working — language preferences, session state. Analytics ones that count visitors without identifying anyone by name.
No ad cookies. No retargeting pixels. No data sold to ad networks. No behavioural profiling across sites.
Browser settings control cookies. Most browsers allow blocking all cookies, blocking only third-party cookies, or wiping cookies when the browser closes. Blocking everything won’t break the site, though some preferences may not stick between visits.
Incognito or private browsing mode clears cookies automatically when the window closes. Works across all major browsers. For visitors who want zero cookie persistence, that’s the simplest path.
Third-Party Services
A small number of external services keep the site running.
Analytics. A standard analytics tool processes traffic data in aggregate. IP, browser, pages visited — turned into statistical summaries. No individual profiles.
Hosting and CDN. The site runs on infrastructure managed by a hosting provider. Server logs are processed as part of normal operations. The provider’s privacy policy covers their side.
Anti-spam. The contact form runs spam filtering to separate real messages from automated junk. The service may look at IP addresses and interaction patterns to tell humans from bots.
CMS and security plugins. The content management system and its security components operate under their own developers’ policies. Updates get applied regularly.
Each service has its own data practices. The site picks services that align with minimal collection principles. But this site cannot guarantee what a third-party provider does internally. Visitors who want specifics on which tools are in use can ask through the contact form.
Data Retention and Deletion
Contact form messages stay in the editorial inbox during the conversation and for a reasonable period after for reference. Messages don’t sit in an archive forever. They’re not mined for patterns or repurposed for anything beyond the original exchange.
A visitor who wants their previously submitted data deleted can request it through the contact form. The team verifies the request comes from the right person, then removes the data.
Technical data from server logs follows the hosting provider’s retention schedule. Analytics data lives in aggregate form without individual identifiers.
Security Measures
The site runs over HTTPS. Data moving between the visitor’s browser and the server is encrypted. Page loads, form submissions, everything in transit gets the same protection.
Admin access is restricted to editorial team members. Individual credentials for each person. Login activity gets logged.
The CMS, plugins, and server software get regular updates. When a vulnerability shows up in any component, the patch goes in as soon as the update is available.
Anti-spam tools filter automated submissions on the contact form. Rate limiting prevents abuse.
Periodic security checks look for misconfigurations, outdated components, and signs that something got in that shouldn’t have. External scanning tools add a second layer on top of internal checks.
All of that said — no system online is completely immune to every threat. Software vulnerabilities, infrastructure attacks, and social engineering are possibilities that no site can fully eliminate. The site maintains current practices and responds to new threats as they come up. But claiming total immunity would be dishonest, so it isn’t claimed.
Changes to This Policy
The privacy policy may be revised. The current version lives on this page with the last-updated date at the top. Using the site after an update means accepting the revised version.
Questions
Data handling questions, access requests, and deletion requests go through the contact form. Adding “privacy” to the message text helps with routing.