The server sets the time, the database keeps each company apart, and the original record is never overwritten. Here is exactly how — and where the limits are.
08:02:14
Server time · workplace time zone
English is the authoritative version of this security overview. ឯកសារនេះផ្តល់ជូនជាភាសាអង់គ្លេស ដែលជាភាសាផ្លូវការ។
Defense in depth
Each layer assumes the one before it could be wrong. A request has to pass all four to become attendance.
Sends the request over HTTPS with a signed session token. Location is read once, at the slide.
SlidesClock check_in_outThe only way in. Checks geofence distance, the server-observed IP, the registered device and shift rules in one transaction.
PostgreSQL confirms the user holds an active membership in that organization before anything is read or written.
Stamped with the server’s clock. The original event is kept; a correction is added beside it, never over it.
Platform controls
A phone clock is a setting. Attendance never trusts it.
Isolation is enforced by the database engine, not by app code alone.
What was captured and what was agreed later are both kept.
Clients cannot insert attendance rows directly.
GPS is read at the slide, and at no other time.
Personal files are private; old operational data is pruned.
Data minimization
Only what the workplace policy needs, at the moment it needs it. The full list of what is collected and how long it is kept is in the privacy policy.
Least privilege
Roles are enforced by the same database policies as tenant isolation, so a hidden button is never the only thing standing in the way.
Honest limits
Security pages usually overpromise. Here is where ours stops, so you can plan around it.
Device registration is live, but hardware attestation such as Apple App Attest is not. We do not claim SlidesClock is tamper-proof or spoof-proof.
We hold no SOC 2 or ISO certification and do not imply one. The posture rests on hosted infrastructure (Supabase, Vercel) and database-level access control.
GPS, network and device checks are practical signals a workplace chooses. None of them proves who is holding the phone.
Questions
No. SlidesClock records the time from the database server when the attendance function runs. Changing the phone’s time, time zone or offline cache does not change the recorded time.
No. There is no background location tracking. GPS is read only at the moment an employee slides to clock in or out under a GPS policy, or when a manager captures a workplace location to set a geofence.
No. Every table is protected by PostgreSQL Row-Level Security, and policies check that the signed-in user holds an active membership in the organization before any row is returned or changed.
Not the original. Raw punch events cannot be overwritten by employees or managers. A correction is stored as a separate record with the employee’s reason, and the reviewer’s decision is logged with their user ID and a timestamp.
No, and it does not claim to be. It runs on Supabase and Vercel with database-level access controls, HTTPS connections and private storage for personal files.
On iOS, no: attendance checks do not send the SSID or BSSID, so network verification uses the public IP the server observes. Android may send the SSID/BSSID where available. The Wi-Fi password is never collected.
Email support@slidesclock.com or use the contact page with a description and steps to reproduce. Please do not access other organizations’ data while testing.
Write to support@slidesclock.com with steps to reproduce. Please don’t access other organizations’ data while testing.
Last reviewed
