Coram Cookies and Browser Storage
Version: October 14, 2026. Effective only when published by Coram.
Coram uses cookies and browser storage for staff authentication, workspace recovery and campaign attribution. Meta Pixel is currently paused. These technologies have different purposes and privacy effects.
| Technology | Purpose and information | Current duration / controls |
|---|---|---|
| Supabase authentication cookies | Carry/refresh staff authentication sessions | Duration depends on the authentication configuration, session and refresh behavior. Blocking may prevent sign-in. Signing out and clearing site data can affect sessions |
| Workspace localStorage | Recovery copy of substantial workspace information, potentially including athlete names/DOB/measurements, observations, sources, metrics, favorites and settings | No current time-based expiry in application code; not separately encrypted by Coram. Signing out alone does not clear all recovery copies. Recognized deletion can clear current-browser data; offline/dormant copies may persist until app/browser clearing |
| Campaign sessionStorage | Limited allowlisted UTM/campaign attribution for public-site marketing | Browser session storage; actual lifetime depends on browser session/restore behavior, rather than a fixed guaranteed hour count |
| Marketing preference localStorage | Remembers your accepted or rejected marketing preference; separate from the athlete workspace copy | No fixed expiry in the current preference code; remains until changed or cleared by you or the browser. A browser opt-out signal keeps optional tracking off even if an earlier preference allowed it |
| Meta Pixel and associated cookies/requests — currently paused | Previously measured public marketing page views, video engagement and CTA activity, plus information Meta independently collected such as device/browser/network/site activity | Newly loaded current pages do not initialize Pixel; previously open pages may retain older code until closed or reloaded. Previously set cookies and information Meta received may remain; duration depends on browser and Meta settings |
Coram's own Pixel event payloads used marketing metadata without intentionally attaching athlete records, raw performance measurements or authenticated user IDs. Meta could independently collect information through its technology. Review Meta's Privacy Policy for its practices and choices. Pausing Pixel does not delete previously received information or cookies already on your device.
Browser controls can limit cookies and clear site/local/session data. These controls may affect authentication and recovery, and may not implement all legally required advertising choices. Protect devices used for athlete records and avoid shared/unmanaged browsers where access cannot be controlled.
The public marketing pages offer a Privacy choices control with equally available Accept marketing and Reject marketing choices. Optional Meta tracking stays off unless you affirmatively accept and stays off when your browser sends a Global Privacy Control or Do Not Track signal. Browsing or closing the choice does not count as acceptance. With Pixel paused, accepting marketing does not activate Meta tracking. Reopen Privacy choices to change or withdraw your preference. Withdrawal stops future optional collection when available; it does not erase information already received by Meta. A choice applies to that browser and site; clearing its storage or using another browser may require a new choice. Contact us about other applicable privacy choices.
Questions and applicable privacy requests: coramperformance@gmail.com. See our Privacy Policy.