Cookie policy.

1. Cookies and similar storage

Cookies are small values a browser stores and sends with applicable requests. Local storage, session storage, and device-secure storage can also remember information. This policy distinguishes the fitr.ca marketing website from Fitr’s app and external services you choose to use.

2. The marketing website

The current website does not set analytics, advertising, or tracking cookies. Fonts and editorial images are served locally, and there are no embedded advertising or social-media tracking scripts. Product-preview choices and animation preferences are held in page memory and reset on reload.

Vercel Web Analytics and Speed Insights provide cookieless website usage and performance measurements. Selected button clicks and successful waitlist submissions include only fixed source labels. Reported page URLs omit query strings and fragments; unsubscribe, API, and unknown pages are excluded. These measurements do not include submitted email addresses or form contents.

The early-access form sends your submitted information to Fitr’s signup endpoint. It does not require a tracking cookie or create an app account. A shared database abuse limit uses a keyed hash of the network address for ten-minute windows and does not set a browser identifier. Expired entries are removed on subsequent signup activity or scheduled cleanup. Hosting and security logs may process request information.

There are currently no optional marketing-site cookies requiring an acceptance banner. If optional tracking technology is introduced, this policy and the relevant controls must be updated, with consent obtained before that technology runs where required.

3. The app and web-app experience

The separate app uses secure or platform-specific storage for authentication tokens, Clerk session data where enabled, preferences, cached feature data, and drafts. It saves the device’s analytics-consent choice and, if enabled, the leave-home reminder’s home point and geofence information. Configured notification, crash-reporting, and product-analytics SDKs can also use registration, installation, or session identifiers. The mechanism and persistence depend on the platform, app version, and enabled integrations.

First-party app engagement and affiliate attribution are described in the Privacy Policy. The app’s usage-analytics choice controls its engagement recording and configured PostHog collection. Sentry crash reporting is separate from that choice. These are app integrations, not marketing-site scripts. Clearing authentication storage can sign you out; clearing local data does not delete your account or server-side content.

4. Email links and external services

Waitlist emails contain signed unsubscribe links identifying the subscription to stop. These are not browser cookies. The website integration does not itself add email-open pixels. Resend can separately apply domain-level open or click tracking settings; those settings affect message processing and must be reflected in the published privacy notice.

App stores, retailers, payment services, sign-in providers, and sharing destinations may use their own cookies or storage when visited. Their policies and controls apply. A link to an external service does not embed that service’s tracking code in this website.

5. Your controls

Browser and device settings let you inspect and clear stored data and manage permissions. Blocking storage may affect sign-in, saved preferences, or external checkout. Use an email’s unsubscribe link to change waitlist preferences; clearing cookies does not unsubscribe an email address.

This marketing website does not conduct cross-site advertising tracking. It does not run advertising scripts that need to be disabled in response to Do Not Track or Global Privacy Control signals. This does not limit any rights concerning other Fitr processing.

• Email preferences
• Privacy Policy

6. Changes and questions

Fitr will update this policy when storage or tracking practices change. Contact legal@fitr.ca with questions or privacy requests. Read this policy together with the Privacy Policy.