Clock-Me Privacy Policy
1. Introduction
Clock-Me ("the System," "we," "our," or "us") is a time tracking and workforce management platform owned and operated by Clock-Me LLC. This Privacy Policy explains how we collect, use, store, and protect information when you use our web application and mobile app.
We are committed to protecting your privacy and ensuring transparency about our data practices. This policy applies to all users of Clock-Me, including employees, supervisors, managers, administrators, and clients.
2. Information We Collect
2.1 Account Information
- User ID / Username: Your unique identifier in the system
- Name: Your full name as provided by your employer
- Role: Your assigned role (Employee, Supervisor, Manager, Administrator, Client)
- Address: Physical address (for company billing or location assignment)
- Contact Information: Email address (if provided for notifications)
2.2 Time and Attendance Data
- Punch Records: Date, time, and type (in/out) of each punch
- Work Hours: Calculated hours worked, including regular, overtime (1.5x), and double-overtime (2x) hours
- Meal Break Records: Start time, end time, and duration of meal breaks
- Rest Break Records: Start time, end time, and duration of rest breaks (California locations)
- Lunch Deductions: Applied lunch break deductions (automatic or actual)
- Location Data: The work location associated with each punch
2.3 Location Data
We collect location data in the following scenarios:
GPS Snapshot (Punch In/Out)
- GPS Coordinates: Latitude and longitude at the moment of the punch
- GPS Accuracy: The accuracy level of your device's GPS reading
- Mock Location Detection: Whether your device is using simulated/fake GPS (Android only)
- Approximate Street Address: After a punch, the punch coordinates are converted into an approximate street address (reverse geocoding) so the record is easier to read
- Refused Punch Attempts: If our server refuses a punch (for example, outside the work area, GPS too weak, or simulated GPS detected), the coordinates, accuracy and reason of that attempt are recorded for your employer's review. If the app itself stops a punch when you tap the punch button, only the reason, your distance from the work location and the GPS accuracy are recorded (no coordinates)
- Punch Requests: If your GPS signal is too weak to confirm you are at the work location, you can choose to send the punch to your manager for approval. The request includes the punch coordinates, GPS accuracy, distance from the work location and an optional note you write, and is visible to your employer's administrators and the managers of that location
- GPS Fix Time: The time your phone took the GPS reading used for a punch, so outdated readings can be flagged for review
- App & Device Integrity: When you punch, the app asks Google Play Integrity (Android) or Apple App Attest (iOS) to confirm it is the genuine Clock-Me app on a device that has not been modified. We receive and store the result (for example "passed" or "failed" and the reason), not your device's contents
Who sees it: Punch locations (as coordinates, an approximate address, and a point on a map with its GPS accuracy range) are visible only to your employer's authorized administrators and managers for the locations they manage. GPS readings are estimates and are presented as such; this is a record of punch moments, not live tracking.
Shift Location Verification — only if enabled for your account
- Who: Applies only to employees whose employer has enabled shift location verification for their profile
- Random Check-Ins: While you are punched in, the app may occasionally send you a push notification asking you to tap and confirm your location. Location is captured only when you tap to respond — not continuously in the background
- No Background Tracking: We do not track your location silently between punches. Your position is only recorded at (1) punch-in, (2) punch-out, and (3) when you respond to a check-in prompt
- Never Off the Clock: Location is never collected when you are not punched in
- Missed Check-Ins: If you don't respond to a check-in within 5 minutes, your manager is notified. If you still haven't responded by 10 minutes, your shift is automatically closed at that time. Contact your manager if you believe this was a mistake
- Battery: This model uses negligible battery because we do not run background location services
- Purpose: Fair attendance verification without invasive continuous tracking
Purpose: Location data is used solely to verify that punches occur within the designated work area (geofence validation) and to ensure ongoing compliance with attendance policies. This helps ensure accurate time tracking and prevents time fraud.
Note: Meal breaks and rest breaks do NOT require location validation. Employees may take breaks anywhere.
2.4 California Compliance Data
California Employees: For employees working at California locations, we collect additional data to comply with California Labor Code requirements.
- Meal Break Tracking: Actual meal break start and end times to ensure 30-minute minimum compliance
- Rest Break Tracking: 10-minute paid rest break records for every 4 hours worked
- Meal Break Waivers: Digital waivers for shifts of 6 hours or less, including employee signature, date, and acknowledgment text
- Daily Overtime: Hours tracked for daily overtime (>8 hours) and double-time (>12 hours) calculations
- 7th Consecutive Day: Tracking of consecutive workdays for 7th-day overtime rules
- Split Shift Detection: Records of shifts with unpaid gaps exceeding 1 hour
- Compliance Violations: Records of meal break, rest break, and overtime violations for penalty calculations
2.5 Timecard Attestation Data
When you submit or approve your weekly timecard, we collect:
- Attestation Acceptance: Your acknowledgment of the timecard accuracy statement
- Attestation Text: The exact certification text you agreed to at the time of signing
- Signature Data: Digital signature (drawn or typed)
- Timestamp: Date and time of attestation
- Submission Source: Whether submitted via web or mobile app
Attestation Statement: "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."
Missed-Lunch Attestation (automatic lunch deduction, outside California)
If your employer deducts a lunch break automatically and you did not take it, you can ask for that deduction to be removed for a shift in the current or previous payroll week. When you do, we collect:
- Reason: The reason you selected (your own choice, work needs, or other) and an optional note
- Attestation Text and Version: The exact statement you confirmed, so it can be shown later as you saw it
- Signature: Your typed full name, the date and time, and whether it was sent from the web or the mobile app
- Technical Data: Your IP address and browser or app identification at the time of signing
- Decision: Whether your manager approved or denied the request, who decided, when, and the reason given
Your employer's administrators and the managers of your location can see the request. If it is approved, the deduction is removed and your hours for that shift are recalculated; a timecard you had already signed for that week is reopened so you can sign it again.
2.6 Device Information
For Web Browsers:
- Browser ID: A randomly generated unique identifier stored in your browser's local storage
- Screen Resolution: Your device's screen dimensions
- Timezone: Your device's timezone setting
- Platform: Your operating system (e.g., Windows, macOS, Linux)
For Mobile App:
- Push Token: A unique token for sending push notifications (Expo Push)
- Device ID: Your device's unique identifier
- Device Type: iPhone, Android, etc.
- App Version: The version of the Clock-Me app installed
Important: We do NOT collect:
- Browser history or browsing activity
- Personal files or photos
- Contacts or messages
- Biometric data (fingerprints, face recognition). Face ID / fingerprint sign-in is checked by your phone and never sent to us. If you turn it on, your sign-in details are kept encrypted in your phone's secure storage and erased when you log out.
- Financial information
- Social media accounts
- Background location when app is closed
2.7 Technical Data
- IP Address: Your device's IP address at time of access
- User Agent: Browser/app identification string
- Timestamps: When actions are performed in the system
- Error Logs: Technical error information for debugging (via Sentry.io)
2.8 Support and Records Requests
When you send a request on our support page (no login needed, so former employees can use it too), or ask for older time records in the app, we collect:
- Contact Details: Your name, email address and phone number
- Account Details: The company code and user ID you enter, used to find your employer and check that the request matches an employee
- Request: The topic, the dates it is about, and your message
- Security Data: Your IP address and the date and time of the request, used to limit abuse (requests per hour, temporary blocking of addresses that keep sending) and kept as a record of when the request was made
- Bot Check: The support page uses Cloudflare Turnstile to tell people from automated bots
Where it goes: Requests for your employer (records, account access, hours or pay) are sent to the administrators of the company that matches the company code. Requests for Clock-Me (app problems, billing, privacy) go to the Clock-Me team. If the company code doesn't match any company, the request goes to the Clock-Me team. If you ask for a copy of your time records and your employer approves it, the records are emailed to the email address you entered (or, for requests made in the app, the email on your profile).
3. How We Use Your Information
3.1 Primary Purposes
| Data Type |
Purpose |
| Account Information |
User authentication and access control |
| Time Records |
Calculating work hours and payroll |
| GPS Location (Punch) |
Verifying punch location within work geofence |
| GPS Location (Heartbeat) |
Verifying continued presence during shift (foreground only) |
| Meal/Rest Break Data |
California labor law compliance, penalty calculations |
| Timecard Attestation |
Legal compliance, payroll accuracy, audit trail |
| Device Information |
Fraud prevention (device sharing detection) |
| Push Token |
Sending work-related notifications |
3.2 California Labor Law Compliance
For employees at California locations, we use collected data to:
- Calculate daily overtime (1.5x after 8 hours, 2x after 12 hours)
- Calculate 7th consecutive day overtime
- Track meal break compliance and identify violations
- Track rest break compliance and identify violations
- Calculate meal break and rest break penalty hours
- Detect split shifts and calculate premium pay
- Generate compliance reports for employers
- Store meal break waivers for audit purposes
3.3 Fraud Prevention (Device Sharing Detection)
To maintain time tracking integrity and prevent "buddy punching" (one employee punching for another), we monitor for device sharing patterns.
How It Works:
- When you punch, your device identifier is recorded.
- The system checks if the same device was used by a different employee.
- A potential violation is flagged ONLY if ALL conditions are met:
- Same device identifier (Browser ID, Push Token, or Device ID)
- Same work location
- Within a 2-hour time window
- Different user account
4. Data Retention
We keep each type of data only as long as the law requires or allows for its purpose. How long time and payroll records must be kept is set by wage-and-hour and recordkeeping laws, such as the Fair Labor Standards Act (FLSA) enforced by the U.S. Department of Labor, state labor departments and state wage laws, and tax rules. These periods vary by state, so we keep these records for at least the longest period that may apply to your employer. Records may be kept longer while needed for a legal claim, an audit or a legal hold. When data is no longer needed, it is deleted or anonymized.
| Data Type |
How Long We Keep It |
Time and payroll records (time entries, punch records and their GPS coordinates, timecard attestations, meal break waivers, meal/rest break records, compliance violation records, records requests) |
As long as required by federal and state wage-and-hour and recordkeeping laws (such as the FLSA and state labor laws) |
Audit logs — payroll/legal (time-entry edits, waivers, manager overrides, attestations, meal/rest breaks, weekly approvals, records requests) |
As long as the time and payroll records they relate to |
Audit logs — user management and billing (user activation/deactivation/role change, plan changes, payments) |
As long as required by employment, business and tax recordkeeping laws |
Audit logs — security (login, password change, account lock, force logout) |
As long as needed to protect accounts and investigate security incidents |
Audit logs — operational (view events, notifications sent, push logs, test events) |
Short term, only as long as needed to run and troubleshoot the service |
| Device identifiers and GPS heartbeat data |
Short term, only as long as needed for fraud detection and attendance verification |
| Support requests |
As long as needed to answer the request and keep a record of it |
5. Data Security
We implement industry-standard security measures to protect your information:
Technical Safeguards
- Encryption in Transit: All data transmitted using HTTPS/TLS
- Secure Authentication: JWT-based authentication with secure token handling
- Access Controls: Role-based access limits who can view what data
- Error Monitoring: Sentry.io for secure error tracking and performance monitoring
What We DON'T Do:
- Sell your data to third parties
- Use your data for advertising
- Track your location when app is closed (background)
- Share California compliance data outside of employer reporting
6. Data Sharing
We only share your information in the following circumstances:
6.1 With Your Employer
Your employer (the organization using Clock-Me) has access to:
- Your time and attendance records
- Punch locations and timestamps
- Meal break and rest break records
- Timecard attestations and signatures
- Compliance violation reports
- Meal break waivers
- Support and records requests you send to them, including the contact details you enter
6.2 Service Providers
We use the following third-party services:
| Service |
Purpose |
Data Shared |
| Google Places API |
Address Autocomplete |
Inputted address text |
| Expo Push Notifications |
Mobile notifications |
Push tokens only |
| LocationIQ |
Reverse geocoding (approximate street address of punch locations) |
GPS coordinates |
| Google Maps Platform (Maps JavaScript API) |
Displaying work locations and punch points on maps for authorized administrators and managers |
Map area being viewed (requests come from the administrator's or manager's browser); no names or employee records are sent |
| Google Play Integrity API (Android) |
Confirming punches come from the genuine Clock-Me app on an unmodified device |
App and device integrity signals collected by Google Play services; a one-way hash of the punch request (no readable coordinates or names) |
| Apple App Attest (iOS) |
Confirming punches come from the genuine Clock-Me app on a genuine Apple device |
A device key generated on your iPhone and Apple's attestation of it; no personal data |
| Brevo |
Email notifications |
Email addresses |
| Sentry.io |
Error monitoring |
Error logs, device info (no personal data) |
| MongoDB Atlas |
Primary database hosting |
All application data (encrypted at rest) |
| Redis |
Caching & session management |
Session tokens, temporary cached data |
| Cloudflare |
CDN, DNS & network security; Turnstile bot check on the support page |
IP address, traffic metadata, browser signals used for the bot check |
| Stripe |
Subscription billing & payment processing |
Billing name, email, and payment details (handled directly by Stripe; we do not store full card numbers) |
| Expo EAS |
Mobile app builds & over-the-air updates |
Device/app version info |
| Railway |
Backend/API application hosting |
All application data (hosting provider) |
| Vercel |
Frontend web application hosting |
All application data (hosting provider) |
| PostHog |
Product usage analytics |
App usage events, device/browser type, 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) |
6.3 AI-Assisted Development & Security Tools
We use Anthropic Claude internally as a software development and code-security tool — for code review, static analysis, and regular security audits of our codebase. These tools operate on our source code and infrastructure configuration; they are not integrated into the live product and do not have access to production user or employee data.
6.4 App Distribution Platforms
The Clock-Me app is distributed through the Apple App Store (Apple Developer Program) and Google Play (Google Play Console). These platforms may independently collect device, install, and crash data under their own privacy policies when you download or update the app. We do not share your workforce data (punches, locations, timesheets) with Apple or Google — their role is limited to app distribution.
7. Your Rights
Depending on your jurisdiction, you may have rights regarding access, correction, and deletion of your data.
Copies of your time records: Employees see their last 4 weeks of hours in the app. For older records, use "Need older records?" in the app, or the support page if you no longer work for the company. Your employer is notified and the date of your request is recorded. Your employer, not Clock-Me, decides on and answers these requests.
California Residents
Under the California Consumer Privacy Act (CCPA), you have the right to:
- Know what personal information is collected
- Request deletion of your personal information
- Opt-out of the sale of personal information (we do not sell data)
- Non-discrimination for exercising your rights
To exercise these rights, please contact your employer's HR department or email us at app@clock-me.com.
8. Cookies, Local Storage, and Analytics
We use local storage for device identification (fraud prevention) and session management. We do not use third-party advertising cookies.
8.1 Google Analytics
Our public web pages (marketing site and login page) use Google Analytics, a web analytics service provided by Google LLC, to help us understand how visitors use our site (pages visited, approximate location at city level, device and browser type, and referral source). Google Analytics uses cookies and similar technologies for this purpose. IP addresses are anonymized before storage.
What we do NOT track: Google Analytics is not used inside the authenticated Clock-Me application. Your time and attendance records, punch locations, and other workforce data are never shared with Google Analytics.
Information generated by these cookies about your use of our public pages is transmitted to and stored by Google. Learn more in the Google Privacy Policy. You can opt out of Google Analytics by installing the Google Analytics Opt-out Browser Add-on or by using your browser's cookie controls.
8.2 PostHog
We use PostHog, a product analytics platform, to understand how users interact with Clock-Me (features used, general usage patterns, device/browser type) so we can improve the product. In the mobile app, PostHog also records app screens so we can see and fix problems. Typed text (including passwords) and images (including signatures) are masked, but names, hours and work locations shown on screen can appear in a recording. We do not send your time and attendance records, GPS coordinates, or other workforce data to PostHog as data.
9. Mobile App Permissions
The Clock-Me mobile app requests the following permissions:
| Permission |
Purpose |
Required? |
| Location (GPS) - Foreground |
Geofence validation during punch; heartbeat while punched in |
Yes (While Using App) |
| Push Notifications |
Receiving work reminders, break notifications |
Optional |
| Camera |
Future feature (not currently used) |
No |
"Always Allow" Location: NOT required. We do not track location when the app is closed or in the background.
10. Children's Privacy
Clock-Me is a workplace application and is not intended for use by individuals under 16 years of age.
11. Changes to This Policy
We may update this Privacy Policy from time to time. Significant changes will be communicated through the app or via email. Continued use of Clock-Me after changes constitutes acceptance of the updated policy.
12. Legal Terms, Liability, and Indemnification
Your use of Clock-Me is also subject to our Terms of Use, which include important legal provisions covering:
- Limitation of Liability — In no event shall Clock-Me be held liable for damages exceeding the amount paid to Clock-Me in the twelve (12) months preceding the claim. (See Terms of Use, Section 10.)
- Governing Law & Venue — This agreement is governed by the laws of the State of New Jersey, and any dispute shall be resolved exclusively in the state or federal courts located in Middlesex County, New Jersey. (See Terms of Use, Section 11.)
- Indemnification — Users agree to indemnify and hold Clock-Me harmless against any claims that arise from the use of this platform or from their business operations. (See Terms of Use, Section 12.)
Please review the full Terms of Use for the complete legal language.
13. Contact Us
If you have questions about this Privacy Policy, please contact us at:
Email: app@clock-me.com