1. About this policy
Your employer or organization manages your workforce account, the information it enters, and the attendance policies and optional features it enables. Information collected can therefore differ between organizations and roles. Ask your organization about its own employment privacy notices and requirements alongside this policy.
EMAS is intended for organizational workforce use, not as a service directed to children.
2. Information we collect
- Accounts and contact details: names, email addresses, phone numbers, account and employee identifiers, sign-in credentials, roles, invitations, and account status.
- Employee and organization information: company and branch details, departments, designations, employment status and dates, and information supplied by your organization. Optional employee fields include date of birth, gender, marital status, profile-photo references, blood group, and salary grade. Blood group is health information; salary grade may describe compensation classification.
- Attendance and work activity: check-in and check-out times, breaks, shifts, attendance corrections, work-from-home or outdoor-duty records, site visits, approvals, and workforce reports.
- Location: precise or approximate coordinates, accuracy, timestamps, and location history when location-based attendance or tracking is used, including background collection where enabled and permitted.
- Devices and security: device identifiers, device names and platform details, trusted-device records, IP addresses, user-agent information, sessions, and security or activity records.
- Notifications:notification content, delivery and read status, browser push subscription details when supported and enabled, and, when you enable notifications in the Android app, that device's Firebase Cloud Messaging registration token. Each subscription or token is stored with your account, organization, device platform, the sign-in session it was registered under, its status, and timestamps.
- Attendance selfie photos:when your organization's attendance policy requires or enables a selfie check-in, EMAS stores a reference to the captured image, capture time, and device information. This is distinct from face verification below and can be an active feature for your organization today.
- Face verification (not an active feature in this release):face verification is built into EMAS but is disabled for this release and not available to any organization today. If a future release enables it, it would additionally collect face captures, encrypted face templates, enrollment requests, and verification results — see "Face verification" below.
- Leave and attachments: leave dates, types, reasons, approvals, and attachment references you or your organization provide. Free-text reasons and attachments may contain personal or health information; provide only what is necessary for the request.
3. How information is used and accessed
Information is used to manage accounts and access, record attendance and breaks, apply organizational attendance rules, manage leave and approvals, verify authorized devices, deliver notifications, maintain security, and produce workforce reports.
Authorized company administrators, HR staff, and other permitted organizational roles can access workforce records and reports within their assigned access. This can include employee attendance, submitted leave information, and live or historical location. EMAS processes information to provide the service, and service providers receive the information needed for their respective functions. Your organization is responsible for how it uses records and reports outside EMAS.
4. Location and background tracking
Location-based features use your device location to associate attendance with a place, check work-area boundaries, record site visits, and show authorized company staff employee locations and location history. Precision depends on device capabilities and the access you allow. Approximate location may not satisfy a work-area check.
Where your organization enables or requires background location for attendance, the app can request background location permission and, once granted, collect and send location while an attendance tracking session is active, including when the app is minimized, closed, or not in use. An active session may continue until it is ended; leaving the app is not the same as checking out. Tracking behavior also depends on device settings, connectivity, and operating-system restrictions.
You can review or revoke location access in your device or browser settings. Denial or revocation can limit location-based attendance and tracking. Ask your organization about its attendance requirements and available alternatives. Previously recorded location information is not deleted by changing a permission.
5. Face verification
Face verification is built into EMAS but is disabled for this release and not an active feature for any organization today. The rest of this section describes how it would work only if a future release enables it for your organization; it does not describe current behavior. Where enabled, enrollment would request images from five face angles; attendance verification would submit a face image for server-side processing.
EMAS stores encrypted face templates and enrollment requests, together with verification records such as results, confidence scores, timestamps, and associated device, IP address, or location information where supplied. The face-verification records do not themselves retain the submitted raw captures as image files. This does not guarantee that images cannot be retained by a camera application, a separately supplied image service, or a configured processing provider. Attendance selfie references are separate records.
Availability and any external face-processing provider depend on the service configuration. Contact EMAS and your organization for the processing and retention arrangements applicable to an enabled service before submitting face images. This policy does not represent face verification or liveness checking as available in every deployment.
6. Service providers
- Hosting and database infrastructure: EMAS Attendance uses Render for application hosting and PostgreSQL database infrastructure. Employee, company, attendance, and related application records are stored in the PostgreSQL database hosted on Render. The public EMAS service also uses Cloudflare network delivery. Hosting and network services process requests and information needed to operate and secure the service.
- Email: EMAS integrates with Resend for account and notification emails when email delivery is configured. Email addresses and message content are provided for delivery.
- WhatsApp (Meta):when your organization configures WhatsApp messaging, EMAS uses Meta's WhatsApp Cloud API to deliver attendance or location alerts to configured recipients. Phone numbers and message content are provided to Meta for delivery. This is used only for organizations that have configured it; it is not active otherwise.
- Maps: map views use OpenStreetMap. Loading maps can disclose your IP address and the viewed map area; embedded maps or map links can include coordinates of the location being displayed.
- Browser push:where supported and enabled, subscriptions and notification delivery use your browser's push service. The provider depends on the browser. Browser push is distinct from native mobile push notifications.
- Android app notifications (Google Firebase Cloud Messaging):when you enable notifications in the Android app, EMAS delivers them through Google's Firebase Cloud Messaging. Google receives your device's registration token and, for each notification, its title and text, a notification identifier, and an in-app link. For attendance alerts, that text can include an employee's name, the time, and a place name, address, or coordinates. Notifications are sent marked as private for the lock screen, so Android can hide their text on a secured lock screen, depending on your device settings. The Android app includes Google's Firebase Cloud Messaging library only to receive these notifications.
- Face processing: no particular external biometric provider is identified by this policy. Any provider used for an enabled deployment needs to be identified in the information supplied for that service.
External image and attachment links may use additional services selected by your organization. Ask it which services apply to your records.
EMAS does not use advertising SDKs, analytics SDKs, or crash-reporting SDKs in the website or mobile app.
7. Data retention
There is no single retention period established here for all EMAS records. Retention depends on the record type, organizational requirements, and the cleanup settings enabled for the service. Attendance, location, notifications, and security records may have different retention arrangements. A configured period does not by itself establish that automatic deletion is operating for your organization.
Notification registrations: signing out removes this browser's push subscription and deactivates this device's app-notification token, and EMAS stops sending to a registration once the sign-in session it was registered under ends or is revoked. Registrations are deleted when the associated user record is deleted or the organization's data is purged.
Account or employee deactivation does not erase associated records. Device permission changes and uninstalling the app do not erase server records. Ask EMAS and your organization about applicable periods, face-data retention, backups, and any employment, security, or legal retention requirements.
8. Your choices and deletion inquiries
Contact your organization's administrator or HR team to ask about access to or correction of workforce records, optional information, and the policies applied to your account. You can control location and notification permissions through your device or browser. Privacy rights depend on the laws that apply to you and the organization handling your data.
You can submit a request to delete your account and associated data in either of two ways: from the app, through "Request account deletion" on your account/profile page; or, without the app or an active login, through the public request page at /account-deletion-request, which emails you a confirmation link before anything is submitted. Submitting a request does not delete your account or data immediately: it creates a request for your organization's administrator or HR team to review, and some records may still need to be retained for legitimate business, security, or legal reasons even after a request is approved. Removing an employee or deactivating an account is a separate action and is not the same as deleting its associated data. You may also contact the support address below with a privacy or deletion inquiry; this contact is not an automated deletion facility or a guarantee of deletion. Ask what can be removed, what must be retained, and which organization will handle your request.
Include your organization name and the email associated with your account. Do not email passwords, face images, or unnecessary sensitive documents. Identity and organizational authority may need to be checked before records can be discussed or changed.
9. Security
The public EMAS service uses HTTPS to protect information in transit. Account access is controlled through authentication and role-based permissions. The Android app uses device-protected storage for refresh credentials, and stored face templates are encrypted. These measures do not mean that every record is encrypted in the same way or that any system is completely secure. Protect your device and account credentials, and report suspected unauthorized access to your organization and EMAS support.
10. Contact and policy updates
Who operates EMAS Attendance: EMAS Attendance is an independent software product developed and operated by Ashok Reddy Kundurru. No registered company has been established for this product. Learn more about the product and its developer on our About page.
For EMAS Attendance privacy questions, contact support@emas.app. For employer-specific records, attendance requirements, or retention decisions, also contact your organization's administrator or HR team.
Changes to this policy will be reflected on this page with an updated date. Review it when your organization enables additional features or changes how it uses EMAS.