Privacy policy
Your organization’s people data belongs to your organization. Here is what we hold, why, where it lives and how it is protected.
01 Who we are and what this covers
ClockBadger is software for running an organization’s people and work: HR records, attendance, shifts, leave, payroll, projects, time tracking and team chat. This policy explains what personal data passes through clockbadger.com and the ClockBadger app, what we do with it, and the choices you have.
It covers two kinds of data. Customer data is what an organization (our customer) and its people put into ClockBadger. Our own data is what we collect to run the business, such as a demo request or an email you send us. Questions about either go to [email protected].
02 Your employer decides; we process on their behalf
When an organization uses ClockBadger, that organization decides which people are added, what is recorded about them and who inside the organization may see it. For that data the organization is the controller and ClockBadger is its processor: we store and process it to provide the service the organization signed up for, on its instructions, and for no other purpose.
If you are an employee of one of our customers and want to see, correct or delete your records, ask your employer first. They hold the records and can act on them directly. If you contact us, we will pass the request to them.
03 What we hold
Depending on which parts of ClockBadger an organization uses, customer data can include:
- Profile and employment details: name, work email, phone, job title, department, location, manager, joining date and employment status.
- Identity and statutory details, where the organization records them: national ID, passport or visa numbers, tax and pension numbers. Identity numbers are encrypted in the database.
- Attendance and time: clock-in and clock-out times, breaks, shifts, leave, overtime and tracked work time. From biometric devices we receive only the device user number and the punch time, never fingerprint or face templates; those stay on the device.
- Pay: salary structure, allowances, deductions, loans, bank details and payslips.
- Work content: projects, tasks, comments, chat messages and files people upload.
- Recruitment: applications, CVs and interview notes for candidates who apply through an organization’s careers page.
- Account and security data: password hashes (never the password itself), two-factor settings, sign-in times, and an audit trail of who changed what, including the IP address of the request.
From visitors to this website we collect only what you choose to send us, for example through the demo form or by email. The website has no analytics, no advertising trackers and sets no tracking cookies.
04 How we use it
- To provide ClockBadger to the organization: calculate attendance, leave and pay, route approvals, send notifications and keep records.
- To send service email: account invitations, password resets, approval and request notifications, and payslips. We do not send marketing email to people in a customer’s organization.
- To keep the service secure: detect abuse, investigate incidents and keep the audit trail.
- To answer you when you contact us or ask for a demo.
We do not sell personal data, and we do not use customer data to advertise to anyone.
05 Where it is stored, and who helps us
ClockBadger runs on Amazon Web Services in the Asia Pacific (Mumbai) region. The database, uploaded files and backups are stored there and encrypted at rest. We use a small number of service providers to run it:
- Amazon Web Services: hosting, file storage, database backups and sending email.
- Cloudflare: delivers the website and app securely and protects them from attacks. Traffic passes through Cloudflare encrypted.
- Google, only if an organization connects Google Calendar to create meeting links for interviews.
Each provider processes data only to provide its service to us. All traffic to clockbadger.com and the app is encrypted with HTTPS.
06 How we protect it
- Each organization’s data is kept separate from every other organization’s.
- Inside an organization, access follows roles and reporting lines: people see what their role allows, and payroll and personal records need specific permissions.
- Every change to sensitive records is written to an audit trail.
- Two-factor sign-in is available to every user and required for our own administrators.
- Servers accept web traffic only through Cloudflare, and have no open remote-login port.
No system is perfectly secure. If we become aware of a breach affecting an organization’s data, we will tell that organization without undue delay.
07 How long we keep it
We keep customer data for as long as the organization uses ClockBadger, because it is the organization’s record. The organization can delete people and records itself. When an organization ends its subscription and asks us to, we delete its data from the live service. Database backups are kept for 35 days and then expire, so deleted data is gone from backups within that time.
Demo requests and emails sent to us are kept for as long as we need them to reply and follow up, and deleted on request.
08 Your choices and rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, or to object to how it is used. For data your employer controls, your employer handles these requests; for data we control, such as a demo request, email us.
We reply within 30 days. You can reach us at [email protected].
09 Children
ClockBadger is a workplace tool and is not meant for anyone under 16.
10 Changes to this policy
If we change this policy we will update the date at the top of this page. If a change materially affects how customer data is handled, we will tell customer organizations in advance.