Skip to content
Bloomlabz
Attendly app icon

Attendly

Live

Attendance tracking and workforce operations for growing teams.

Privacy Policy

How Bloomlabz handles personal data in the Attendly service.

Bloomlabz Pvt Ltd ("Bloomlabz", "we", "us" or "our") operates Attendly, a business attendance, leave and payroll-support service. This Privacy Policy explains how personal data is handled when the Service is used. Our contact and grievance email is contact@attendly.bloomlabz.com. Our published location is Hyderabad, Telangana, India.

This Policy applies to business users of Attendly and to personal data that a customer enters into, or that is generated through, the Service. It does not replace a customer’s own employee privacy notice or its obligations under employment, tax, labour or data-protection law.

1. Roles and Responsibilities

For customer account, support and billing-contact data, Bloomlabz determines the purposes and means of processing needed to provide and protect the Service.

For workforce data a customer enters or generates in Attendly, including employee, attendance, leave, salary and proof data, the customer is responsible for determining whether and how that processing is permitted. Bloomlabz processes that data to provide, secure and support the Service, and on the customer’s documented instructions, subject to applicable law. A customer must not treat Attendly as transferring its employer responsibilities to Bloomlabz.

2. Personal Data We Collect

Depending on the features used, data may include: account and business details; authorised-user credentials and profile details; employee identifiers and contact details; employment and salary configuration; attendance, leave and payroll records; device and session information; support communications; and limited operational, diagnostic and security logs.

We also collect subscription and billing data: the plan, add-ons and seat packs held, invoice and receipt records, billing contact details, and payment-processor references such as an order, payment or subscription ID and the outcome of a transaction (success, failure, refund). We do not collect or store full card, bank account or UPI details ourselves; those are collected directly by our payment processor, Razorpay (see Section 5).

The kiosk receives an employee PIN for verification. Attendly is designed not to store a raw employee PIN; it stores a salted verification value. The kiosk may collect a compressed selfie as an attendance proof. Proofs are stored in a private location and are intended to be viewed only by authorised users for a legitimate attendance-review purpose.

3. Purpose and Legal Basis for Processing

We use personal data to provide requested features; authenticate and administer authorised accounts and office devices; record, synchronise and review attendance; generate customer-requested reports; provide support; maintain security and service integrity; investigate misuse or incidents; comply with legal obligations; and improve the Service using information that is aggregated or de-identified where reasonably practicable.

We do not sell personal data or use workforce data for third-party behavioural advertising.

Optional usage analytics

Usage analytics is off by default. Owners and Accountants may choose “Share usage analytics” in My Account. When enabled, Attendly sends screen visits, successful logins, employee creation, attendance corrections, checkout marking, payroll actions and feedback ratings/categories to our Supabase-hosted service. Events include a session identifier, platform, app version, account and organisation identifiers and a timestamp; payroll submission/approval events may include a payroll-run identifier. These events are linked to the account, not anonymous. Usage analytics does not include salary amounts, employee PINs, photos, face embeddings or feedback message text.

The choice applies separately to each account on each device or browser. Turn it off in My Account to stop future optional usage events. Withdrawal does not delete previously stored events; deletion requests follow Section 8. Analytics is disabled for kiosk accounts. Business records, security audit logs, essential operational telemetry and feedback you explicitly submit are separate from optional usage analytics and continue when this choice is off. We do not use these events for cross-company advertising tracking.

4. Kiosk photographs and on-device face processing

The kiosk uses on-device passive liveness checks to help detect presentation attacks such as a printed photograph or screen replay. It may also create an on-device face embedding for a one-to-one comparison with an employee reference embedding. Raw camera frames used for these checks stay on the device; when face matching is enabled, the reference embedding is stored server-side with restricted access. Attendly does not use this feature for broad face search, identification of unknown persons, or continuous surveillance.

A face-match result is not a decision that blocks a punch: a low-confidence result may be recorded for authorised customer review. Face embeddings are not made generally available to customer users. Customers must determine whether these features are appropriate for their workplace, provide a clear employee notice, obtain any consent or other authorization required by law, offer any required alternative process, and respond to employee concerns.

5. Disclosure of Personal Data

We may disclose data to the relevant customer and its authorised users; service providers that help us host, maintain, secure or support the Service; professional advisers; competent authorities where required or permitted by law; and parties involved in a corporate transaction, subject to appropriate protections where required. We do not disclose workforce data for an unrelated party’s independent marketing use.

Billing contact details and the minimum transaction data needed to process a payment (such as the amount, currency, plan and order reference) are shared with Razorpay Software Private Limited, our payment gateway and subscription-billing processor, so it can process payments, subscriptions and refunds on our behalf. Razorpay collects and handles card, bank account and UPI details directly and independently of us, under its own privacy policy and terms; we recommend reviewing them before paying. We do not control and are not responsible for Razorpay’s independent processing of that data.

A customer authorises Bloomlabz to use service providers, including Razorpay, as reasonably necessary to provide the Service. We may disclose information where necessary to establish, exercise or defend legal claims, protect people or systems, or investigate fraud or abuse.

6. Retention, deletion and exports

We retain data for the period reasonably necessary to provide the Service, meet the customer’s instructions, resolve disputes, enforce agreements, maintain security records and comply with legal obligations. Customers are responsible for exporting records they need before cancellation or deletion.

An Owner can permanently close a company from My Account after signing in again and confirming the company slug. This removes active company data, private proof/photo files, and Owner, Accountant and kiosk logins. Employee offboarding uses an effective Inactive from date set by an Owner or Accountant: the preceding day is the final active day. New operational attendance and leave stop on the inactive date. Proofs, photos, face templates and biometric metadata become due for deletion after 45 days; remaining identity becomes due for anonymisation after 90 days, subject to resolving historical leave and approving final payroll where required. Holds can extend identity retention beyond Day 90 and are visible to authorised admins. Failed Storage deletions retry without restoring employee visibility. Historical attendance, leave, approved payroll totals and audit chronology remain under an anonymised Deleted employee record. Reactivation before erasure cancels pending retention stages. Legacy inactive employees receive a rollout grace period. Employees should contact their employer for workforce-data requests; support can assist with requests requiring a different legal deadline. Details are published at bloomlabz.com/attendly/account-deletion.

An account that is not on a paid plan when its free trial ends, or whose payment lapses, is automatically moved into a read-only Archived state and, if not reactivated, is automatically and permanently deleted. Section 7 of the Terms of Service sets out this timeline, the notice we send, and how to prevent it. Backup, legal, accounting, security and dispute-resolution copies may persist for the applicable retention period even after account or employee deletion; billing, invoice and payment records are kept for as long as applicable tax, corporate and accounting law requires.

7. Security

We use administrative, technical and organisational measures that are designed to protect data appropriate to the nature of the Service. Access is restricted by role and authentication, sensitive proofs are not publicly available, and service traffic uses encrypted HTTPS connections. Attendly uses hosted Supabase infrastructure, which provides encryption at rest; we do not add a separate client-managed encryption layer for face embeddings. No system, network or transmission method is completely secure. Customers must protect their accounts, devices, employee PIN processes and exported reports, and promptly notify us of suspected unauthorised use.

8. Rights, requests and complaints

Rights available to an individual depend on applicable law and the role in which Bloomlabz processes the data. Employees should ordinarily contact their employer, which controls their workforce data and is best placed to verify and action the request. Account holders may contact contact@attendly.bloomlabz.com for requests concerning account data or this Policy.

We may ask for information necessary to verify a request, direct a request to the relevant customer where appropriate, and decline or limit a request where permitted by law. You may also use any complaint or redress mechanism available under applicable law.

9. Customer responsibilities

Each customer is responsible for the accuracy, lawfulness and appropriateness of the data it supplies; its notices, consents, authorisations and workplace policies; responding to employees; configuring access; reviewing reports before use; and complying with all employment, payroll, tax, biometric and privacy obligations applicable to it. A customer must not use Attendly to make unlawful, discriminatory or solely automated decisions about an individual.

10. Grievance Officer

For concerns about this Policy, contact:

Grievance Officer
Bloomlabz Pvt Ltd
contact@attendly.bloomlabz.com
Hyderabad, Telangana, India

We will address requests and complaints in accordance with applicable law. This contact does not limit any right to use a statutory grievance or redress mechanism.

11. Changes to This Policy

We may revise this Policy to reflect changes to the Service, our practices or law. The current version and effective date will be published in the Service. Where required, we will provide additional notice or obtain a new acceptance before applying a material change.

12. Contact

For privacy questions, requests or complaints, email contact@attendly.bloomlabz.com. This Policy is not legal advice and does not change any rights or obligations that cannot lawfully be excluded.