Cookie Policy
This Cookie Policy explains how cookies and similar technologies are used across the Trackless platform, which comprises:
- Trackless SDKs -- client libraries integrated into customer applications (web, iOS, Android)
- Trackless Dashboard -- the web application at dashboard.tracklesstelemetry.com
- Trackless Website -- the marketing site at tracklesstelemetry.com
1. SDK Telemetry Cookies: None
The Trackless SDKs (web, iOS, and Android) use zero cookies and zero client-side storage of any kind for telemetry purposes. Specifically, the SDKs:
- Do not set or read HTTP cookies
- Do not use localStorage
- Do not use sessionStorage
- Do not use IndexedDB
- Do not use any other form of persistent or semi-persistent client-side storage
- Do not write to or read from the device filesystem for any telemetry purpose
All telemetry aggregation occurs in volatile memory. On web, aggregated data is lost when the page is closed. On iOS and Android, aggregated data is lost when the app is terminated.
The SDKs collect only the following coarse, non-identifying device properties: platform (iOS, Android, or web), OS major version, device class (phone, tablet, or desktop), and an optional coarse locale code derived from the device's system locale setting.
No cookie consent banner is required for SDK operation.
2. Dashboard Cookies: Essential Authentication Only
The Trackless Dashboard uses cookies solely for authentication and session management. These cookies are set by Amazon Cognito, the identity service that manages dashboard user accounts.
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
| Cognito session tokens | Authenticate the logged-in user and maintain the dashboard session | Essential / strictly necessary | Session duration |
Dashboard cookies are not used for:
- Analytics or usage tracking
- Advertising, retargeting, or behavioral profiling
- Cross-site tracking
- Sharing data with third parties
- Any purpose other than authenticating the dashboard user's session
Dashboard localStorage
In addition to session cookies, the Trackless Dashboard uses browser localStorage for UI preferences essential to dashboard functionality. These values contain no telemetry data, no personal information, and no tracking identifiers. Stored preferences include:
- Sidebar collapsed/expanded state
- Onboarding wizard progress
- Usage banner dismissal state
- Getting-started checklist completion state
This storage is strictly functional and falls within the strictly necessary exemption of ePrivacy Directive Article 5(3).
3. Third-Party Cookies: None
Trackless does not use any third-party cookies across any part of the platform. Specifically:
- No third-party analytics services (e.g., Google Analytics, Hotjar, Mixpanel)
- No advertising networks or tracking pixels
- No social media widgets or embedded content that sets cookies
- No third-party A/B testing or personalization tools
Stripe hosted checkout: When you are redirected to Stripe to complete a purchase or manage your subscription, Stripe may set cookies on its own domain in accordance with Stripe's Cookie Policy. These cookies are set by Stripe, not by Trackless, and are governed by Stripe's privacy practices. Stripe does not receive any telemetry data, app names, event names, or usage details.
4. ePrivacy Directive Article 5(3) Analysis
4.1 SDK Telemetry -- No Storage, No Access to Stored Information
The Trackless SDKs do not store any information on the end user's terminal equipment for telemetry purposes. The device properties collected are inherent characteristics of the operating environment made available through standard platform APIs. They are not "information stored on the terminal equipment" within the meaning of Article 5(3).
Conclusion: Article 5(3) consent requirements do not apply to Trackless SDK telemetry.
4.2 Dashboard Authentication -- Strictly Necessary Exemption
Dashboard session cookies fall within the strictly necessary exemption of Article 5(3). The user has explicitly requested access to the dashboard service, and session cookies are the minimum technical mechanism required to maintain the authenticated state.
4.3 Combined Assessment
| Component | Cookies Used | ePrivacy Article 5(3) | Consent Required |
|---|---|---|---|
| SDKs (web, iOS, Android) | None | Not applicable | No |
| Dashboard | Essential session cookies | Strictly necessary exemption | No |
| Marketing website | None | Not applicable | No |
No cookie consent banner is required on any Trackless platform surface.
5. Do Not Track (DNT) Signals
Trackless does not track users in any capacity. The platform's architecture is designed to make individual user tracking impossible. Because no tracking occurs, the Do Not Track browser signal has no effect on Trackless's behavior -- the outcome is the same regardless of the signal.
6. Changes to This Policy
We may update this Cookie Policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. Changes will be posted on this page with an updated "Last Updated" date.
7. Contact
If you have questions about this Cookie Policy, please contact us at:
Camp Four Software
Email: privacy@tracklesstelemetry.com