1. Who we are
EN-Time HR is a workforce management, attendance, payroll and visitor-management software brand developed and operated by Electrohelps Networks Pvt. Ltd. ("Electrohelps", "we", "our" or "us"). The product website is entimehr.com ; the corporate website is electrohelps.in . For privacy questions contact [email protected] .
2. Scope and roles
This policy covers the EN-Time HR website, mobile apps and connected services to the extent they are made available. Where an employer, school or other customer organization determines the purposes of workforce, student or visitor records, that customer typically determines why the data is processed and we process it under contractual instructions. We may independently determine purposes for our website enquiries, service administration, billing, account security and support. Roles depend on applicable law and the relevant customer agreement.
3. Information handled
- Account and identity: name, employee or student identifier, business email, mobile number, role, company, login and authentication events.
- Workforce records: joining, department, designation, employment documents, shift schedules, leave, attendance punches, approvals, reimbursements and exit records.
- Payroll and statutory information: salary information, bank account and identification or statutory details where the subscribed modules require them.
- Attendance verification: location at authorized check-in or check-out, captured selfie or image, timestamps, site assignment, and device-linked attendance identifiers where enabled.
- School information: student identifiers, classes, attendance and relevant parent/guardian contact information when a school enables the education module.
- Visitor records: visitor name, contact, host, purpose, photos where configured, check-in/check-out timestamps and visit history.
- Technical information: IP address, device and app version, diagnostic logs, security events, push-notification tokens, and support correspondence.
- Website enquiries: contact and organization information voluntarily submitted by a prospective customer.
4. How information is collected
Information may be entered by users or authorized organizations, imported from approved biometric/access devices, received from mobile attendance actions, generated by service usage, or provided through support and website enquiries. Actual collection depends on customer configuration, installed integrations and permissions.
5. Purposes and legal bases
- Provide contracted HRMS, attendance, payroll, school attendance and visitor workflows.
- Authenticate users, prevent misuse, apply access controls, log events and protect the service.
- Send authorized operational notices and respond to support requests.
- Maintain records, meet applicable legal obligations and investigate security incidents.
- Improve service reliability through limited technical diagnostics.
Where GDPR applies, processing may rely on contract, legitimate interests, legal obligation, consent or other appropriate lawful grounds as applicable to the particular role and data. Where consent is required, a valid consent mechanism must be used; a user granting a device permission is not automatically consent for every subsequent use.
6. Mobile permissions
Location: for GPS/site attendance when the organization enables it. The intended initial use is foreground check-in or check-out, not continuous background tracking. If a later version enables background tracking, its policy and app disclosures must be updated before release. Camera: for attendance selfies or visitor photos initiated by the user. Notifications: for operational alerts when enabled. Device and operating-system permission controls may restrict those functions.
7. Biometric systems
Compatible external biometric attendance machines may supply a device user identifier and punch event. Fingerprint templates, facial templates or face embeddings are not assumed to be collected by the app; where any deployment does process such sensitive templates, it must be separately documented, secured and disclosed.
8. Sharing and subprocessors
Information may be accessible to the customer organization and authorized staff in accordance with configured roles. We may use hosting, database, backup, email, notification, customer-support and security service providers under appropriate terms. We do not represent that the list of providers is final; see Subprocessors for the current publication process. We may disclose information where lawfully required, or as part of a lawful corporate transaction with applicable safeguards.
9. Data location and international transfers
Data hosting locations and cross-border transfers depend on the agreed deployment and infrastructure. The organization should review deployment documentation and applicable transfer requirements. Specific hosting regions must be verified and published before production launch.
10. Security
We aim to use transport encryption, access controls, least-privilege permissions, authentication, logging, backup and appropriate organizational safeguards. No system can promise absolute security. See Security & Data Protection for details and reporting.
11. Retention, deletion and rights
Data is retained according to customer instructions, contractual obligations, the purpose of processing, backup schedules and applicable law. Closing an app account is not always identical to removal of statutory employment, payroll or school records. Valid requests are reviewed and data not subject to a lawful retention requirement is deleted or de-identified according to an implemented process. See Data Retention and Account Deletion . Rights may include access, correction, erasure, withdrawal of consent, grievance and appeal depending on applicable law and our processing role.
12. Children and students
When used by educational institutions, the school or relevant organization is generally responsible for determining the lawful basis and any parent/guardian authorizations required for student data. We do not intend to use student attendance data for targeted advertising or profiling. Read Student Privacy .
13. Cookies and third-party technologies
The website may use essential functionality and, if separately enabled, analytics or other optional technologies disclosed in the Cookie Policy . The final mobile SDK list and store privacy declarations must match the released binaries.
14. Changes and contact
We may update this policy when services, laws or data practices change and will publish the updated date. For questions and requests contact [email protected] or use Privacy Requests . The verified registered office address and privacy/grievance contact details must be published before launch.