AR ADMS Cloud
// Legal

Privacy Policy

Last updated: 18 November 2026

This policy explains how AR Technologies Ltd. handles personal data in AR ADMS Cloud. There are two roles:

  • For employee and attendance data that an organization puts into the service, the organization decides what is collected and why. We process that data on its behalf and only on its instructions. Employees should contact their employer first.
  • For account, billing and website data of our customers' users and of developers, we decide how it is used, as described below.

1. What we collect

Account usersName, email address, password (stored only as a one-way hash), two-factor settings, organization membership and role, sign-in times and IP addresses.
Employees (on behalf of the organization)Name, employee code, branch, department, designation, joining date, device user ID, punch times, the device used, calculated attendance, leave and corrections.
Devices and CollectorsSerial numbers, model and firmware details, IP addresses, connection and heartbeat times, the Windows PC name where a Collector runs.
BillingBilling contact details, invoices, payment status, gateway transaction IDs and payment method name.
DevelopersCompany name, contact email, API clients and usage counts.

2. Biometric data

Fingerprint, face and palm templates are not stored in AR ADMS Cloud. They stay on the attendance devices. When a device sends its user or biometric tables, the service acknowledges them without keeping them; only the punch record (who, when, which device, verification method) is stored.

3. Payment data

Online payments are made on the pages of shurjoPay or bKash. We never receive or store card numbers, card security codes, PINs or wallet passwords; we only receive the result of the payment and its transaction ID.

4. How we use data

  • To provide the service: receive punches, calculate attendance, produce reports, send the notifications and webhooks you set up.
  • To keep it secure: sign-in protection, audit logs of changes, detecting misuse and abuse of the API.
  • To bill: invoices, receipts and renewal reminders.
  • To support you when you ask us, and to tell account owners about important changes to the service.

We do not sell personal data, and we do not use employee data for advertising or for any purpose of our own.

5. Who else receives data

  • Infrastructure providers that host our servers and backups, and send our email, under confidentiality obligations.
  • Payment gateways (shurjoPay, bKash) for payments you start.
  • Apps you connect: software you authorize through our API or webhooks receives the data you allow, and is responsible for it.
  • Authorities when the law requires it. Where allowed, we tell the affected organization first.

6. Security

Browsers, the Windows Collector and the API connect over encrypted HTTPS. Each organization's data is separated in the application and, additionally, by row-level security in the database. Secrets are stored encrypted, Collector requests are signed, access follows roles and permissions, and every change to attendance is recorded in an audit log. Many ADMS devices only support plain HTTP; they are accepted only when their serial number is registered, and their connection carries punch records and device status.

7. How long we keep data

  • Attendance and punch data: for the data retention period of the organization's plan, then deleted.
  • After an organization closes its account: 30 days (to allow an export), then deleted from the live system; backups are overwritten in their normal cycle.
  • Invoices and payment records: as long as tax and accounting law requires.
  • Security and audit logs: as long as needed to protect the service and the organization.

8. Your choices and rights

Users can update their name, email, password and two-factor settings in the panel. Employees can ask their employer (the organization) to see, correct or delete their data; the organization can do this in the panel or ask us for help. Account owners can ask us for a copy of their account data or its deletion at CHANGE_ME_billing@arcloud.bd.

9. Cookies

The panel uses only the cookies needed to keep you signed in and protect forms (session and security cookies). We do not use advertising or third-party tracking cookies.

10. Changes

We will update this page when our practices change and tell account owners about significant changes. The date at the top shows the current version.

11. Contact

Questions about privacy: AR Technologies Ltd., Dhaka, Bangladesh · CHANGE_ME_billing@arcloud.bd