Security

Permissions enforced by the database

Every read and write is checked against the person's role and the locations they're allowed to see, by row-level security inside the database itself. Hiding a button is never the only protection. Actions that change records (approving time, granting time off, exporting) run through checks that confirm the permission again, and only an admin can approve their own time or time off, which is marked in the audit log and can be switched off.

Separation between companies

Each company's data is tied to that company, and every rule in the database checks it. One company can never see another's records.

Encryption

All traffic uses HTTPS (TLS). Data is encrypted at rest by our database provider. Passwords are never stored, only a secure hash.

Hosting

The database is hosted in London on infrastructure run by Supabase on Amazon Web Services. The app runs on Vercel in London.

Audit trail

Changes to time, time off, rules and people are recorded in an audit log, so companies can see who changed what and when. Every export to another system is logged.

Least data

Location is read once at clock-in, only where a company switches the check on. We don't track people during shifts. Pay rates are shown only to roles that include seeing pay.

Keeping software up to date

We keep the frameworks and libraries ClockinBee depends on up to date and patch security issues promptly.

Report a vulnerability

If you think you've found a security problem, please email info@renewminder.com or use our contact form with the details. Please give us a reasonable time to fix it before sharing it publicly. We won't take action against good-faith research that avoids harming people's data or the service.