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, macOS, 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 (iOS, macOS, Android, and web) 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 the device filesystem for any telemetry purpose, and do not read anything stored on the device. The native SDKs use only runtime properties the operating system exposes to every app (OS version, device class, locale and language) and constants compiled into the app itself (its version and build number from its own Info.plist or manifest, and whether it is a debug build). The web SDK touches no device storage of any kind.
All telemetry aggregation occurs in volatile memory. On web, aggregated data is lost when the page is closed. On iOS, macOS, and Android, aggregated data is lost when the app is terminated.
The SDKs collect only the coarse, non-identifying context listed in Section 3.1 of our Privacy Policy: platform (iOS, macOS, Android, or web), OS version, device class (phone, tablet, or desktop), a country code and a language code from the device's locale setting, browser and OS family (web), the developer-provided app version and build number, and the environment (sandbox or production).
No cookie consent banner is required for SDK operation.
2. Dashboard: No Cookies, Browser Storage for Sign-In and Settings
The Trackless Dashboard sets no cookies. It uses your browser's localStorage and sessionStorage to keep you signed in and to remember settings you choose. Some of these entries relate to you, so we list them all:
| Entry | Purpose | Contains | Duration |
|---|---|---|---|
| Sign-in tokens (Amazon Cognito) | Authenticate you and keep you signed in | Your account ID and email address | Access token 1 hour; refresh token 30 days; removed on sign-out |
| Passkey sign-in memory | Go straight to the passkey prompt for addresses that have used a passkey here | Email addresses that signed in with a passkey in this browser | Until you switch that address to password sign-in, delete your last passkey, or clear site data |
| Onboarding progress | Remember getting-started checklist and setup-wizard progress | Completion flags, stored under your account ID | Until you clear site data |
| Display preferences | Remember the sidebar state, date range, and dismissed banners | Setting values only | Until you clear site data |
| Pending-invitations flag (session storage) | Show pending team invitations once per browser session | A flag stored under your account ID | Until the tab closes |
| Update-reload marker (session storage) | After a Trackless update, reload an open dashboard tab once without reloading in a loop | The time of that reload only | Until the tab closes |
This storage is not used for:
- Analytics or usage tracking
- Advertising, retargeting, or behavioral profiling
- Cross-site tracking
- Sharing data with third parties
It contains no telemetry data and never leaves your browser, except the sign-in tokens, which are sent to our API to authenticate your requests.
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).
The SDKs store nothing on your device and read nothing stored there: no cookies, no local storage, no file metadata, and no record of when or how the app was installed. Beyond the runtime properties above, the native SDKs use only constants compiled into the app itself: its version and build number from its own Info.plist (Apple platforms) or manifest (Android), and whether it is a debug build. The web SDK reads nothing stored on the device. When the developer does not set an environment, it compares the page's own hostname, taken from the page's URL, not from device storage, in memory: localhost, a *.localhost name, a 127.x.x.x address, [::1] or 0.0.0.0 marks the page as sandbox, and any other hostname as production. Only sandbox or production is sent; the hostname itself is not. No SDK sends a distribution channel. Nothing is written on any platform — all buffering is in volatile memory, and unsent data is lost when the app closes.
Conclusion: Article 5(3) consent requirements do not apply to Trackless SDK telemetry. The SDKs store nothing on terminal equipment and read nothing stored there.
4.2 Dashboard Storage -- Strictly Necessary Exemption
The dashboard's browser storage falls within the strictly necessary exemption of Article 5(3). You explicitly request access to the dashboard. The sign-in tokens are the minimum technical mechanism required to keep you authenticated, and the remaining entries only remember choices and progress you make while using the dashboard.
4.3 Combined Assessment
| Component | Cookies Used | ePrivacy Article 5(3) | Consent Required |
|---|---|---|---|
| SDKs (web, iOS, macOS, Android) | None | Not applicable | No |
| Dashboard | None (browser local storage and session storage, see Section 2) | 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 LLC
PO Box 7238, Ann Arbor, MI 48107
Email: privacy@tracklesstelemetry.com