Cookie Policy
Effective Date · February 24, 2026
IRONCLOCK
Cookie Policy
Effective Date: February 24, 2026
This Cookie Policy explains how IronClock ("Company", "we", "us", or "our") uses cookies and similar technologies when you access or use the IronClock platform, including the web application, mobile application, and all related services (collectively, the "Service").
This Cookie Policy is part of and supplements our Privacy Policy and Terms of Service. Capitalized terms not defined in this Cookie Policy have the meanings given to them in the Privacy Policy or Terms of Service.
1. WHAT ARE COOKIES AND SIMILAR TECHNOLOGIES?
Cookies are small text files placed on your device by a website or application. They are widely used to make websites function properly, improve performance, and provide information to the site operators.
Similar technologies include:
- Local storage: Data stored in your browser that persists between sessions
- Secure device storage: Encrypted storage on mobile devices used to securely store authentication credentials and application preferences
- Software development kits (SDKs): Code libraries embedded in mobile applications that may collect usage data or enable specific functionality
2. COOKIES WE USE
2.1 Essential Cookies
The web application uses one essential first-party cookie:
| Cookie | Purpose | Type | Duration | Attributes |
|---|---|---|---|---|
| Session cookie | Maintains your authenticated session after login. Contains an encrypted session token that identifies your Account. | First-party, HTTP-only | 14 days | HTTP-only (not accessible via JavaScript); Secure (transmitted over HTTPS only); SameSite: Lax (provides CSRF protection) |
This cookie is strictly necessary for the web application to function. Without it, you cannot log in or use authenticated features. It is set when you log in and cleared when you log out.
We do not use any advertising, marketing, or third-party tracking cookies.
2.2 Non-Essential Cookies
The web application does not currently set any non-essential cookies. Where optional web analytics are enabled, the analytics provider may set additional cookies as described in Section 5.1. If we introduce other non-essential cookies in the future, we will update this Cookie Policy and implement appropriate consent mechanisms before setting them.
3. LOCAL BROWSER STORAGE
The web application uses browser local storage for the following purposes:
| Storage Key | Purpose | Type | Duration |
|---|---|---|---|
| User information cache | Stores a cached copy of your Account information (name, email, role) to improve page load performance and reduce server requests | Local storage | Cleared on logout or when browser storage is cleared |
| Theme preference | Stores your selected display theme (light or dark mode) | Local storage | Persists until you change it or clear browser storage |
Local storage data is accessible only within your browser and is not transmitted to third-party services.
4. MOBILE DEVICE STORAGE
The mobile application uses platform-native secure storage to store authentication credentials and application preferences:
| Data | Purpose | Storage Method | Duration |
|---|---|---|---|
| Authentication tokens | Maintains your authenticated session within the mobile application | Encrypted device storage (platform keychain or keystore) | Access tokens expire after a short period; refresh tokens expire after 30 days or upon logout |
| User and organization data | Caches Account information and selected organization for offline access | Encrypted device storage | Cleared on logout |
| Notification preferences | Stores dismissed notification identifiers to prevent re-displaying acknowledged alerts | Encrypted device storage | Cleared on logout |
Mobile secure storage is protected by your device's native encryption and security mechanisms. Data stored in platform keychains or keystores is encrypted at rest and accessible only to the IronClock application.
5. ANALYTICS AND PERFORMANCE TECHNOLOGIES
5.1 Web Analytics (Optional)
The web application may use a third-party analytics service to collect anonymized usage data, including page views, navigation patterns, and feature interactions. Web analytics are loaded only if configured by the Company and are not enabled by default.
Where web analytics are active, the legal basis for this processing is your consent (where required by applicable law) or our legitimate interest in understanding how users interact with the Service. For users in jurisdictions requiring prior consent for non-essential cookies or tracking, web analytics will not be activated without your consent.
Web analytics services may set their own cookies or use similar tracking mechanisms. If web analytics are enabled, we will maintain a supplementary list of analytics cookies (including their names, purposes, and durations) accessible from this Cookie Policy or through an in-application cookie preference center. Where web analytics are active, the data collected is used solely to understand how users interact with the Service and to improve its functionality and design.
5.2 Mobile Analytics (Optional)
The mobile application may use a third-party analytics SDK to collect event-level usage data, including:
- Authentication events (login, logout)
- Clock actions (clock-in, clock-out)
- Feature interactions (screen views, notifications, NFC scans)
- Network connectivity events
Analytics events may be associated with a pseudonymous user identifier to provide aggregated usage insights. Mobile analytics are used solely to improve the Service and diagnose issues.
Where required by applicable law, the mobile application will not initialize analytics collection until the user has provided consent. Users may withdraw consent at any time through the application's privacy settings. If consent is not given or is withdrawn, the mobile application will function normally without analytics collection.
5.3 Error Tracking and Performance Monitoring (Optional)
The web application, mobile application, and backend may use third-party error tracking and performance monitoring services to identify software defects, monitor application performance, and improve reliability. These services collect:
- Error reports and stack traces
- Performance metrics (page load times, API response times)
- A pseudonymous user identifier for correlating issues
These services are configured to minimize the collection of personally identifiable information. Sensitive data — including authentication tokens, passwords, and API keys — is automatically redacted before transmission to error tracking providers.
Backend infrastructure may also use application performance monitoring tools to track server health, transaction performance, and resource utilization. These tools do not collect end-user personal information beyond anonymized request metadata.
6. PUSH NOTIFICATION TOKENS
The mobile application requests permission to send push notifications. If you grant permission, a device-specific push notification token is generated by your device's operating system and registered with our servers. This token is used solely to deliver notifications to your device.
Push notification tokens are:
- Stored on our servers and associated with your Account
- Automatically deactivated after 90 days of inactivity
- Removed from our servers when you log out of the mobile application
You may disable push notifications at any time through your device's notification settings.
7. TECHNOLOGIES WE DO NOT USE
For transparency, the Service does not use the following technologies:
- Third-party advertising or marketing cookies
- Cross-site tracking cookies or pixels
- Retargeting or remarketing technologies
- Browser fingerprinting for identification purposes
- Social media tracking widgets or plug-ins
8. DO NOT TRACK SIGNALS
Some web browsers transmit "Do Not Track" (DNT) signals. Because there is no common industry standard for interpreting DNT signals, the Service does not currently respond to DNT signals. We will update this Cookie Policy if a uniform standard is adopted.
9. YOUR CHOICES AND CONTROLS
9.1 Essential Cookies
The session cookie is strictly necessary for the web application to function. If you block or delete this cookie through your browser settings, you will not be able to log in or use the web application. No consent is required for essential cookies under applicable privacy laws.
9.2 Browser Storage
You may clear local storage data at any time through your browser's settings (typically under "Site Data" or "Storage"). Clearing local storage will remove your cached user information and theme preference but will not affect your Account or data stored on our servers.
9.3 Mobile Device Storage
You may clear mobile application storage by logging out of the application or by uninstalling and reinstalling the application. On iOS, data stored in the Keychain may persist after uninstallation unless manually cleared through device settings.
9.4 Analytics Opt-Out
Where analytics technologies are active:
- Web: You may use browser extensions or privacy settings to block analytics scripts. You may also enable your browser's built-in tracking protection features.
- Mobile: You may limit analytics collection through your device's privacy settings. On iOS, you can manage tracking permissions through Settings > Privacy & Security > Tracking. On Android, you can opt out of personalized ads through Settings > Privacy > Ads. Additionally, you may disable analytics within the IronClock mobile application's privacy settings, where available.
9.5 Push Notifications
You may disable push notifications at any time:
- iOS: Settings > Notifications > IronClock > toggle off Allow Notifications
- Android: Settings > Apps > IronClock > Notifications > toggle off
Disabling push notifications does not affect the core functionality of the Service but may result in delayed awareness of clock event reminders, schedule changes, or administrative notifications.
10. COOKIE CONSENT FOR EU AND UK USERS
For users located in the European Economic Area (EEA), the United Kingdom, or other jurisdictions that require prior consent for non-essential cookies or tracking technologies:
- Essential cookies: The session cookie is placed under the "strictly necessary" exemption and does not require consent.
- Non-essential technologies: If we introduce non-essential cookies or tracking technologies that require consent under applicable law, we will present a consent mechanism before activating them.
- Withdrawal of consent: Where consent has been given, you may withdraw it at any time through the cookie consent mechanism or by adjusting your browser or device settings.
As the web application currently uses only a single essential session cookie, no cookie consent banner is required for cookie placement. The user information cache stored in local storage is considered strictly necessary for the proper functioning of the web application. The theme preference is a functional storage item that enhances your experience; it does not track your activity or share data with third parties. Where applicable law requires consent for functional storage, we will implement appropriate consent mechanisms.
11. DATA PROTECTION AND THIRD-PARTY SERVICES
Third-party analytics, error tracking, and performance monitoring providers process data in accordance with their own privacy policies and terms of service. We select providers that offer strong privacy protections and contractually require them to process data only for the purposes described in this Cookie Policy and our Privacy Policy.
For more information about how we share data with third-party service providers, see Section 3.2 of our Privacy Policy.
12. CHANGES TO THIS COOKIE POLICY
We may update this Cookie Policy from time to time to reflect changes in our practices, technologies, legal requirements, or for other operational reasons. For material changes, we will provide at least thirty (30) days' prior notice by email to the address associated with your Account or by prominent notice within the Service. For non-material changes, we will update the "Effective Date" at the top of this policy.
We encourage you to review this Cookie Policy periodically to stay informed about our use of cookies and similar technologies.
13. CONTACT INFORMATION
If you have questions about our use of cookies or similar technologies, please contact us at:
IronClock
Email: [email protected]
Website: www.ironclock.app
For data protection inquiries or to exercise your privacy rights, see Section 7 of our Privacy Policy or email: [email protected]
Last Updated: February 24, 2026