Effective date: 3 August 2026
Last updated: 3 August 2026

This Privacy Policy explains how Easysofts Tech ("Easysofts", "we", "us" or "our") handles personal data through the Easysofts website, the AttendSetu mobile application (formerly and/or also known as Accutendance, Android package com.easysoftstech.attendance), its attendance-notification APIs, and related support services (together, the "Services"). It also explains the choices and rights available to parents, lawful guardians, authorised adult school representatives, and other website visitors.

Please read this Policy before using the Services. The AttendSetu application is intended for parents, lawful guardians, and authorised adult school personnel. It is not intended for a child to create or operate an account independently. If you are under 18, please ask your parent or lawful guardian to use the application on your behalf.

SECTION 1   SCOPE AND RESPONSIBILITY FOR SCHOOL DATA

Schools and educational institutions normally decide what student and attendance information is entered into the Services, why it is used, who may access it, and how long the school's official records must be kept. For those records, the school is generally the primary decision-maker and Easysofts processes the information to provide the contracted attendance and notification service. Parents and guardians should ordinarily contact the relevant school first regarding the accuracy, correction, or deletion of school records.

Easysofts is directly responsible for the processing purposes that we determine ourselves, such as operating and securing our website and APIs, providing support, maintaining the application, and displaying advertising. The exact legal roles of Easysofts and a school may depend on the applicable law and the agreement with that school. Nothing in this Policy removes any responsibility imposed on either party by law.

SECTION 2   INFORMATION WE PROCESS

A. Information supplied by a school or entered for sign-in

• School or class code, enrolment number, student name, class/standard, batch, and related school identifiers.
• A school-issued password and any replacement password submitted through the change-password feature.
• Attendance events and status information, such as check-in, check-out, present, absent, event date and time, and school notices.
• Information included by the school in a notification message.

B. Application, device, and technical information

• Firebase installation and messaging identifiers, registration tokens, and topic subscriptions used to route notifications to the correct signed-in account.
• Notification permission and app privacy-choice status, application version, operating-system and device information, IP address, request date/time, and technical or security logs that may be generated when the Services are accessed.
• Notification title, complete message, and receipt time stored in the application's private on-device database for the active account.

C. Advertising and consent information

When advertising is enabled, the Google Mobile Ads (AdMob) and User Messaging Platform (UMP) SDKs may automatically collect or share IP address (which may be used to estimate general location), app interactions such as launches, taps or ad views, diagnostic information, advertising ID, app-set ID, other applicable device/account identifiers, and privacy-consent choices. Google may use this information for advertising, analytics, ad measurement, security, and fraud prevention, subject to the user's choices and applicable law.

D. Website and support information

If you visit our website or contact us, we may receive your name, email address, phone number, organisation, message, IP address, browser/device information, and standard web-server logs. We use this information to respond, provide support, maintain security, and operate the website.

E. Information the AttendSetu mobile app does not request

The current AttendSetu mobile app does not request precise GPS location, contacts, call logs, SMS, camera, microphone, photos/files, or payment-card details. It does not read or store fingerprint or facial templates from the user's phone. A school's separate biometric attendance device may generate an attendance event that is sent as a notification; the school is responsible for explaining any biometric system it operates and the legal basis for that separate processing.

SECTION 3   HOW WE USE INFORMATION

We process information only for relevant, specified, and lawful purposes, including to:

• authenticate the school-issued account and allow a password change;
• associate the account with the correct student, class, standard, and batch;
• route, display, and locally organise attendance alerts and school notices;
• prevent one account's notifications from being displayed to another account on the same device;
• provide customer support, diagnose failures, protect the Services, prevent abuse, and maintain service availability;
• meet legal, regulatory, contractual, audit, and dispute-resolution requirements;
• display and measure banner advertising and manage privacy choices where AdMob is enabled; and
• improve functionality using aggregated or de-identified information where reasonably possible.

We do not use a student's name, enrolment number, password, attendance record, or notification text to create an advertising profile, and we do not intentionally pass those fields to Google AdMob in an ad request. We do not use student attendance records for email marketing or sell them to data brokers.

SECTION 4   AUTHORITY, CONSENT, AND WITHDRAWAL

Depending on the context and applicable law, processing may be based on the informed consent of the adult user or parent/lawful guardian, instructions from and the service agreement with the school, steps necessary to provide the requested service, compliance with law, or another legally permitted ground. The school and any person supplying information must have the authority to provide it and must give required notices and obtain required parent or guardian permission before student data is submitted.

Where processing is based on consent, the person who gave it may withdraw it by contacting the school and/or Easysofts using Section 16. Withdrawal does not affect processing already lawfully completed. If information is essential to authentication, notification delivery, or account security, withdrawing consent may require us or the school to suspend or close access to the Services. We may retain limited information when required by law or reasonably necessary to establish, exercise, or defend legal claims.

SECTION 5   CHILDREN'S AND STUDENTS' PRIVACY

Student records often concern persons under 18. The Services are designed so that a school supplies the student record and an adult parent, lawful guardian, or authorised school representative uses the mobile application. Schools are responsible for identifying the appropriate parent or guardian and, where required, obtaining and maintaining verifiable parental consent before providing a child's personal data. Easysofts may request reasonable information from a school or requester to verify authority before acting on a request concerning a child.

We do not knowingly use student data for behavioural monitoring unrelated to attendance, or direct targeted advertising at children. Advertising, where enabled, appears on the parent/guardian-facing notification-history screen and is not based on attendance records. A child should not independently sign in, manage advertising choices, or use the application. If you believe a child's data was supplied without proper authority, contact the school and Easysofts immediately so the matter can be reviewed and appropriate restriction, correction, or deletion can be arranged.

SECTION 6   NOTIFICATIONS AND ON-DEVICE STORAGE

AttendSetu receives messages through Firebase Cloud Messaging. The Android notification panel shows a shortened preview; the complete message is stored in the application's private local database and can be viewed after opening the app. Notification history is separated by the currently signed-in account. The password used at sign-in is transmitted over HTTPS for authentication and is not saved in the app's local session storage.

On logout, the app clears the active account's locally stored notification history, cancels displayed notifications, requests unsubscription from messaging topics, and requests deletion of the current Firebase messaging token. Unsubscription may complete later if the device is offline. Clearing app storage or uninstalling the app also removes the app's local copy. Logging out does not automatically erase the school's official attendance records or server records; those require a separate request under Section 10.

Android controls how notifications appear on a device and lock screen. Users should protect their device with a secure screen lock and can disable or change notification visibility in Android Settings.

SECTION 7   GOOGLE ADMOB ADVERTISING AND PRIVACY CHOICES

AttendSetu may display a small Google AdMob banner inside the application. Depending on region, consent, account configuration, and Google's availability, ads may be personalised, non-personalised, limited, or not shown. The app uses Google's UMP tools to request and refresh applicable advertising choices. Where required, users can revisit those choices from Ad privacy choices in the application menu. Users can also reset or delete the Android advertising ID through Android's privacy settings.

Google's independent handling of information is described in How Google uses information from sites or apps that use its services, the Google Privacy Policy, and Firebase privacy and security information. Google's policies and retention periods apply to data controlled by Google.

SECTION 8   WHEN INFORMATION IS SHARED

We may disclose information only as reasonably necessary for the purposes described above:

• School or institution: to the school responsible for the relevant student record and authorised staff.
• Google service providers: Firebase Cloud Messaging for notification delivery, and Google AdMob/UMP for advertising, measurement, consent, security, and fraud prevention.
• Infrastructure and support providers: hosting, database, network, security, backup, and technical-support providers acting under appropriate instructions or terms.
• Legal and safety reasons: when required by applicable law, court order, lawful government request, or when reasonably necessary to protect rights, safety, systems, users, or prevent fraud and abuse.
• Business reorganisation: as part of a merger, acquisition, financing, restructuring, or sale of relevant assets, subject to appropriate confidentiality and continued protection.

Easysofts does not sell or rent student names, login credentials, attendance records, or notification content. Advertising providers may collect and share the device and advertising information described in Section 2(C) under their own terms; that advertising disclosure is not a sale of school attendance records by Easysofts.

SECTION 9   INTERNATIONAL PROCESSING

Easysofts is based in India. Some service providers, including Google, may process information on servers located in India or other countries. Those countries may have different data-protection laws. Where applicable, we and participating schools will take reasonable steps required by law and provider agreements for permitted cross-border processing. Transfers remain subject to any restriction issued by a competent authority.

SECTION 10   RETENTION, DELETION, AND ACCOUNT CLOSURE

• On-device history: retained on the device until the active account logs out, app data is cleared, the app is uninstalled, or the device operating system removes it.
• School-issued account and attendance records: retained under the school's instructions, service agreement, academic/administrative requirements, and applicable law. When the specified purpose ends and no legal or dispute-related need remains, the responsible party should delete or anonymise the data and allow routine backup copies to expire.
• Notification delivery and server/security logs: retained only for as long as reasonably needed to deliver the service, investigate errors or abuse, maintain security, satisfy contractual or audit needs, and comply with applicable retention law.
• Support communications: retained while the request is open and afterwards for a reasonable period needed for follow-up, security, legal compliance, or dispute handling.
• Third-party data: retained by Google and other providers according to their policies. For example, Firebase states that Firebase installation identifiers are retained until an applicable deletion call and may take time to be removed from live and backup systems.

Users do not create an independent account inside AttendSetu; the school issues the login. To close or delete a school-issued account, a parent/guardian should contact the school or send a request to contact@easysoftstech.com. Include the school/class code, enrolment number, school name, requested action, and a safe way to verify parental/guardian authority. Do not email your password. We may forward the request to the responsible school and may request verification before disclosing, correcting, or deleting a student's information. We will act without unreasonable delay and within the time required by applicable law. Some information may be retained when lawfully required; we will explain the reason where permitted.

SECTION 11   SECURITY

We use reasonable administrative, technical, and organisational safeguards appropriate to the nature of the Services. Measures in the current application include HTTPS/TLS transmission, access-restricted app storage, disabled Android cloud backup for app data, account-separated notification history, session checks, and removal of local history on logout. We also use access controls and service-provider safeguards for hosted systems as appropriate.

No internet transmission, device, database, or storage system is completely secure. We cannot promise absolute security. Users must keep school-issued credentials confidential, avoid reusing the password on other services, keep the device and app updated, and promptly report suspected unauthorised access. If a personal-data breach occurs, we will investigate and provide legally required notifications and remediation in cooperation with the responsible school and service providers.

SECTION 12   YOUR PRIVACY RIGHTS AND CHOICES

Subject to applicable law and appropriate identity/authority verification, a parent, lawful guardian, or eligible individual may request information about processing; access; correction, completion, or updating; erasure; withdrawal of consent; and grievance redressal. A parent or lawful guardian may exercise applicable rights for a child. Requests relating to official school records should first be made to the school, and Easysofts will reasonably assist where it processes those records for the school.

You may also choose whether to allow Android notifications, change lock-screen notification settings, use applicable Ad privacy choices, reset/delete the advertising ID, log out to remove local history, clear app storage, or uninstall the application. If you are dissatisfied with our response, you may pursue the school's grievance process and submit a complaint to the competent data-protection authority when applicable, after completing any grievance process required by law.

SECTION 13   WEBSITE COOKIES, EXTERNAL CONTENT, AND LINKS

Our website may use cookies or similar storage needed for security, login sessions, preferences, and reliable operation, as well as standard server logs. Pages may load resources from providers such as Google Fonts or content-delivery networks, which may receive technical request information such as an IP address and browser details. We do not use school attendance records to track visitors across unrelated websites.

The website and app may link to Google, WhatsApp, social networks, schools, or other third-party sites. Opening an external service is governed by that provider's terms and privacy policy. Easysofts is not responsible for a third party's independent privacy practices.

SECTION 14   PAYMENT INFORMATION

The current AttendSetu mobile application does not collect or process payment-card, bank-account, or UPI credentials. If Easysofts offers a separately contracted paid service or redirects a customer to a payment provider, the payment provider's notice will apply and this Policy will be updated if our own data practices materially change.

SECTION 15   CHANGES TO THIS POLICY

We may update this Policy when the Services, providers, legal requirements, or data practices change. We will publish the revised version on this page and change the "Last updated" date. Where required, we will provide additional notice through the app, website, school, or another appropriate method and obtain consent for a new purpose when applicable. Previous lawful processing is not made unlawful by a later update.

SECTION 16   PRIVACY AND GRIEVANCE CONTACT

For privacy questions, a rights request, account/data deletion, or a grievance, contact:

Privacy & Grievance Contact
Easysofts Tech
SR No. 11/B, Nirmal Park, 2A Building, Flat No. 6,
Dhankawadi, Pune, Maharashtra 411043, India
Email: contact@easysoftstech.com
Alternate email: easysoftstec@gmail.com
Phone: +91 998 899 8535

Use the email subject "AttendSetu Privacy Request". Include enough information to identify the relevant school-issued account and your relationship to the student, but do not send a password, full identity document, or other unnecessary sensitive information by ordinary email. We may provide a safer verification method if additional proof is required.