Cookie policy

Your choices

Use Cookie preferences on any page to allow or reject optional analytics, customize your choice, or withdraw a previous choice. Analytics start off until you allow them. Withdrawing stops future optional tracking; it does not undo information already sent. Essential sign-in and service functions remain available when you reject analytics.

Your choice is stored in this browser on this website. Another browser, device, or website host may need a separate choice. If saving your choice fails, optional analytics stay off in the current tab; an earlier saved choice may return on your next visit. The preference controls explain the error. Clearing site data removes saved preferences and can sign you out.

Cookies and storage used by service features

Not every entry is present for every visitor. Some are created only during sign-in or an onboarding workflow. Local storage persists until the application or you remove it; session storage is scoped to the browser tab's session. These storage types are distinct from cookies.

Supabase authentication cookies

Support sign-in, session refresh, and account verification when authentication is configured. Names and expiry depend on the configured Supabase project and authentication library; cookies may be split into multiple entries. They are not optional marketing analytics.

pipeline.auth.last-activity (local storage)

Records activity for the idle sign-out check. It is cleared when the application clears the session activity record.

onboarding_workspace_id and onboarding_token (local storage)

Support the onboarding workspace test flow. They remain until cleared by the application or browser site-data controls. Treat the token as a credential and do not share it.

pipeline_nav_prev and pipeline_nav_curr (session storage)

Support in-app back-navigation fallbacks. Paths can include record identifiers. The application clears this navigation history on sign-out.

mkt-nav-scroll-top (session storage)

Remembers the selected public navigation destination so it opens at the top, then removes the matching entry.

orvexa:cookie-consent:v1 (local storage)

Remembers your optional analytics choice and its preference version. Changing Cookie preferences replaces that choice.

orvexa:debug-api (local storage, only if manually set)

An optional developer diagnostic setting enabling additional API console logging. It is not created by the cookie preference controls and is not a marketing analytics identifier. Remove it through browser site-data controls when no longer needed.

Optional Plausible analytics

The application supports Plausible when a site operator configures it. No Plausible script is loaded. Optional analytics events are sent directly to Plausible only after analytics are allowed. The integration is intended for cookieless measurement of public marketing pages, not signed-in clinic, patient, or report activity. No advertising tracker is added by these controls.

Public page views and limited demo and signup actions help evaluate the website. Inquiry content, patient data, and account credentials must not be used as analytics event properties. The integration sends only the event name, configured website domain, and public page URL without its query or fragment to plausible.io. It omits referrers, event properties, and cookies. As with any direct network request, Plausible receives network information such as the browser IP address and user agent. Custom or self-hosted analytics configurations are disabled pending a separate privacy review. Orvexa AI should verify its deployment settings before publishing a final policy.

Questions

Read the privacy notice or contact Orvexa AI without including patient information or credentials. Browser privacy settings can also block or clear storage, but blocking essential storage may prevent sign-in or disrupt a workflow.