Privacy policy
Last updated: 29 October 2026
App, developer and scope of this policy
This Privacy Policy applies to the AadhaarManager Android app, published on Google Play under the developer name Anita Pathak, and the related services provided through mkpathak.com. AadhaarManager users can use this policy to identify the app, its developer, the people responsible for operations and the privacy contact.
- Android app name: AadhaarManager
- Google Play developer name: Anita Pathak
- Related website: mkpathak.com
- App support and privacy contact: support@mkpathak.com
Publisher, operations and contact
mkpathak.com is independently operated by Munish Pathak. Anita Pathak manages general operations, including data-collection coordination, case-study activities, Android app management and user-support coordination. Anita Pathak is also the developer identified for AadhaarManager on Google Play. Operational responsibilities do not give unrestricted access to personal records: access remains subject to the purpose of the task and the permissions described below.
For AadhaarManager or website privacy questions, access or correction requests, or deletion enquiries, contact support@mkpathak.com and identify the app or service concerned. Do not send passwords or full Aadhaar numbers in a support message. AadhaarManager and mkpathak.com are independently managed services; they are not official Government of India or UIDAI apps or websites.
Data collection and case studies
Data-collection activities must identify the requester and intended purpose. Anita Pathak coordinates general collection and case-study operations within that stated purpose. Case-study outputs should use aggregated or de-identified information. Identifiable personal information must not be included in a published case study without the necessary permission and an appropriate basis for disclosure. Assigning operational responsibility does not authorise sale of personal information or disclosure for unrelated purposes.
Why this portal collects information
This website helps schools manage daily tasks, prepare customised forms and collect information through structured requests. Information is stored to support the task for which it was submitted and to reduce repeated work. Public government orders and school reference information are separate from user submissions.
Who requested the data and why
When collecting information, we specify who requested it and what it will be used for. The requesting person's contact details are published with the collection so respondents can ask questions about the request and intended use. This contact information is separate from the private answers submitted by respondents.
Where does our school data come from?
Official school reference information
School reference data is sourced from the official UDISE+ (Unified District Information System for Education Plus) dataset released by the Department of School Education & Literacy, Ministry of Education, Government of India.
Browse UDISE+ reference · Know Your School
Literacy, demographic and population references
Literacy, demographic and population statistics are referenced from the Census of India, maintained by the Office of the Registrar General & Census Commissioner. Refer to the relevant release or reference period when comparing figures.
Browse Census of India reference
How we maintain data integrity
We reflect official public disclosures directly. We do not invent, synthesise or alter school records or postal codes. If an official data point is missing or unverified in government repositories, we identify that limitation transparently rather than estimating or guessing. A blank or unverified value is not treated as a confirmed zero.
A source can change after a copy is imported. If a record appears outdated or inconsistent, use the current official reference and report the school identifier, field and source link to website support. An independently operated website is not a replacement for the government source and cannot amend the source record.
Public references and private submissions are separate
School reference information describes publicly disclosed records. Information supplied through a form is treated as private task data except for limited fields that the form explicitly states will appear in a public response list. For UPS Promotion, the public response list displays only block, school and teacher names; other submitted details remain restricted. Private answers are not provided to third parties for their own use. Read the privacy policy for authorised access and the technical services used to operate the site.
Service request enquiries
The Services Offered form sends your name, email, mobile number, post/designation and requirements to support@mkpathak.com through the portal email queue. The Contact Us form sends your email, mobile number and any name or message you provide to the same support address. These details are used to assess and respond to your request and are not published as a public enquiry. If a data collection is later created, we agree the requester contact details to publish with that collection.
Information we use
Depending on the service or request form, the portal may process school names, UDISE codes, district and block assignments, staff contact and employment details, student information, competition identifiers and dates, and other information requested by the relevant office. Accounts, uploaded documents, submissions and administrative activity are also recorded where needed to operate the service.
Who can access information
Access to administrative records is controlled through login, role permissions and assigned district, block or school. Authorised users can manage records only within their permitted scope. Authorised portal administrators, including Super Admin, have access needed to administer the service. Schools can view or update their submissions when the request settings allow it. When editing is closed, the request administrator or an authorised portal administrator can permit resubmission.
Some request forms are available without login and use a UDISE code to look up school information. Knowing a school reference code does not authorise access to submitted answers. An authorised account is required to read private submission details or change records, subject to the request settings and any specific candidate-correction process described on the form. Public response lists expose only the limited fields disclosed on the relevant form.
Public statistics
Aggregate statistics published on the website are accessible to everyone. The public site provides school reference resources, government orders and school forms. Private operational reports and detailed personnel records are restricted. Where a form explicitly provides a public response list, only the fields identified in its notice are public.
Sharing and service providers
We do not sell personal school records or share them with independent third parties for their own use. Information is used to support schools and authorised users managing their tasks. Technical providers may process information needed to host the website or deliver configured services, such as document storage and email. Browser information processed by advertising services is described below and is separate from school submissions.
Security
The portal uses hashed account passwords, role-based permissions, session protections and audit records for administrative activity. These controls help protect information against unauthorised access. No website or transmission method can guarantee absolute security; users should keep login details private and report suspected misuse to the administrator.
Cookies and visitor statistics
A session cookie supports sign-in, security checks and continuity between visits to portal pages. Built-in visitor statistics use a random session identifier to estimate visits, page views, online visitors and active time. This analytics feature does not store visitor names, account identifiers, IP addresses or visited URLs in its statistics table. Separate aggregate Hot Links counters store public page identifiers and visit/click totals, without visitor or account identifiers. The browser analytics script respects Do Not Track and Global Privacy Control signals. Hosting services may maintain separate operational logs.
Advertising and browser choices
Google advertising code is limited to reviewed public guide pages when advertising is enabled and the visitor has opted in. It is not loaded on data-entry forms, private workspaces, download libraries or shared administrative reports. Google and its partners may place or read cookies and use web beacons, IP addresses and other browser information for ad delivery and measurement. See how Google uses information from sites that use its services and Google advertising choices. A local website preference does not replace any certified consent platform required for advertising in a visitor’s region. Where advertising choices are offered, the portal stores your choice in your browser. You can withdraw a saved advertising choice using the button below. School submissions are not provided to advertisers.
Retention, corrections and requests
Retention depends on the purpose of the request and the administrative needs of the relevant office. Contact the responsible request administrator to correct submitted information or request permission to resubmit. For questions about access, retention or deletion, contact the portal administrator through the Contact us page. Deletion may depend on applicable record-keeping requirements and the authority of the office responsible for the information.
Contact and policy updates
For privacy questions or concerns, use Contact us. This policy may be updated as the portal's services or data practices change. The date above identifies the latest version.