Privacy Policy

Last updated: 14 September 2026

This Policy covers the Sarkari Exam Typing website, Windows app, purchases and support. It explains what information we use, who receives it and how to contact us about it.

1. Who is responsible for your data

Nitin Mathuria owns Sarkari Exam Typing and is responsible for its handling of personal data. He works with the team to operate the service from Sawai Madhopur, Rajasthan, India. Team members may use customer information to handle access, payments and support as needed for their work. The Grievance Officer remains Nitin Mathuria: grievance@sarkariexamtyping.com.

2. What we collect and why

Information	What we use it for
Purchase email, account ID and activation-key records; older account details where they still exist	To create and identify your account, deliver or recover your key, and let you sign in. Current paid sign-in uses the activation key.
Plan, purchase amount, start and expiry dates, device sessions and abuse flags	To provide paid access, calculate upgrade offers and investigate licence sharing.
Requests for paid passages or lessons and request counters	To check the licence before delivering paid content and apply usage limits.
Attempt summaries, including exam, passage, speed, accuracy, mistake count and completion time; locally saved lesson progress	To show results and progress. Website summaries may be saved to your account; the native Windows app saves practice progress on the device.
Order and payment references, buyer email, amount, status, checkout declarations and refund records	To confirm purchases, deliver access, answer billing questions and keep transaction records.
Device/browser identifier, browser or app information, platform, language, timezone and last activity; IP address and browser details on activation	To check access, show devices, support remote sign-out and investigate misuse. Hosting and security services also receive technical request data such as IP addresses.
Support message, supplied name and reply email, page, category, account ID if signed in, and IP address for unsigned submissions	To answer your request, send it to the support team and limit repeated abusive submissions.
Windows app usage data, only if you choose Allow in the app: a random install ID, app version, interface language, typing layout, plan type, screens opened, when lessons and tests open, start and end, scores, activation outcomes, upgrade clicks and the type of any crash	To find where people get stuck and fix the app. Sent to Google Analytics 4. Switch it off at any time under Settings > Privacy in the app. Typed text, passage text, your activation key and your email are never sent.
Pseudonymous presence identifier and current page	To count active browsers/accounts and understand current site usage. See Section 4 for its retention and the separate advertising tools.

Typing is scored on your device. The account result-saving service accepts a compact summary, not the text of every keystroke. Website session recording is a separate process described in Section 4. Do not type passwords, activation keys or other sensitive information into practice or feedback fields.

We use information you provide to fulfil the purchase or support request and information needed to secure the service or meet applicable legal duties. Optional tracking follows the choices and defaults below. If you do not provide a purchase email, we cannot deliver or recover a paid account in the usual way; free practice remains available.

3. Payments

Payments are handled by Cashfree Payments. When you pay, your card, UPI, or bank details are collected and processed by Cashfree under its own privacy policy. We receive order/payment references, buyer information, amounts and status needed for fulfilment and disputes. We do not store your full card number, CVV or UPI PIN. Checkout records include your immediate-access and age/guardian declarations. These are separate from tracking choices.

4. Cookies, analytics and advertising

Google Analytics, Google Ads and Microsoft Advertising tags load before you choose an option in the notice. For visitors in the EEA and UK, Google's analytics and advertising storage starts denied; elsewhere, including India, it starts granted. A saved choice overrides these defaults. Microsoft Advertising uses the browser's time zone to approximate the opt-in region and otherwise starts with advertising storage granted.

Microsoft Clarity loads only after you select “Accept”, in every region. Selecting “Reject” updates Google's consent settings immediately. Reload the page after rejecting so Microsoft Advertising reads the saved choice. Rejection does not remove cookies already stored. Google can still receive measurements without cookies when storage is denied. To change your choice or remove stored cookies, clear this site's browser data; the notice will appear again.

The tools and the information they receive are:

Google Analytics 4 (measurement ID G-PP61TK94C5) — which pages you visit, which links and buttons you click, how far you scroll, how long you stay, and whether you started or finished a typing test. Sets cookies beginning _ga.
Google Analytics 4 in the Windows app (same measurement ID) — the app asks once, after setup, whether it may send usage data. Nothing is sent unless you choose Allow. Events from the setup screens are held on your PC until you answer and are discarded if you choose Don't allow. The app uses a random install ID instead of cookies, and Google receives your IP address with each request. Change the choice under Settings > Privacy; switching it off deletes the install ID from the app.
Google Ads (conversion ID AW-18277916992) — tells us whether an advert led to a purchase, and the rupee value of that purchase. Sets a cookie beginning _gcl and may contact doubleclick.net.
Microsoft Clarity (project xog1n4j4it) — records your session: mouse movement, scrolling, clicks and a replay of the pages you view, so we can see where people get stuck. Recordings can include rendered page text and results; do not assume everything visible on a page is excluded. Payment credentials are entered in the payment provider's checkout. Sets cookies beginning _clck and _clsk.
Microsoft Advertising (UET tag 343267648) — tells us whether an advert on Bing or Edge led you here, and whether you clicked through to the Windows app listing in the Microsoft Store. Sets cookies beginning _uetsid and _uetvid, and contacts bat.bing.com.

When you are signed in, our Google Analytics integration can attach your account ID to measurement events. This is an identifier, even though it is not your email address.

These providers process this data on their own infrastructure, which may be outside India, under their own privacy policies. Google's restricted consent mode permits measurements without cookies; it does not mean there are no network requests to Google. Google explains this behaviour in its consent-mode documentation.

Separately, and regardless of your choice, we run a first-party operational presence counter: a random browser identifier is sent with a heartbeat and stored only as a server-side digest. Signed-in accounts are counted by a pseudonymous account digest. This tells us unique active accounts/browsers and active pages, but does not record raw IP addresses, keystrokes, or a page-view history in the presence collection. This does not mean other service logs or support records exclude IP addresses. Presence entries expire 24 hours after their last heartbeat and are removed by a scheduled daily cleanup; hourly summaries use a 30-day retention cutoff. Actual removal depends on the cleanup completing.

We also use the storage that is necessary to run the app — for example, keeping you signed in, remembering your light/dark theme, local practice progress, and your answer to the notice above. Authentication and device identifiers are also used by our access-control services.

Our pages self-host the web fonts used by the interface. The Firebase software kit is loaded from Google's content delivery network (www.gstatic.com). Loading that software transfers your IP address and request details to Google so it can serve it. Firebase authentication and App Check also communicate with Google to support sign-in and abuse prevention.

5. How we share data

With the service providers who run the Platform for us — Google Firebase (hosting, database, authentication) and Cashfree (payments) — under contract.
With Google/Gmail and Brevo to send activation keys, service reminders and support replies. These providers receive the recipient address and message content. Our code currently tries Gmail first and uses Brevo as a fallback.
Support submitted through “Message us” is stored privately and may also be sent to our support chat through Telegram, including your message, name, reply email and page. A team reply can be sent to you by email. Email forwarding may also involve Cloudflare.
If you choose WhatsApp support, Meta/WhatsApp processes your number and conversation under its own terms. Links to Trustpilot, Product Hunt and SaaSHub take you to separate review services with their own privacy policies.
With Google Analytics, Google Ads and Microsoft Advertising under the regional defaults and saved choices described in Section 4. These tags load before acceptance, and storage may already be enabled outside the opt-in regions. Clarity receives session recordings after acceptance.
With Google's content delivery network, which serves the Firebase software kit and therefore receives your IP address when a page loads (see Section 4).
When required by law, court order, or to protect our rights and users.
We do not sell your personal data.

6. Where data is stored

Our backend functions are configured for Google's Mumbai region (asia-south1). This does not mean every database, authentication, email, payment, support or analytics record stays in that region. Providers may process data in India and other countries. Windows practice progress is also stored on your device. Opening the website from the Windows app uses the website services described in this Policy.

7. How long we keep it

Account and licence records are used while access is needed; plan expiry does not automatically delete the account. Closing an account removes its authentication record, saved server attempts, entitlement and device-session records. Some activation, support, payment and audit records are not removed by that action. Contact us for a review of the remaining personal data and deletion of records no longer needed. Payment and dispute records may need to be retained for accounting or legal obligations.

Deleting the online account does not erase local files or progress on every device, emails, or copies held in provider backups. Local data can be removed using the browser or Windows app storage controls. Provider backup and log retention follows the relevant service settings. Monitoring retention is described in Section 4.

8. Privacy requests and grievances

You can contact us to:

Access a summary of your personal data.
Correct or update inaccurate data.
Request erasure of your data and closure of your account.
Withdraw consent where processing is based on consent.
Raise a privacy complaint with our Grievance Officer.

Email Grievance Officer Nitin Mathuria at grievance@sarkariexamtyping.com, preferably from your purchase email. If that is unavailable, we will arrange another proportionate identity check before disclosing or changing account data. Do not send passwords, activation keys or identity documents in your initial request. We will acknowledge complaints within 48 hours, provide a reference and resolve them within one month of receipt. If a request cannot be fulfilled, we will explain the reason and any applicable retention requirement.

You can also use the account-closure page. Withdrawing information needed to provide paid access may prevent us from continuing that access. Account closure and withdrawal do not remove any refund right required by law.

The DPDP Act, 2023 and its 2025 Rules have phased commencement. As at this Policy's review date, the main processing obligations and the Act's access, correction, erasure, nomination and grievance provisions are scheduled to commence eighteen months after the November 2025 Gazette publication, in May 2027. The requests offered above are available through us now; statutory DPDP rights and Board remedies apply as their provisions commence. See the official commencement notification. This Policy does not limit rights already available under applicable Indian law.

9. Children

Users under 18 must use the service with a parent or guardian, who must complete the purchase and accept the Terms. Checkout asks for an age/guardian declaration; it does not verify the parent's identity or age. Please contact the Grievance Officer if a child has submitted personal data without appropriate involvement so we can review and address it.

10. Security

We use access controls, deny-by-default database rules, server-side payment verification, and secret management for server credentials. Your personal activation key is an access credential delivered to you and must be kept private. No system is perfectly secure. Report suspected unauthorised access to support or the Grievance Officer promptly.

11. Changes

We will publish changes here with a new "last updated" date and provide notice of material changes through the service or purchase email where appropriate. A Policy update does not, by itself, give permission for a new use that requires your consent.

Terms & Conditions · Refund & Cancellation · Disclaimer · Home