Guru11 India Privacy Policy: data the site collects and does not
This privacy policy is a plain-language inventory of the data the Guru11 India editorial site handles. The inventory is short because the site is a static publication rather than an application. The policy explains what the server logs, what cookies the site sets, what the contact channel records, how long each item is kept, and what happens when a reader writes in with a deletion request.
What this policy covers
This policy applies to the domain guru11india.com and to any subpath under that domain. It does not apply to the Guru11 operator's site, to the operator's mobile app, or to any third-party site the operator links out to. When a reader clicks an outbound link on a Guru11 India page, the operator's own privacy policy takes effect on the destination, and the reader should read that policy before sharing any detail the operator's form asks for.
This policy also does not apply to the editorial team's internal file storage, which holds screenshots of the operator's published pages, draft outlines, and the editorial changelog. Those files are not linked to a reader's identity, are stored on a private volume that is not exposed to the public web, and are deleted on a rolling basis once the related hub page is re-read and confirmed current. A reader who would like more detail on those internal files can write in through the contact channel.
Data the site does not collect
The site does not ask a reader for a name, an email address, a phone number, an Aadhaar number, a PAN, a date of birth, a bank account, a UPI handle, a card number, or any payment credential. The site does not run a login wall, does not require an account to read a hub page, and does not store a profile of returning visitors. There is no comment section, no subscription form, no chat widget, no survey tool, and no account-creation step that records a reader's input.
The site does not place advertising cookies, retargeting pixels, or third-party analytics cookies. There is no Google Analytics tag, no Facebook pixel, no LinkedIn insight tag, no Hotjar recording, and no affiliate redirect that would let another party read a reader's behaviour on this domain. The site does not embed social-share buttons that phone home to a social network, and the site does not load third-party fonts, third-party scripts, or third-party iframes that would let another party observe a reader's visit.
Server logs and basic request data
Like every site served over HTTP, the Guru11 India server keeps a temporary log of each request. The log records the request time, the requested URL, the HTTP response code, the number of bytes sent, the referrer header if one is present, and the IP address that made the request. The log is used to keep the server healthy, to spot abusive traffic, and to debug errors when a hub page returns an unexpected status. The log is not sold, shared, or used to build a profile of any reader.
Server logs are rotated automatically and are not retained for longer than the operational window requires. The exact retention window is set by the hosting provider's default, and the editorial team has not extended it. The site does not run a separate analytics platform that keeps a reader's history across sessions, and the editorial team does not query logs in a way that ties a request back to a real person outside of an active abuse investigation.
Cookies, local storage, and the cache layer
Guru11 India does not set any cookie of its own and does not use localStorage, sessionStorage, IndexedDB, or the Cache API to remember a reader between visits. The site does not need a cookie to work because there is no logged-in state, no comment thread, and no preference to save. If a browser holds a cookie for this domain, it was placed there by the reader's own browser, by a browser security feature, or by an extension the reader has installed, not by the editorial code on this site.
The site does serve static assets such as CSS, JS, and image files, and the browser may cache those assets locally under its normal caching rules. That cache is local to the reader's device, is not transmitted to the editorial team, and is purged by the reader's browser on its own schedule. The site uses a small cache-bust parameter on asset URLs when a CSS or content change needs to ship faster than the default browser cache TTL.
The contact channel and reader messages
Messages sent to the contact channel are stored in the editorial team's shared mailbox until the thread is closed. The mailbox is hosted on a privacy-respecting provider with two-factor authentication, and the editorial team is the only group with access to it. The mailbox is reviewed weekly, closed threads are exported to a private archive, and the export is encrypted at rest with a key the team controls. The export is deleted when the related hub page is re-read and confirmed current, with a typical archive lifetime of ninety days.
The contact channel does not ask a reader for personal data, and the desk prefers a message without personal data because the editorial work does not need it. Where a reader chooses to include personal data in a message anyway, the editorial team redacts the personal data from the archive export at the end of the thread, and the redaction is logged in the editorial changelog so the audit trail is preserved.
Sub-processors and third-party services
The site uses a small number of sub-processors to operate. The hosting provider serves the static files from a single virtual machine, the DNS provider resolves the domain, and the contact channel provider hosts the editorial mailbox. Each sub-processor is chosen for a privacy-respecting default, and the editorial team reviews the sub-processor list whenever a new provider is added or an existing one changes its terms.
The site does not embed any third-party iframe, widget, font, or script on a reader's page. The images are served from the site's own asset folder, the styles and scripts are served from the same origin, and the typography uses the visitor's system font stack so no font request leaves the device. If a future update adds a third-party embed, this policy will be updated to list the new provider and the data the provider may receive before the embed is published.
Children's privacy and the 18+ rule
Guru11 India is written for adult readers of legal age to use real-money gaming or fantasy apps in India. The site does not target minors, does not collect data from anyone known to be under the legal age, and does not host content that is designed to appeal to readers under 18. If a parent or guardian believes a minor has used this site, the contact page explains how to send a note, and the editorial team responds with confirmation that no profile or tracking record exists for the visit in question.
The Guru11 app itself is governed by the operator's own age rules and KYC requirements. This site does not see, store, or copy a reader's KYC documents. The KYC flow described on the app-download and login hubs is described in plain language so a reader knows what to expect from the operator, not so this site can capture the documents. The privacy boundary between this site and the operator is enforced on this side of the relationship by design.
Data sharing, legal requests, and ownership changes
Guru11 India does not sell, rent, or trade reader data because the site does not collect reader data in the first place. If a lawful authority submits a valid legal request, the team responds within the time allowed by Indian law and shares only what is strictly required. The team does not volunteer data, does not act on informal requests, and does not hand over a reader's correction email unless the email is itself the subject of a valid request.
If the ownership of the Guru11 India site changes in the future, the privacy policy will be updated to reflect the new data controller, and a notice will appear on the homepage for at least 30 days before the change takes effect. Readers who want to know the current data controller can email the contact channel for confirmation, and the team replies to that kind of question directly.
Retention schedule in one place
The retention schedule below summarises the items above. Server logs are kept for the hosting provider's default window, which is short. The contact mailbox export is kept for ninety days after the related thread is closed. The screenshots of the operator's published pages are kept until the related hub is re-read and confirmed current. The editorial changelog is kept indefinitely because it is part of the editorial record, not the reader record, and contains no personal data.
A reader who would like any of those items deleted sooner can write in through the contact channel with a short note describing the request. The team responds within a few working days with confirmation that the item has been deleted, and the confirmation is itself logged in the editorial changelog so the audit trail is preserved.
Updates to this privacy policy
This policy is reviewed when the site adds a new feature, a new embed, a new outbound integration, or a new data flow. The "last updated" date at the bottom of the page reflects the most recent review. Material changes are summarised at the top of the policy for at least 30 days after the change is published, so a returning reader can see what changed without re-reading the whole document.
For questions about this policy, send a note through the contact channel. The editorial team replies to privacy questions directly and treats them as a priority over general editorial enquiries. If the policy needs to be updated in response to a question, the update is published before the team closes the thread so the public record stays current.
How this policy fits the editorial mission
The privacy policy is part of the editorial mission because trust is part of the editorial product. A reader who lands on a Guru11 India hub and wonders whether the page itself is harvesting data should be able to read the policy in plain language and walk away with a clear answer. The answer is that the page does not harvest data, the server logs are rotated quickly, and the editorial team does not build a profile of any reader.
The team reviews the policy alongside every new hub and every new blog post. If a new piece of content would change what the site collects, the policy is updated before the content is published, and the change is logged in the editorial changelog that the team keeps privately. That habit is what keeps the policy honest over time.
Closing note on reader trust
The Guru11 India site is built on the assumption that a reader will return only if the editorial work is useful and the privacy posture is honest. The team would rather lose a feature than lose that trust, and the privacy policy is one of the public artefacts that proves the trust is real. A reader who spots a privacy concern can use the contact channel to flag it, and the team takes that kind of correction seriously.