Cookie Policy

Last updated: February 26, 2026

How We Use Cookies and Similar Storage

Ryva uses cookies and similar browser storage to keep accounts signed in, secure authentication flows, measure product usage, and improve performance.

Categories We Use

  • Strictly necessary cookies: used by Clerk for sign-in, account session continuity, and security controls.
  • Analytics cookies: used by PostHog for event analytics and user interaction metrics.
  • Performance measurement: Vercel Analytics and Vercel Speed Insights may set identifiers to measure page performance and traffic trends.

Integrations and AI Request Handling

GitHub, Slack, Exa, and Claude requests are processed primarily as server-to-server API calls. Those integrations are generally not driven by browser cookies on your device, but by access tokens and credentials managed in backend systems.

AI requests are routed through Vercel AI Gateway and may be sent to Anthropic Claude. Web-search requests may be sent to Exa when a run requires external retrieval.

Technology-Specific Notes

  • Clerk: manages authentication/session cookies required for protected routes and account access.
  • PostHog: may set browser identifiers (for example keys prefixed with ph_) when analytics is enabled.
  • Vercel Analytics / Speed Insights: collect usage and performance telemetry with lightweight client instrumentation.
  • GitHub and Slack integrations: rely on OAuth and API tokens scoped to connected accounts/workspaces.
  • Claude via Vercel AI Gateway and Exa: process AI and web-search requests via backend API calls.
  • Theme preference: dark/light mode preference is stored via browser storage (localStorage), not a dedicated cookie.

Third-Party Context

Some cookie and telemetry behavior is controlled by third-party providers (Clerk, PostHog, Vercel). Their policies also apply to data they process.

How to Control Cookies

  • Block or delete cookies in your browser settings
  • Clear site data (cookies and local storage) for this domain
  • Use privacy tools/extensions to limit analytics tracking

If you disable necessary cookies, login and protected dashboard features may not work correctly.

Do Not Track

Browser "Do Not Track" behavior is not consistently standardized across vendors. We currently do not implement a separate Do Not Track response mechanism.

Policy Updates

We may update this policy when we change analytics providers, authentication flows, infrastructure, or legal requirements.

Contact

Questions about cookies can be sent to support@ryva.dev.