Skip to content
Last updated 22 Nov 2026

Privacy Policy

What personal data AttendifyDesk handles, in which role, which service providers are involved, how long data is kept and what rights the tools support.

Two roles: processor for workspaces, controller for the website

For data entered into a workspace — attendance, leave, payroll and employee records — the customer (the company whose Admin created the workspace) decides why and how the data is used. AttendifyDesk processes that data on the customer's behalf to run AttendifyDesk. Employees who have questions about their records should contact their company's Admin first.

For this marketing website and for the account details we need to run the service (such as the Admin's email and billing contact), AttendifyDesk acts in its own right.

Data handled inside a workspace

The following categories are processed to provide the service. All of it is isolated per company at the data layer.

  • Identity and profile: name, work email, profile photo, role, department, team, shift, joining date and employment status; private HR notes written by admins.
  • Attendance: check-in and check-out times, a check-in face photo (unless the company switches it off), mode (Office, WFH or On-Duty), WFH and On-Duty requests with destination, purpose and the review decision, breaks, Present / Late / Half-day / Absent status, regularization requests and the declared reasons.
  • Office network: when the company lists its office networks, the internet address an Office check-in comes from is compared with that list at the moment of check-in. It is not stored with the attendance record.
  • Leave: leave types, balances, applications, approvals and notes, delegations, holiday calendars.
  • Payroll (Pro and above): base salary, expected workdays, deductions, net pay and payslips.
  • Communication: announcements and acknowledgements, feedback and requests (optionally anonymous), support tickets and attachments, notification preferences.
  • Engagement: attendance score, streaks, badges and leaderboard position; birthday and anniversary dates used for celebration emails.
  • Security: sign-in events, active sessions with device and browser labels, and an append-only audit log of sensitive actions.

Check-in photos, location and anonymous surveys

A face photo is taken at each check-in (unless the company switches it off) and stored as an image with that day's record for review; it is not used for automated face recognition, and it is deleted when an employee is erased. There is no GPS or geo-fencing. Anonymous pulse-survey responses are stored without any user identifier, so they cannot be linked to a person.

Service providers (sub-processors)

AttendifyDesk relies on the following providers to run the service.

  • Paddle — card checkout, subscriptions, invoices and payment methods. Card details are entered on Paddle's checkout, not in AttendifyDesk.
  • Razorpay — UPI and QR-code payments and subscriptions. UPI details are entered on Razorpay's checkout, not in AttendifyDesk.
  • Google (Gmail) — transactional email such as invitations, leave decisions, digests and payment notices.
  • Firebase Cloud Messaging (optional) — browser push notifications for leave events, when enabled.
  • Cloudflare Turnstile — bot protection on sign-in and registration.
  • PostHog — product analytics: usage events sent from the app and the server to help us improve AttendifyDesk.
  • Slack and Microsoft Teams — only when the customer connects an incoming webhook; event summaries are then posted to the customer's own channel.
  • The customer's own webhook endpoints — only when the customer subscribes to outbound webhooks.

Retention

Attendance data older than the customer's retention setting is purged by a monthly job. The default retention period is 5 years and the Admin can change it. Audit logs are append-only and are not purged by retention. When a plan ends, the workspace is paused and data is kept.

Account, billing and support records are retained for as long as needed to run the service and meet legal obligations.

Your rights and the tools that support them

The following features are available regardless of which privacy law applies to you.

  • Access and portability: every employee can download a JSON export of their own data from Settings → Privacy; monthly statements export as PDF and Excel.
  • Erasure: admins can erase an employee's personal details by anonymisation, which keeps attendance history and audit trails consistent without identifying the person.
  • Deactivation: employees can request deactivation from Settings → Privacy; bulk deactivation requires approval from a second admin.
  • Session control: review and revoke active sessions; suspicious sign-ins trigger an alert email.
  • Notification choices: email preferences are managed in Settings.

Security

Passwords are hashed with bcrypt (cost 12). Access tokens last 15 minutes and are refreshed from an httpOnly cookie (30 days with "remember me", otherwise 1 day). Tenant isolation is enforced at the data layer, access is role-based, and billing webhooks are signature-verified. The Security & Data Protection document describes the controls in more detail. No certification is claimed.

This website

The marketing website sets no analytics cookies. It stores your light/dark theme preference in your browser's localStorage. Contact forms send the details you enter to the sales or support mailbox you choose. See the Cookie Policy.

Contact

Privacy questions and data requests: support@attendifydesk.com.

Questions about this policy? Email support@attendifydesk.com.

All policies

Ready to get your team started?

Create your workspace in minutes, then choose Basic or Pro when you are ready.