Clock-Me Data Safety Summary
Clock-Me collects and processes only the information necessary to provide secure, compliant, and accurate time-tracking services. This summary aligns with our Privacy Policy and Terms of Use.
📌 Data Collected & Purpose
1. Personal Information
Collected
- Data Types: Name, Email Address, User ID, Role, Address.
- Purpose: Account management, authentication, and linking records to your employer.
2. Location Data
Collected
Updated
- Data Type: Precise Location (GPS Coordinates).
- Collection Methods:
- Punch Snapshot: Point-in-time capture at the moment of "Punch In" and "Punch Out"
- Random Location Check-Ins: Occasional in-app prompts during a shift asking the employee to tap and confirm their location. GPS is captured only when the employee taps to respond — never continuously in the background (only for employees whose employer has enabled shift location verification)
- Collection Trigger: Only at punch events and when the employee taps to respond to a check-in prompt. No timer-based, silent, or background collection.
- Derived & Related Data: An approximate street address is derived from each punch location (reverse geocoding), and punch attempts refused by the server (outside the work area, weak GPS, simulated GPS) are recorded with their coordinates and reason. Punches stopped by the app itself on tap are recorded with the reason, distance from the work location and GPS accuracy only (no coordinates). The time of the GPS reading is recorded with each punch.
- Punch Requests: When GPS is too weak, the employee may send a punch for manager approval; it is stored with the punch coordinates, GPS accuracy, distance from the work location and an optional employee note.
- App Integrity: At each punch the app obtains a Google Play Integrity (Android) or Apple App Attest (iOS) verdict confirming the genuine app on an unmodified device; only the verdict result is stored.
- Visibility: Authorized administrators and managers can view punch locations as coordinates, an approximate address, and a point on a map with its GPS accuracy range, for the locations they manage.
- Purpose: Verifying the employee is at the correct worksite at start of shift, end of shift, and at randomized moments during the shift.
- Background Tracking: NONE. Clock-Me does not track your location continuously in the background. Location is captured only at the discrete moments listed above. Location is never collected when you are off the clock.
3. California Compliance Data
California Only
New
- Meal Break Records: Start time, end time, duration of 30-minute unpaid meal breaks.
- Rest Break Records: Start time, end time, duration of 10-minute paid rest breaks.
- Meal Break Waivers: Digital waivers for shifts ≤6 hours, including:
- Employee signature (typed name)
- Date and timestamp
- Waiver acknowledgment text
- Overtime Calculations: Daily overtime (>8h), double-time (>12h), 7th day overtime.
- Compliance Violations: Records of missed/late meal breaks, missed rest breaks, split shift occurrences.
- Purpose: California Labor Code compliance, penalty calculations, employer reporting.
4. Timecard Attestation Data
Collected
New
- Data Types: Attestation acceptance, digital signature, timestamp, submission source.
- Purpose: Legal compliance, payroll accuracy, audit trail.
- Attestation Text Stored:
"I certify that this timecard is complete and accurate. I confirm that I have recorded all hours worked and that I have not performed any work before my scheduled start time, after clocking out, or while off the clock during meal or rest breaks. I also confirm that all meal periods and rest breaks have been accurately recorded and provided in accordance with company policy and applicable law. I have not worked any unrecorded or 'off-the-clock' time."
5. Device & Identifiers (Fraud Prevention)
Collected
- Data Types: Device ID, Browser ID (UUID), Push Token, Screen Resolution, Timezone.
- Purpose: Fraud prevention (detecting "buddy punching" via device sharing) and sending notifications.
- Note: We do NOT collect browsing history, contacts, or biometric data.
6. App Activity
Collected
- Data Types: Punch logs, timestamps, timesheet actions, break start/end times.
- Purpose: Calculating work hours, payroll accuracy, compliance reporting, and employment history.
7. Error & Performance Data
Collected
New
- Service: Sentry.io
- Data Types: Error logs, stack traces, device type, app version.
- Purpose: Application debugging, performance monitoring, crash reporting.
- Note: No personal data (names, emails) is sent to Sentry.
🔒 Data Sharing
Clock-Me does NOT sell user data. Data is shared only with:
- Your Employer: To facilitate payroll, attendance management, and compliance reporting.
- Service Providers:
- Google Places API: For address autocomplete when creating or editing accounts.
- LocationIQ: For address validation (geocoding) and the approximate street address of punch locations (reverse geocoding).
- Google Maps Platform: For displaying work locations and punch points on maps to authorized administrators and managers (map area only; no employee records are sent).
- Google Play Integrity / Apple App Attest: To confirm punches come from the genuine Clock-Me app on an unmodified device (integrity signals and a one-way hash of the punch request; no readable location or names).
- Expo: For sending push notifications.
- Brevo: For email alerts.
- Sentry.io: For error monitoring and crash reporting.
- Google Analytics: Aggregated, anonymized visitor statistics on our public web pages only (marketing site and login page), subject to cookie consent. Never used inside the authenticated app — no time, attendance, or location data is shared with Google Analytics.
- PostHog: Product usage analytics (features used, general usage patterns) and recordings of app screens used to fix problems. Typed text and images are masked; names, hours and work locations shown on screen can appear in a recording.
- MongoDB Atlas: Primary database hosting for all application data (encrypted at rest).
- Redis: Caching and session management (temporary data only).
- Cloudflare: CDN, DNS, and network security for our web infrastructure.
- Stripe: Subscription billing and payment processing. Card details are handled directly by Stripe; we do not store full card numbers.
- Expo EAS: Mobile app builds and over-the-air updates.
- Railway: Backend/API application hosting.
- Vercel: Frontend web application hosting.
- AI-Assisted Development Tools: We use Anthropic Claude internally for code review, static analysis, and security audits of our codebase. It is not integrated into the live product and has no access to production user data.
- App Distribution: The app is distributed via the Apple App Store and Google Play. These platforms may independently collect device/install/crash data under their own privacy policies; we do not share workforce data with them.
🛡 Security Practices
- Encryption Data is encrypted in transit (HTTPS/TLS) and at rest.
- Authentication Secure token-based session management (JWT).
- Data Minimization We collect only data necessary for time tracking and compliance.
- No Biometrics We do not collect or upload biometric data (FaceID/Fingerprint). Face ID / fingerprint sign-in is checked by the phone; if turned on, sign-in details stay encrypted in the phone's secure storage and are erased at logout.
- Audit Trail All timecard attestations and compliance records are securely stored.
⚙️ Permissions & User Controls
Based on our Privacy Policy, the app requires the following permissions:
Location Access
- Required Setting: "While Using the App" (Foreground).
- When Used:
- At the moment of punch in/out (snapshot)
- When the employee taps to respond to a random location check-in prompt (foreground)
- "Always Allow" / Background Location: NOT Required and NOT Used. Clock-Me does not track your location when the app is closed.
Other Permissions
- Notifications: Optional (used for shift reminders, break notifications).
- Camera/Photos: Not Collected. We do not store or process employee photos or facial recognition data.
🏛 California-Specific Features
For employees at California locations, the app includes additional features to comply with California Labor Code:
- Meal Break Button: Record 30-minute unpaid meal breaks (no location validation required)
- Rest Break Button: Record 10-minute paid rest breaks
- Meal Break Waiver: Digital waiver form for shifts ≤6 hours
- Daily Overtime Display: Shows regular, 1.5x, and 2x overtime hours
- Compliance Alerts: Notifications for upcoming required breaks
- Penalty Tracking: Automatic calculation of meal/rest break violation penalties
📁 Retention & Deletion
- Time and Payroll Records (time records, timecard attestations, meal break waivers, meal/rest break records, compliance violation records): kept as long as required by federal and state wage-and-hour and recordkeeping laws, such as the FLSA (U.S. Department of Labor) and state labor laws
- GPS Heartbeat Data and Device Fraud IDs: short term, only as long as needed for attendance verification and fraud detection
- Details for each type of data are in section 4 of our Privacy Policy.
- Deletion: You may request account deletion via your employer, at clock-me.com/delete-account.html, or by contacting us at app@clock-me.com.
📋 Timecard Attestation
When submitting your weekly timesheet, you must certify the accuracy of your time records:
"I certify that this timecard is complete and accurate. I confirm that I have recorded all hours worked and that I have not performed any work before my scheduled start time, after clocking out, or while off the clock during meal or rest breaks. I also confirm that all meal periods and rest breaks have been accurately recorded and provided in accordance with company policy and applicable law. I have not worked any unrecorded or 'off-the-clock' time."
This attestation, along with your digital signature and timestamp, is stored for compliance and audit purposes.