Record
Employees clock work or submit a missed entry from web or mobile. Offline clock actions keep stable event IDs and synchronize in order, so one tap never becomes two shifts.
For employers operating in Denmark
An inspection, a union claim, or an accountant asking about a Tuesday four months ago. Employees record start, break and finish. The office approves or returns the record with a reason. Regsta keeps the whole sequence, corrections included, so the day can still be explained afterwards.
Operational principle
A correction should add evidence—not erase the decision that came before it.
Built by Keyton ApS · CVR 38508571 · Aalborg, Denmark
One connected workflow
Employees clock work or submit a missed entry from web or mobile. Offline clock actions keep stable event IDs and synchronize in order, so one tap never becomes two shifts.
Managers approve or return submitted records with a reason. A correction creates a linked version beside the original instead of quietly replacing it.
Exports and the inspection package connect approved hours with the audit trail, the compliance findings and the decisions that produced them.
Security boundary
The customer interface is not the security boundary. Authorization and company isolation are enforced again on the server and in the database.
Evidence model
No payment card, hidden trial, or automatic paid conversion. Any future Pro service will be optional, separately priced, and activated only after explicit acceptance. No interest and no fees.
A Danish employer must operate an objective, reliable and accessible system for daily working time, give employees access to their own records, and as a rule retain the records for five years after the reference period. The default limit is an average of 48 hours a week over four months. Regsta supports the documentation and warns on recorded hours; the employer still assesses leave, illness, the overenskomst and any exemptions.
Self-service, without a sales meeting: create the company, add one employee, record a shift and approve it. The goal is that a smaller company is operational in under five minutes. That is a goal, not a promise — it has not been measured with real customers.
Web and native clients can queue clock actions on the device and synchronize them idempotently, in order, when connectivity returns. The app shows whether an action is pending, synchronized or needs attention. Signed-store mobile acceptance is still a separate release gate.
Yes, but never silently. A correction requires a reason and is written to the audit trail; the original and the replacement both remain visible. A company can also open a bounded window for retrospective manual entry, and the source of the entry stays visible on the record.
Approved hours are exported as CSV or standard Danløn, ProLøn and DataLøn payroll files, ready for seamless import with full reconciliation.
No. There is no GPS trail, no geofence and no photo at punch-in. Regsta documents working time, not position. On a shared punch station the boundary is the station's own device credential and a personal PIN, not a location.
Yes. A company defines its own certificate types and a warning window, and Regsta says so before the certificate expires — as information in Compliance Guardian and on planned shifts. Whether the person may still drive is decided by you and your overenskomst; Regsta does not block scheduling. No certificate number, issuing authority or document is stored.
Company isolation is enforced directly in PostgreSQL with forced Row Level Security using a non-bypass application role, in addition to server-side membership and capability checks.
The primary database and login region are configured in the EU. The DPA, subprocessors, processing locations and any transfer basis are reviewed for the specific customer relationship. Anonymisation, deletion and employee access to their own records are built-in product flows. Regsta holds no salary data.
A company can evaluate Regsta, but the current compliance model and product language are designed for employers operating under Danish work-time requirements.
No. Regsta provides operational records and configurable monitoring. An employer remains responsible for its agreements, exemptions, and legal assessment. Nor is Regsta independently certified: repository tests and database-enforced controls are not a penetration test, an ISO certificate, a SOC report, a WCAG audit or a legal opinion.