Skip to main content
Resultpedia

Privacy Policy

How Resultpedia collects, uses, shares and protects your data — DPDP Act 2023 compliant.

Effective: June 2026  ·  Last updated: 12 June 2026

This Privacy Policy describes how Resultpedia ("we", "us", "our") collects, uses, shares, and protects information when you use resultpedia.com (the "Site"). This Policy is prepared in accordance with the Digital Personal Data Protection Act, 2023 ("DPDP Act") and the rules notified under it, and it additionally describes the disclosures Google requires of every website that participates in the Google AdSense programme.

1. Who we are

Resultpedia is an independent editorial publication operated from Bengaluru, Karnataka, India by the Resultpedia editorial team. We report on Indian government recruitment, examinations, results, admit cards, answer keys and welfare schemes. We are not a government body and we never ask you to submit application forms, fees or identity documents through this Site. For data-protection queries, contact our Data Protection Contact at grievance@resultpedia.com.

2. What information we collect

2.1 Information you give us

  • Email address — only if you write to us or subscribe to an email digest we may offer.
  • Push subscription token — if you allow browser push notifications. Our push system is self-hosted: the subscription endpoint and keys are stored on our own server and are never shared with a third-party push vendor. The token identifies your browser, not you — it contains no name, email or phone number.
  • Correction requests and tip-offs — whatever name, email address and message you choose to include when you email an editorial desk.

2.2 Information collected automatically

  • Server logs — IP address, user-agent, referrer, requested URL, timestamp and response code, kept for routine security and debugging. Retained for up to 30 days, then deleted.
  • Analytics — pseudonymous usage data via Google Analytics 4 and, when enabled, Microsoft Clarity (heat-maps and session replays with all text input masked). Analytics identifiers are not joined to any personal identity because the Site has no login.
  • Advertising data — Google AdSense and its certified ad partners process device and interaction data to serve and measure ads. See Section 7.
  • Local preferences — small values stored in your browser's localStorage (for example your Hindi/English toggle and recent searches). These never leave your device and we cannot read them server-side.

2.3 What we do NOT collect

  • Aadhaar, PAN, voter ID, passport, roll numbers, application IDs, or any government identification number.
  • Payment or card data — the Site sells nothing and takes no payments.
  • Biometric, health, caste, financial or other sensitive personal data.
  • Account credentials — there is no reader login on the Site.

3. Why we process it (purposes and lawful basis)

  • Deliver push notifications you opted in to — consent, withdrawable any time (Section 8).
  • Respond to emails, corrections and grievances — consent / legitimate use.
  • Operate, secure and debug the Site — legitimate use.
  • Measure aggregate traffic and improve coverage — legitimate use (pseudonymous).
  • Serve and measure advertising that funds the Site — consent / legitimate use, with the opt-outs in Section 7.
  • Comply with legal obligations, including IT Rules 2021 grievance handling — compliance with law.

We do not sell personal data, run our own behavioural profiles of readers, or use your data for automated decisions that affect you.

4. Who we share it with (processors)

We share the minimum data necessary with these categories of processors:

  • Hosting — our web host (servers serving resultpedia.com), which necessarily processes IP addresses in transit and in server logs.
  • Google — Google Analytics 4 (traffic measurement) and Google AdSense (advertising; see Section 7).
  • Microsoft — Clarity usage analytics, when enabled.
  • Email delivery — a transactional email provider processes the address and content of emails we send you.

Push notification data is not shared with any push vendor — subscriptions live in our own database. We do not share personal data with any third party for that party's independent marketing.

5. Cross-border transfers

Some processors above store data outside India (Google and Microsoft operate global infrastructure). Transfers occur under those vendors' standard safeguards. If the Government of India notifies restrictions on transfer to specific countries under the DPDP Act, we will comply.

6. How long we keep it

  • Push subscription — until you revoke browser permission, unsubscribe, or the endpoint expires (expired endpoints are deleted automatically).
  • Email correspondence — up to 12 months from our last response, then deleted unless a legal matter requires retention.
  • Server logs — up to 30 days.
  • Aggregate analytics — 14 months (Google Analytics 4 default), then auto-deleted by Google.

7. Cookies, localStorage and advertising

7.1 Cookies the Site itself sets

Resultpedia runs a minimum-footprint cookie strategy. The Site sets one essential session cookie (resultpedia_session) used by Laravel for CSRF protection on form submissions, plus its paired XSRF token cookie. Both are session-scoped, expire when you close the browser, contain no personal information, and cannot be disabled without breaking form submissions. We set no first-party advertising or tracking cookie of our own.

7.2 Third-party cookies

When analytics is enabled, Google Analytics 4 and Microsoft Clarity set their own cookies governed by Google's Privacy Policy and Microsoft's Privacy Statement respectively.

7.3 Google AdSense — required disclosure

The Site shows advertising served by Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website and other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this Site and/or other sites on the internet.

We do not choose which specific advertiser appears on a given page view — Google selects ads contextually and, where permitted, based on interests. Ads are always labelled. If you ever see an ad that asks for exam fees, promises selection, or impersonates a government body, please report it to editorial@resultpedia.com and we will flag it to Google.

7.4 Managing cookies

You can clear or block cookies from your browser settings at any time (Settings → Privacy in Chrome, Firefox, Safari and Edge all expose per-site controls). Doing so may make ads less relevant but will never affect your ability to read any content on the Site — no article, result table or tool on Resultpedia is gated behind cookies, consent walls or sign-ups.

8. Your rights as a Data Principal

Under the DPDP Act you have the right to access a summary of personal data we hold about you, to correct inaccurate data, to erase data we no longer need, to withdraw consent (for example, unsubscribing from push notifications via your browser's site-settings panel takes effect immediately), to nominate another individual to exercise your rights if you are incapacitated, and to grievance redressal.

To exercise any right, email grievance@resultpedia.com with the subject "DPDP Request — [right]". We acknowledge within 72 hours and respond within 30 days. If you are dissatisfied with our response, you may complain to the Data Protection Board of India.

9. Children

The Site is not directed at children under 13. School-board result pages are read by students aged 14–18 and their parents; simply reading a page involves no collection of personal data from anyone. We do not knowingly collect personal data from any minor without verifiable parent or guardian consent, and we do not serve personalised advertising to users Google identifies as under 18. If you believe we hold information about a child without such consent, contact grievance@resultpedia.com and we will delete it within seven working days.

10. Security

We protect data with HTTPS/TLS on every page, role-based access control on the admin surface, audit logging of administrative actions, dependency security patches applied within the working week, and rate-limited public endpoints to deter scraping and credential-stuffing. Editorial accounts use strong passwords and two-factor authentication where supported. We store no payment-card data under any circumstance.

11. Breach notification

If a personal data breach occurs, we will notify the Data Protection Board of India and affected Data Principals as required under the DPDP Rules, generally within 72 hours of becoming aware of the breach, with a plain-language description of what happened and what we are doing about it.

12. Changes to this Policy

Material changes will be posted on this page with an updated "Last updated" date. Significant changes will additionally be announced via a Site banner. Continued use of the Site after a change takes effect constitutes acceptance of the revised Policy.

13. Contact

  • Data Protection Contact: grievance@resultpedia.com
  • Grievance Officer (IT Rules 2021): legal@resultpedia.com — see Copyright & DMCA for the full grievance procedure
  • General queries: see Contact