Privacy Policy

Policy Identity and Scope

One policy for the NAAZ website, applications, and privacy conversations.

This Privacy Policy is provided by Anupama Software, the developer of NAAZ (National Agri Assist Zone). It applies to the NAAZ public website, the NAAZ Android and iOS applications, and information sent to NAAZ for support, contact, privacy, or account-deletion purposes.

A particular explanation applies only when you use the service or feature it describes. For example, location information is relevant only when an application feature requests location and you grant permission.

Responsible organisation: Anupama Software
Policy status: Version 1.0
Effective date: 15 July 2026
Privacy contact: support@naaz.app

Privacy at a Glance

Information should have a clear purpose and a clear boundary.

These principles lead into the complete explanations below. They are part of this policy, not a separate or simplified version of it.

Purpose

NAAZ should ask only for information connected to a real responsibility.

Permission

Location is used only when a relevant feature requests it and you allow it.

Boundaries

NAAZ does not sell personal information or build advertising profiles.

Protection

Access should remain limited to people and providers with a defined need.

Control

You can ask questions, correct information, withdraw permission, or request deletion.

Why Privacy Is a NAAZ Responsibility

Useful information should support coordination without taking control away from people.

NAAZ exists to make agricultural workforce coordination clearer and more dependable. That work may require account details, location, communication, and records of agricultural participation. Each kind of information should remain connected to that purpose.

Transparency is not surveillance. Records should help people understand what happened, protect fairness, and complete agricultural work responsibly. They should not become an excuse for unnecessary observation, unrelated profiling, or unlimited retention.

Information NAAZ Handles and Why

Every category should be understood together with its source, necessity, and purpose.

The public website provides information and email links. It does not use advertising trackers, analytics cookies, public account forms, or behavioural profiling. The NAAZ application uses the information categories below to provide accounts and agricultural workforce coordination.

NAAZ uses Firebase Authentication for phone-number sign-in, Cloud Firestore for platform data, Cloud Functions for backend operations, and Firebase Cloud Messaging for in-app notifications. NAAZ does not use Firebase Analytics or Firebase Crashlytics.

Authorised administrators may access internal operational reports generated from information already collected for platform administration, operational management, dispute handling, safety, and improvement of agricultural workforce coordination. These may include district-wise job summaries, job and payment status reports, Farmer and Agri Service Partner activity summaries, and administrative exports.

Internal operational reporting is not Firebase Analytics, behavioural analytics, advertising analytics, cross-app tracking, cross-site tracking, or advertising. NAAZ does not use personal information for advertising or cross-app tracking.

Current public service

Website visits and email communication

What information: Email address, message, and any information or attachment you choose to send. Web-hosting systems may also create limited technical logs such as an IP address, requested page, time, browser type, or error information.
How NAAZ receives it: You send an email using your own email service. Limited technical records may be created automatically when the website is delivered or protected.
Why it is needed: To understand and answer your message, provide support, receive a privacy request, deliver the website, investigate errors, and protect the service.
Necessity: Email is optional unless you choose to begin a conversation. Technical records should remain limited to what delivery and security require.

Application account

Mobile number, verification, and account access

What information: Your phone number, user ID, one-time-password verification result, account role, account status, and limited authentication or security records.
How NAAZ receives it: You enter your mobile number. A verification service sends and checks the one-time password and returns the result needed to protect access.
Why it is needed: To create and protect an account, confirm that the mobile number can be reached, support sign-in, and help prevent unauthorised access or misuse.
Necessity: Required for account access. NAAZ should not ask you to share the one-time password with another participant or support representative.

Participation identity

Role and profile information

What information: Your user ID, Farmer or Agri Service Partner role, name, relevant local area, and profile details needed to participate. For an Agri Service Partner, this may include agricultural skills, experience, availability, and work interests.
How NAAZ receives it: You provide and update the information in your account.
Why it is needed: To present the correct participation path, make agricultural requirements or contribution understandable, support suitable coordination, and help participants recognise who is involved.
Necessity: Basic role and profile information is required for account participation. Any optional field should be identified when it is requested.

Clarity and local relevance

Language, location, and notification information

What information: Your language preference, your precise location when permission is granted to support nearby agricultural coordination, notification preference, and a device notification token when notifications are enabled.
How NAAZ receives it: You choose a language. Location is received only after a relevant feature asks and you grant device permission, or when you provide an area manually. A notification service supplies a technical token when notifications are enabled.
Why it is needed: Language presents information more clearly. Location helps make nearby agricultural needs or availability relevant. Notifications communicate meaningful account or work updates.
Necessity: Language selection is needed for clarity. Device location and notifications are permission-dependent. Refusing a device permission should not create unrelated disadvantages.

Agricultural coordination

Requirements, participation, completion, and trust records

What information: Other User Content, including agricultural work details, place and timing, applications, selection, attendance, progress, completion, payment-confirmation status, ratings, disputes, concerns, and reliability or reputation information.
How NAAZ receives it: Farmers and Agri Service Partners provide information and confirm significant actions as agricultural work moves through its lifecycle. Responsible administration may add review outcomes where a concern requires attention.
Why it is needed: To make the work understandable, support suitable selection, recognise participation, confirm closure, reduce dependence on scattered memory, address concerns, and strengthen future coordination.
Necessity: Information connected to an agricultural activity is required only to the extent needed for that activity, platform integrity, and fair records. Payment confirmation does not by itself mean NAAZ processes a payment or collects bank details.

Help and accountability

Support, privacy, and grievance records

What information: Your contact details, the question or concern, relevant account or activity references, supporting information you choose to provide, and the response or outcome.
How NAAZ receives it: You contact NAAZ or submit a request. NAAZ records the steps needed to understand, review, and respond.
Why it is needed: To provide support, correct information, respond to a privacy request, review a concern fairly, and demonstrate that the request was handled responsibly.
Necessity: Optional unless you ask for help or exercise a choice. Share only information relevant to the request.

Who Can See or Receive Information

Access should follow responsibility, not curiosity.

NAAZ does not make all account information visible to everyone. The information a person or organisation receives should be limited to what their role and the relevant purpose require.

Farmers and Agri Service Partners

May see information needed to understand a requirement, consider participation, coordinate selected work, recognise who is involved, confirm progress, or understand relevant reliability. Private account and security information should not be shown to other participants.

Authorised NAAZ administration and support

May access information when needed to support users, protect accounts, preserve operational integrity, review concerns, maintain records, or respond to privacy requests. Access should be limited by role.

Technical service providers

May process limited information to provide hosting, authentication, OTP delivery, notifications, secure storage, communication, diagnostics, or other confirmed service functions. They should act only for defined purposes and under appropriate protection.

Institutions and programme partners

Do not receive personal information merely because they are associated with agriculture. Access requires a confirmed programme, a clear purpose, an appropriate legal basis, and information limited to what that responsibility requires.

Legal and safety requirements

NAAZ may disclose relevant information where required by applicable law, a valid legal process, or a necessary response to protect people, rights, platform integrity, or public safety. The disclosure should remain proportionate to the need.

Organisational change

If responsibility for NAAZ is lawfully reorganised or transferred, personal information may move with that responsibility only with appropriate notice, protection, and continued respect for the purposes described here.

What NAAZ Does Not Do

Clear boundaries are part of responsible information use.

No sale of personal information

NAAZ does not exchange personal information with another organisation for payment.

No advertising profiles

NAAZ does not build profiles for targeted advertising or cross-service behavioural advertising.

No third-party marketing

NAAZ does not provide mobile numbers, profiles, or participation records to others for unrelated marketing.

No biometric collection

The current NAAZ product does not require fingerprints, face geometry, voiceprints, or other biometric identifiers.

No hidden AI profiling

The current NAAZ product does not use personal information for automated AI profiling or decisions that replace human judgement.

No unnecessary observation

Location, records, and administration should support a defined responsibility rather than continuous or unrelated surveillance.

How Information Is Protected

Protection requires technology, responsible access, and prepared people.

NAAZ is responsible for using safeguards appropriate to the nature of the information and the harm that misuse could cause. No digital service can promise that risk has been completely removed, so protection must be reviewed as the platform develops.

Technical protection

Secure transmission and protected storage

Account features use secure communication, protected authentication, securely configured storage, backups, and monitoring appropriate to the service.

Access protection

People should see only what their responsibility requires.

Administrative access should be role-based, authenticated, reviewed, and removed when it is no longer needed.

Operational protection

Important actions should remain accountable.

Security procedures, access records, provider review, incident handling, and responsible staff practices should protect information throughout its lifecycle.

Participant protection

Account safety also depends on careful participation.

Keep verification codes private, use only official NAAZ channels, review permission requests, and contact support if account activity appears unfamiliar.

NAAZ reviews encryption, access control, service providers, logging, backups, and incident procedures as part of maintaining the platform's technical security.

How Long Information Is Kept

Information should remain only while its purpose or a lawful responsibility continues.

NAAZ does not apply one retention period to every record. The reason for keeping information, the state of an account or agricultural activity, safety, disputes, and applicable law can require different periods.

Website, contact, and support communication

Kept while the question, support need, or follow-up remains active, and afterward only for a reasonable period needed for continuity, accountability, security, or a legal obligation.

Account and profile information

Kept while an account remains active and then deleted or de-identified after a verified deletion request, except for limited information that must remain for a lawful and explained reason.

Agricultural coordination and reputation records

Kept while needed to complete work, maintain fair operational history, support concerns or disputes, protect participants, and fulfil legal or accounting responsibilities. Records should later be deleted or de-identified when those needs end.

Authentication, security, and technical records

Kept for the limited period needed to protect accounts, investigate misuse, maintain service reliability, and meet security or legal responsibilities.

Privacy and deletion requests

A limited record of the request, verification, decision, and completion may remain so NAAZ can demonstrate that the request was handled responsibly.

Backups and de-identified information

Deleted information may remain temporarily in protected backups until the normal backup cycle replaces it. Information that can no longer reasonably identify a person may be retained for responsible operational understanding.

Your Rights and Choices

Your information should not become something you can no longer question or control.

Ask what NAAZ holds

You may ask for information about the personal information NAAZ processes about you and the purposes for which it is used.

Correct or complete information

You may ask NAAZ to correct inaccurate or misleading information, complete incomplete information, or update information that has changed.

Withdraw a permission or consent

You may change device permissions in your device settings and may withdraw consent where processing depends on consent. Withdrawal does not undo processing that was lawful before withdrawal.

Ask for erasure

You may request deletion of personal information that is no longer needed, subject to information NAAZ must retain for a specified purpose or applicable law.

Raise a grievance

You may raise a concern about how information was handled or how a privacy request was answered and receive a responsible review.

Use other applicable rights

Depending on the law that applies, you may have additional rights, including nomination of another individual to exercise rights in the event of death or incapacity.

Account Deletion

Deleting an account should be understandable, complete, and protected from misuse.

In the app, go to Edit Profile, then Account Management, then Delete Account. A confirmation warning appears before the backend validates eligibility.

Begin the request

Use the in-app Delete Account control. Contact support@naaz.app if you cannot access the account or have permanently lost access to the registered phone number.
Confirm the account

Review the confirmation warning and confirm the request from the signed-in account.
Understand what will happen

Deletion is prevented when active jobs, pending payment confirmation, or open or reviewing disputes exist.
Delete the account and associated information

Eligible deletion removes your NAAZ account, including authentication credentials, your NAAZ profile, your farms, and your in-app notifications.
Deletion completes

You are signed out. Limited jobs, work history, ratings, disputes, and administrative history may remain without keeping the deleted account active.

Public deletion route

Request account and associated information deletion

Use this support route for account-access problems, eligibility questions, or questions about retained records.

Request account deletion

Children's Privacy

NAAZ account services are intended for adults.

NAAZ does not knowingly create accounts for people under 18 or ask children to provide personal information through the public website. References to rural youth describe the wider employment purpose of NAAZ and do not change this account-age boundary.

If you believe a child has provided personal information to NAAZ, contact support@naaz.app. NAAZ will review the information, take appropriate steps to remove it, and consider any protection or legal responsibility that applies.

Changes to This Policy

A policy should change openly when information practices change.

NAAZ may update this policy when the product, providers, law, or operational responsibilities change. The policy version and effective date should make the current text identifiable.

If a change materially affects how personal information is collected, used, shared, or retained, NAAZ should provide appropriate notice and seek fresh consent where required. A policy update does not by itself authorise an unrelated new use of information.

Privacy Questions and Grievances

A privacy concern should have a clear human path.

Contact Anupama Software at support@naaz.app for a privacy question, access or correction request, consent withdrawal, deletion request, children's privacy concern, or grievance about how NAAZ handled information.

Explain the request in ordinary language and include only information needed to identify the relevant account, message, or agricultural activity. NAAZ may ask for proportionate verification before disclosing, correcting, or deleting personal information.

Privacy and grievance contact

Anupama Software

support@naaz.app

NAAZ should acknowledge the concern, review it responsibly, explain the outcome, and identify any further route available under applicable law.

Reflective Principle

Information should support people and responsible coordination without becoming unnecessary observation.

Privacy grows through clear purpose, limited access, careful protection, responsible retention, and choices that people can genuinely exercise.