Privacy Policy

SarkariUpdatesDaily is an independent information and learning platform. This policy covers the public website, learner accounts, course purchases, separate partner accounts and the Android app. It does not replace the privacy policies of a government department, payment provider or another website you choose to open.

Information we handle

Account and profile details

When you register, we store your name, email address, optional mobile number, password hash and optional profile photo. We also keep the information needed to show purchased courses and manage account access.

Orders and support

A course order can include your name, email address, optional phone number, course, amount, order status and payment reference. A support message contains whatever details you decide to send.

Technical and qualified-view records

Servers can record an IP address, requested page, browser or app version, time, device type and security events. For a qualified content view, the system keeps one-way keyed hashes derived from a first-party visitor or app-installation identifier, a shortened network prefix and the user agent, plus visible reading time and limited interaction signals. The qualified-view record does not store the raw IP address.

App preferences and public cache

The Android app may keep your theme choice and a limited cache of public jobs, news, categories and courses on your device so screens can load more quickly.

Partner application details

A partner application uses a separate partner account and can include a profile photo, name, email address, mobile number, postal address, bank account details, Aadhaar document and bank proof. These details are collected for partner identity, payment-detail and eligibility review; they are not learner-profile fields.

How the information is used

We use information to provide requested pages, create and protect accounts, verify course orders, unlock purchased content, send essential account messages, answer support requests, prevent misuse, maintain backups and meet record-keeping requirements that apply to the service. If checkout creates an account for a new customer, a temporary password can be emailed once and should be changed after signing in.

We do not sell personal information.

Partner applications, consent and private KYC

A partner account is separate from a normal learner account and from an administrator account. Partner information is used to receive the application, verify the applicant and payment details, let an authorised administrator review the request, communicate a decision, and operate any partner access that is later approved.

Consent basis: the final review step asks the applicant to actively confirm a declaration before the application can be submitted. That affirmative choice allows us to use the submitted partner and KYC information for the review and partner-management purposes explained here. An application cannot be considered without the required information and declaration.

The partner photo, address and bank fields, Aadhaar files and bank proof are kept in private storage. The address and bank fields and uploaded KYC files are encrypted at rest by the partner system. They are not placed in the public media library or shown on the public website. Access is limited to the applicant and authorised administrators who need it for review or account administration. Encryption and access controls reduce risk, but no storage system can promise absolute security.

An administrator may approve, send back or reject an application, choose the partner permissions that are actually needed, and block or unblock approved access when security or misuse concerns arise. Audit records can keep the application status, decision, responsible administrator, permission changes, blocking events and related notes so that important actions can be traced. These records are not a public activity feed.

If partner revenue is enabled, we keep a private statement of publishing credits, qualified-view milestone credits, holding dates, adjustments, withdrawal requests, decisions, payment status and bank transaction references. A view is considered only after minimum visible reading time and either an interaction or a longer passive-reading period. One counted view per visitor and item per day, replay protection, partner/admin self-view blocking, bot and prefetch checks, rate limits and daily network caps help reduce manipulation. These controls reduce abuse but cannot prove that every visitor is a different person. Amounts are linked to the partner account and approved content so the same submission or view milestone is not paid twice. The public website does not display a partner's balance or payout history.

A withdrawal captures an encrypted snapshot of the supplied bank details so the administrator can verify which account was selected when the request was made. The normal screen shows only the final digits. An authorised administrator must re-confirm the current admin password before full bank details or the encrypted payout snapshot can be viewed for payment review. Bank and ledger records may be retained for transaction, accounting, dispute, fraud-prevention and audit purposes even after partner access ends.

A partner can ask for a correction, application withdrawal, account closure or deletion review through the Contact and Support page, preferably from the email registered on the partner account. We verify the request before acting. Some application, decision, security, dispute, transaction or audit records may need to be retained for a reasonable period or as required by applicable obligations, so a request does not promise immediate deletion of every record. Withdrawing before a decision will stop the application from being considered.

Website cookies and optional services

Necessary cookies support sign-in, security, form protection and your saved consent choice. Optional preferences, analytics and advertising services remain off until you allow their category through the website consent controls. The consent choice is normally remembered for 180 days and can be changed from Cookie preferences. A browser Global Privacy Control signal keeps the advertising category denied while that signal is present.

When you voluntarily open a course affiliate short link, a first-party referral identifier can remember that course referral for the configured attribution period. We store privacy-protected visitor, network-prefix and browser hashes to count daily unique clicks, reduce repeated or automated activity and connect a later verified order to the referring user or partner. We do not store the raw IP address in the affiliate-click table. Referral and commission records may include the course, referring account, click time, order, rate snapshot, payout state and fraud-review notes.

The website also uses a random first-party identifier to deduplicate qualified views and protect the partner revenue programme. It is necessary anti-abuse storage, is not an advertising identifier and is not shared with advertisers. The Android app creates a random installation identifier in secure device storage for the same purpose. Clearing website data or reinstalling the app may replace an identifier, but network caps and other checks still apply.

Google Drive-hosted course media is click-to-load: a connection to Google is made when you choose to open that media. Custom scripts enabled by the site administrator may have their own privacy terms and are loaded only in the consent category assigned to them. Read the Cookie Policy for details.

Payments and external services

Online payments are completed through PayU. We use the order result and payment reference to confirm access, but we do not ask you to email card numbers, CVV values, banking passwords or OTPs. PayU handles payment information under its own terms and privacy policy. Official notices, application links, social networks and other third-party pages follow their own policies once you leave this service.

The Google Play version of the Android app is consumption-only for digital courses. It does not expose PayU checkout, create or share a digital-course purchase referral link, or direct a learner to another payment method. A learner who already owns access may sign in and use the eligible course in the app.

User affiliate payout profiles and partner bank details are encrypted at rest. A payout request keeps an encrypted destination snapshot so later profile changes do not silently alter an already requested transfer. Administrators see a masked destination in normal lists and may process the request under access controls.

Android advertising choices

When enabled, mobile ads may include labelled banners in reading areas, interstitials at reading breaks and App Open ads at suitable launch or resume moments. Frequency limits apply, and an unavailable ad does not prevent you from reading.

An optional rewarded ad can provide ad-free reading on the same device for the duration shown before you choose to watch. You can skip the offer. The benefit starts only after the advertising SDK confirms completion; it has no cash value and does not unlock paid courses. The app stores the reward expiry, launch count and ad-frequency timestamps locally, so the remaining benefit and cooldowns normally survive an app restart. This benefit is not tied to your account or transferred across devices, and clearing app data or reinstalling may remove it.

When mobile advertising is enabled, the Android app may use the Google Mobile Ads SDK. Depending on your device, region and choice, Google and its partners may process an advertising identifier, app interactions, diagnostics and approximate location derived from network information to deliver, measure, limit and protect ads. The app uses Google's User Messaging Platform (UMP) where available to present mobile advertising choices.

The Android UMP choice is separate from this website's cookie preference. Changing one does not automatically change the other. Refusing personalised ads may still allow contextual or limited ads. Ads are kept away from login, registration, checkout, account-deletion and protected course-video flows.

Sharing

Information is shared only when reasonably needed to operate the service—for example with authorised partner reviewers, hosting, email, payment or security providers—or when a valid legal requirement applies. Each external provider processes information under its own contract and policy. We do not provide account information to government departments simply because a notice on the site relates to that department.

Retention, backups and security

Live learner and partner account, application, decision, order, support and audit records are kept only as long as reasonably needed for access, review, support, dispute handling, fraud prevention and record keeping. Detailed qualified-view fingerprints and engagement signals are normally pruned after 90 days; aggregate view totals and financial ledger milestones may be retained longer for reporting, payment, dispute and audit needs. Removed information may remain for a limited time in protected backups until the normal backup cycle replaces it; backup copies are not used as active account records. Reasonable technical and organisational safeguards are used, but no website or app can promise absolute security.

Your choices

• Edit your name, mobile number, password and profile photo from your profile.

• Review or change website choices from Cookie preferences.

• Use the Android app's privacy controls and your device advertising settings for mobile advertising choices.

• Request account deletion from the app or the Delete Account page.

• For a separate partner account or application, request correction, withdrawal, closure or a deletion review through the Contact and Support page.

An account-deletion request restricts normal access immediately. You can cancel during the first 30 days. After that recovery window, login and recovery stop and the request becomes eligible for permanent deletion. If it is not completed manually, the scheduled cleanup completes the deletion at the end of the 60-day lifecycle. A payment provider or another independent service may retain its own records under its policy.

Children

The service is not designed for a child under 13 to create an independent paid-course account. A parent or guardian should supervise any use or purchase by a minor and should contact us if an account was created without appropriate involvement.

Policy changes and contact

We may revise this page when the service or its providers change. The date at the top will show when the wording was last reviewed. Questions or privacy requests can be sent to sarkariupdatesdaily@gmail.com. Please do not send passwords, OTPs or full card details.

For information about independent job notices and external application links, also read the Disclaimer.