Privacy policy

AttendancePulse processes account, billing, enquiry and support information to operate the service. For employee records submitted by a business, that business determines the purpose of collection and access; AttendancePulse processes the information to deliver the configured service.

Employees should contact their employer first about attendance corrections, workplace policies and employee-data requests. The legal operator’s name, address, privacy email and grievance contact are pending confirmation before this policy is adopted.

• Business and account details: business name, account-holder name, email, phone, organization settings, roles and account identifiers.
• Workforce records: employee names/codes, contact details, joining dates, locations, assigned shifts, attendance punches, working hours, breaks, leave, holidays, overtime and correction decisions.
• Optional salary records: salary amounts, adjustments and calculation breakdowns in entitled workspaces, accessible only to authorized organization owners/admins.
• Verification and security: registered-device identifiers, approval/revocation history, QR verification, relevant location measurements and security/audit records.
• Billing: plan, employee capacity, billing period, order/payment references, verification results and transaction status.
• Enquiries and support: submitted name, email, mobile, city, employee count, requirements, ticket messages and attachments.

Location permissions support attendance geofence checks. Location measurements may be recorded when attendance verification is attempted; AttendancePulse is not offered as a continuous background location-tracking service.

Camera permissions support QR scanning and, where separately enabled, face verification. Optional face enrollment can involve a derived face template/embedding rather than storing the enrollment photograph in the standard face-enrollment flow. A template is still sensitive personal information.

Where compatible fingerprint terminals are used, fingerprint enrollment/templates remain on the hardware in the vendor-neutral integration; employee codes and punch events are sent to AttendancePulse. Hardware vendors may process data under their own policies.

Face kiosks and biometric integrations are marked “coming soon” in the public offering. Their inclusion depends on explicit availability, compatibility and entitlement confirmation. Employers must provide appropriate notices and obtain any required lawful basis or consent before enabling biometric/location checks.

• Create and administer workspaces, users and approved devices.
• Record and verify attendance; calculate hours; process leave, corrections, overtime and optional salary calculations.
• Enforce plan entitlements, tenant isolation and role-based access.
• Verify payments, renew subscriptions and send operational messages, receipts and expiry reminders.
• Respond to enquiries and support requests; investigate errors, abuse and security incidents.
• Comply with applicable legal, accounting and recordkeeping obligations.

Workspace information is available to authorized users according to their roles. Salary information is not exposed to managers or employees. Platform administrators may access information as needed for legitimate administration and support.

Razorpay processes checkout/payment information under its own privacy policy. AttendancePulse records payment references and status; it does not require your bank password, UPI PIN or full card details to be entered into an AttendancePulse form.

Configured infrastructure and email providers may process data to host, secure or deliver the service. Contact/custom-pricing submissions are saved and may be emailed to the configured platform-admin inbox. Data may be disclosed when required by law or to protect legal rights and security. Workforce information is not provided for advertising resale.

The production hosting location and complete service-provider list must be confirmed by the operator; this draft makes no guarantee that all information remains in a specific country.

The product uses a self-hosted Java service and PostgreSQL storage. Access is controlled through authenticated sessions, organization scoping and role permissions. Passwords and relevant authentication secrets are stored as hashes. No system can guarantee absolute security; production safeguards and backups depend on the deployed environment.

Subscription expiry locks operational access but does not itself delete business records. Revoked devices retain audit history even when their active employee association is removed.

Records may be retained for service operation, legal/accounting obligations, dispute resolution and security. A defined production retention schedule, backup-deletion process and post-closure retention period require operator confirmation. No automatic deletion deadline or indefinite storage commitment is made here.

The web and mobile applications use necessary browser/device storage for sessions, preferences and related operational state. Mobile credentials may use operating-system secure storage.

The website loads fonts from Google Fonts and the payment window from Razorpay when checkout is opened. Those providers may receive technical information such as IP address and browser details. Their own policies apply. This policy does not claim the website has no third-party requests.

Disabling necessary storage or permissions may prevent sign-in, preference persistence or attendance verification. Any future non-essential analytics or advertising technology should be disclosed and consent obtained where required.

You may request access, correction or deletion of your information, and raise concerns about its use, subject to applicable law, identity checks and legitimate retention needs. Employees should generally direct workforce-record requests to their employer; account holders may contact AttendancePulse support.

You can manage device permissions in your phone settings. Withdrawing a permission can prevent the corresponding attendance method from working; ask your employer about an alternative. Do not send passwords, payment credentials or biometric samples through the public contact form.

Until direct privacy/grievance contact details are finalized, use the website contact form or workspace support for assistance. See Terms & Conditions for service responsibilities. Material policy changes should be published with a revised date and any legally required notice.