Official Statutory & Workforce Policy โ€ข Staff Scheduling

Attendance & GPS Privacy Policy

Complete operational transparency regarding our Time Clock, GPS Geofencing radius calculations, and non-biometric photo verification modules.

Platform: Staff Scheduling
Est. Read: ~10 min
Version: 3.0 Production
Last Revised: November 16, 2026

Executive Summary & Key Highlights (TL;DR)

High-level takeaways for busy administrators and shift workers.

  • Zero 24/7 background location monitoring; GPS is requested ONLY when pressing Clock In or Out.
  • Configurable geofence radius (100m default) calculated using server-side Haversine geodesic distance.
  • Punch selfies are standard 2D photos for visual manager verification (buddy-punching prevention).
  • NO biometric facial recognition, NO mathematical facial vectoring, and NO biometric template databases.
  • Photos are stored outside the public web server root (/storage/selfies/) behind authenticated proxy endpoints.
  • Complies with Illinois BIPA, Texas CUBI, California CCPA/CPRA, Canada PIPEDA, and GDPR Article 9.

1. Executive Summary & Purpose

At Staff Scheduling, we believe that workforce transparency, accurate time tracking, and employee dignity must coexist seamlessly. Modern businesses require reliable methods to prevent wage theft, ensure worker safety, and eliminate buddy-punching (one employee clocking in on behalf of an absent colleague).

However, these business requirements must never compromise worker privacy or subject employees to unauthorized surveillance. This Policy governs the operational mechanics, data capture principles, storage safeguards, and statutory compliance standards governing the Time Clock Software, GPS Geofencing, and Photo Attendance modules across our web and mobile applications (iOS and Android).

๐Ÿ›ก๏ธ Our Non-Surveillance Guarantee

  • Zero 24/7 Background Tracking: We do not track, poll, or record GPS coordinates when an employee is off-shift, on an unpaid break, or while the app runs in the background.
  • Non-Biometric Visual Review: Selfies are passive photographic attachments for human supervisor visual audit. We never generate facial vectors or biometric templates.
  • Private Non-Webroot Storage: Attendance photos are stored outside public web directories, accessible only through access-controlled proxy endpoints.

2. Controller vs. Processor Distinction

In the context of the Time Clock, GPS Geofencing, and Photo Attendance modules:

  • Your Employer (Data Controller): Determines whether geofencing and photo verification are required, configures the physical workplace coordinates, sets the allowed geofence radius (e.g., 100 meters), and reviews attendance records for payroll processing.
  • Staff Scheduling (Data Processor): Processes location data and time clock photographs exclusively on behalf of and according to the instructions of your employer. We do not sell or monetize this data.

For general data processing terms, review our Privacy Policy and Data Processing Addendum (DPA).

3. GPS Geofencing Architecture & Location Practices

3.1 Point-in-Time GPS Verification (Zero Continuous Tracking)

Staff Scheduling utilizes a strictly episodic, point-in-time geolocation model:

  1. Triggered Exclusively by User Action: Location access is requested by the mobile device only when an employee taps an actionable button: Clock In, Start Break, End Break, or Clock Out.
  2. Instant Disconnect: Once the punch payload is transmitted and acknowledged by our API, hardware GPS access is immediately terminated.
  3. No Background Geofence Tracking: The mobile app does not register continuous background geofencing monitors, persistent background location services, or journey-tracking breadcrumb services.

3.2 Geofence Boundary & Mathematical Radius Calculation

To verify that an employee is on-site when starting or ending their shift:

  • Workplace Center Point: The employer configures the physical workplace coordinates (latitude and longitude) in Location Settings.
  • Configurable Radius: The employer sets an allowed geofence perimeter (default: 100 meters; customizable between 50 and 500 meters depending on facility perimeter).
  • Haversine Geodesic Distance: The server computes the great-circle geodesic distance between device coordinates and the workplace center using the mathematical Haversine formula.
  • Out-of-Bounds Flagging: If the calculated distance exceeds the configured radius, the punch record is flagged as out_of_bounds: true with the calculated variance in meters (distance_meters) for supervisor review.

3.3 What GPS Data We Collect & What We Never Collect

ContextWe CollectWe NEVER Collect
PunchesPrecise latitude, longitude, and device accuracy radius at the exact moment of punch.Historical route trails, velocity, altitude, or turn-by-turn travel history.
Break TimesPoint-in-time coordinates at break commencement and break conclusion.Continuous location monitoring during unpaid meal breaks.
Off-ShiftNothing.Background location tracking outside scheduled working hours.
Personal TimeNothing.Personal residence tracking, transit, or weekend activity.

4. Photo Attendance & Non-Biometric Architecture

4.1 Purpose: Buddy-Punching Prevention

When enabled by an employer, the Photo Attendance module requires the employee to take a real-time photographic snapshot ("selfie") directly through the mobile app camera when clocking in or out. The sole purpose of this feature is to prevent buddy-punching.

4.2 Explicit Non-Biometric Architecture (No Facial Recognition)

No Biometric Data Generated

Staff Scheduling is deliberately engineered without biometric recognition capabilities. We do not scan facial geometry, measure pupil distance, map facial contours, extract mathematical vectors, or run AI face-matching algorithms. Punch photos serve purely as passive photographic attachments for occasional human visual inspection by authorized managers.

4.3 Storage Security: Private Non-Webroot Architecture

Unlike standard websites that store uploads in public folders, StaffScheduling isolates media:

  • Non-Public Webroot Directory: Punch photos are stored in an encrypted server directory outside the public web root (/storage/selfies/YYYY/MM/<hash>.jpg). Direct URL access is impossible.
  • Access-Controlled Proxy Endpoints: Photos can only be viewed via secure proxy endpoints (/api/timeclock/selfie.php) requiring active session authentication.
  • No Search Engine Indexing: Media endpoints return strict X-Robots-Tag: noindex, nofollow headers.

5. Role-Based Access Controls (RBAC)

Staff Scheduling enforces strict least-privilege Role-Based Access Controls governing attendance logs:

  • Employee: Can view only their own personal punch history, timestamps, and attached photos.
  • Peer Employees: Strictly blocked from viewing any coworker's timesheet or photos.
  • Location Manager: Can inspect records only for employees stationed within their explicitly assigned location.
  • General Manager / Owner: Can view attendance records across authorized company branches.
  • Audit Trail: Every administrative timesheet adjustment or photo review is recorded in an immutable audit log.

6. Data Retention, Archival & Purging

Data CategoryActive Retention WindowArchival & Purge Protocol
Punch Photos (Selfies)Retained during active employment or organization billing cycle.Automatically purged upon employer cancellation or within 30 days of employee account deletion.
GPS Punch CoordinatesStored alongside timesheet logs for statutory payroll records.Permanently deleted or anonymized upon organization closeout or employer instruction.
Off-Shift Data0 seconds.Never collected, never stored.

7. Statutory Compliance & Biometric Laws

Staff Scheduling is engineered to facilitate compliance across key privacy jurisdictions:

  • Illinois BIPA (740 ILCS 14/): Because Staff Scheduling does not scan facial geometry or extract mathematical templates, no biometric identifiers are generated. However, employers operating in Illinois are advised to maintain employee notice.
  • Texas CUBI & Washington State: Operates as a passive photo attachment rather than a biometric scanner under Tex. Bus. & Com. Code ยง 503.001.
  • California CCPA / CPRA: Full disclosure of point-in-time geolocation collection for employment verification without commercial sharing or selling.
  • Canadian PIPEDA: Adheres directly to the Office of the Privacy Commissioner of Canada guidelines regarding proportionate workplace monitoring.
  • GDPR Article 9: Photos for human visual inspection constitute standard personal data under Article 6(1)(f) (Legitimate Interests) rather than Article 9 biometric special category data.

8. Employer Obligations & Model Consent Notice

Employers (Data Controllers) bear legal responsibility for deploying attendance tracking in compliance with local labor statutes:

  1. Advance Notice: Notify employees before activating GPS geofencing or photo verification.
  2. Device Accommodation: Provide an on-premise shared time clock tablet (Kiosk mode) or manual punch workflow if an employee lacks a personal smartphone.
  3. Reasonable Perimeter: Configure geofence boundaries that mirror the physical workplace without capturing public roadways or private residences.

Model Employee Onboarding Notice (For Employers)

"Our workplace uses Staff Scheduling to record shift hours. When clocking in or out via the mobile app, the system checks your point-in-time GPS coordinates to confirm you are within the designated workplace perimeter ([e.g., 100 meters]). No location tracking occurs off-shift or during unpaid breaks. If photo verification is enabled, you take a snapshot upon punch to prevent buddy-punching. The photo is stored securely for visual supervisor review and does not use facial recognition or biometric scanning."

9. Employee Rights & Inquiries

Employees maintain clear rights regarding attendance records:

  • Right to Inspect: View recorded timestamps, geofence distances, and attached photos directly in the mobile app.
  • Right to Request Corrections: Request manual adjustment from a manager if a device hardware error marks a punch as out-of-bounds.
  • Right to Account Erasure: Delete account records under Settings โ†’ Security โ†’ Delete Account or via our Account Deletion Tool.

10. Technical Safeguards & Storage Security

Attendance logs and photo files are fortified with technical safeguards:

  • TLS 1.3 Encryption: All device-to-cloud communications are encrypted in transit with forward secrecy.
  • AES-256 Storage: Filesystem storage and databases are encrypted at rest.
  • Directory Traversal Shielding: Proxy endpoints enforce strict canonical path validation (realpath()) ensuring requests remain confined within the storage sandbox.

11. Contact & Privacy Office

If you have questions regarding our GPS geofencing, photo verification architecture, or need support: