Everything you need to
hit the ground running.

When an employee clocks in, Clock-me cross-checks three layers: (1) Device fingerprint — a unique ID tied to the registered phone; (2) GPS coordinates — verified against the job site geofence; (3) Behavioral signals — timing and interaction patterns. All three must align. If they don't, the punch is flagged and the manager is notified in real time.

Clock-me uses OS-level signals to detect developer mode, mock location providers, and GPS spoofing apps (common on Android). On iOS, it cross-references the device's location certificate with sensor data. Any discrepancy raises a spoofing flag visible on the admin dashboard, including the app name used to spoof and a timestamp.

Clock-me collects: clock-in/out timestamps, GPS coordinates at punch time, device fingerprint (hashed, non-reversible), and timesheet history. All data is encrypted at rest (AES-256) and in transit (TLS 1.3). Data is stored on ISO 27001 certified infrastructure. Location is only recorded at the moment of clock-in/out — Clock-me does not track employees continuously.

No. GPS is sampled only at clock-in and clock-out, and when a geofence boundary is crossed. The app does not run a background location service between punches. Employees can verify this in their phone's app permissions — location access is set to "Only while using."

Clock-me tracks time to the second — every second counts. Hours are calculated as the exact difference between punch-in and punch-out timestamps with no rounding applied. What you clock is what you pay. Overtime thresholds (daily or weekly) are configured per account in Settings → Payroll Rules, and overtime hours are flagged separately in exports so your payroll system can apply the correct rate.

If there is no internet connection, the system cannot load GPS data and the punch will be blocked. Clock-me requires a live GPS signal and network connectivity to verify the employee's location at the moment of the punch. This is by design — it prevents punches from being submitted without verifiable location data.

The system monitors each registered device within a set timeframe. After that timeframe passes without activity — such as when an employee leaves the company or stops using the app — the device registration is automatically cleared by the system. You can also manually reset it at any time: go to Team → select the employee → Device Settings → Reset Device. The old device is immediately deauthorized and a new onboarding link is issued.

Yes. Since Clock-me uses GPS coordinates to record every punch, the system automatically detects the time zone of the job site based on location — no manual configuration needed. Punches are stamped in the correct local time for that site, regardless of where the employee's device is set. Payroll exports include both local and UTC timestamps for full traceability.

Yes. In Job Sites → Site Settings, you can assign specific employees or crews to each site. If an employee attempts to clock in at an unassigned site, the punch is blocked and flagged. This is useful for multi-client operations where crews should not cross between projects.

The admin dashboard works on all modern browsers: Chrome, Edge, Firefox, and Safari (desktop and mobile). We recommend Chrome or Edge for the live map view, which uses WebGL for rendering. Internet Explorer is not supported.

All timesheet and audit data is retained for a minimum of 3 years on active accounts. Corporate and Enterprise plans include extended retention up to 7 years to meet labor law compliance requirements. You can export the full archive at any time from Reports → Full Export.

Yes. Pro plans and above include REST API access with full documentation. The API supports reading timesheet data, employee records, and punch events. Webhooks are available for real-time push on punch events. Enterprise plans include dedicated integration support for custom HR/ERP systems. Contact app@clock-me.com for API credentials.