Vertix.

Cookies

Cookie Policy

Last updated: May 1, 2026 · Currently available to licensed clinicians in the United States.

This Cookie Policy explains how Vertix uses cookies and similar tracking technologies on vertix.health.

1. What we use

We use a minimal set of cookies organized in three categories:

  • Strictly necessary: session authentication, CSRF protection, security. Cannot be disabled — the product would not function.
  • Functional: remembered preferences (language, theme, dismissed notifications). Optional.
  • Analytics: aggregated, de-identified usage analytics to improve the product. Optional and opt-in.

2. What we do NOT use

  • No third-party advertising trackers.
  • No data brokering pixels.
  • No social-media sharing trackers.
  • No cross-site behavioral tracking.

3. Detail by cookie

CookiePurposeCategoryDuration
cited_sessionAuthenticationStrictly necessarySession
cited_csrfCSRF protectionStrictly necessarySession
mission_ann_dismissed_v1Remembers dismissed announcementFunctional30 days
cited_themeLight/dark theme preferenceFunctional1 year
_ga (if opted in)Aggregated analyticsAnalytics2 years

4. Managing cookies

You can manage cookies through:

  • Your browser settings (refer to your browser's help for instructions).
  • The cookie preference panel on first visit, or anytime via the "Cookies" link in the footer.

Disabling strictly necessary cookies will prevent the platform from functioning. Disabling functional cookies will reset your preferences. Disabling analytics has no impact on functionality.

5. Do Not Track

Vertix honors the Do Not Track (DNT) browser signal. When DNT is enabled, analytics cookies will not be set regardless of consent state.

6. CCPA notice (California residents)

We do not sell personal information. The "Do Not Sell or Share My Personal Information" right under CCPA is automatically respected because no sale or sharing occurs.

7. Changes

Material changes will be communicated via email or in-product banner.

8. Questions

Email [email protected].

Questions about this document? Reach our compliance team.