Security
Security at Regsta: data separation, hosting and the audit trail
Each company's data is kept apart by row-level security in the database. Regsta's database and sign-in are hosted by Hetzner in Falkenstein, Germany, and the application runs on Vercel in Frankfurt. Connections use TLS, and clock events, corrections, approvals and exports go to an audit trail that cannot be changed during the retention period.
Hosted in Germany
The database and sign-in run at Hetzner in Falkenstein, and the application runs on Vercel in Frankfurt. E-mail delivery, rate limiting and push notifications use other providers, each listed on the subprocessors page.
Each company's data is kept apart
Row-level security in the database stops users in another company from reading your data, even if the application has a bug.
Encrypted connections
TLS with HSTS on every connection, a Content Security Policy on every page, and no framing by other sites.
An audit trail the database keeps
Clock events, corrections, approvals and exports cannot be changed or deleted during the retention period. There is no hash chain and no signature.
Roles, and our own access
Each person's role is checked on the server before data changes. Regsta's own operators can reach company data for maintenance, and on each day one does, a row is written to that company's audit trail.
Backups off the server
The database is backed up continuously, with a separate nightly copy, to storage apart from the production server.
No tracking
No advertising or profiling cookies, no Google Analytics and no location tracking of employees.
Found a security problem?
Write to the address below. Tell us what you found and how to reproduce it.
security@regsta.comQuestions about security and data
- Where is Regsta's data stored?
- The production database and sign-in run on Hetzner servers in Falkenstein, Germany, and the application runs on Vercel in Frankfurt. E-mail delivery, rate limiting and push notifications use other providers. The subprocessors page lists every provider, and every connection to Regsta uses TLS with HSTS.
- How is one company's data kept from another's?
- Row-level security in the database stops users in another company from reading your data, even if the application has a bug. The server also checks each person's role before data changes: admin, planner, payroll, auditor or employee decide what someone can see and do.
- What does the audit trail record?
- Clock events, corrections, approvals and exports are written to an audit trail that the database does not let anyone change or delete during the retention period. Corrections keep the original entry and need a reason. The trail has no hash chain and no signature, and Regsta does not say it has one.
- Can Regsta staff see our company's data?
- Regsta's operators can reach company data for maintenance. On each day one does, a row is written to that company's audit trail, so the company can see that access happened. Role checks apply to everyone else, and an admin can export all of the company's data at any time.
- Does Regsta track employees?
- No location tracking, no photos at clock-in and no advertising or profiling cookies. There is no Google Analytics. Employees clock in on their own account, and the time they tap is the time that is recorded, including taps made offline and sent later.
See it for yourself
Create a company account and look at the audit trail, roles and exports with your own test data.