Legal · Cookies

Cookie Policy.

Last updated: July 8, 2026 · Read alongside our Privacy Policy · Questions: [email protected]

1. Introduction

This Cookie Policy explains how Xevyo ("Xevyo," "we," "us," or "our") uses cookies and similar technologies (such as local storage, session storage, and pixels) when you visit or use xevyo.com, our chat platform, and our developer API (together, the "Services").

Xevyo is a self-hosted conversational AI platform. Unlike many AI products, our core inference stack runs on our own infrastructure using our own proprietary models — but our web application, account system, and billing still rely on cookies and comparable technologies to function, to remember your preferences, and to keep your account secure.

This policy should be read alongside our Privacy Policy, which explains in more detail how we collect, use, and protect personal data (including any health-related information you choose to share with the assistant).

2. What Are Cookies?

Cookies are small text files placed on your device when you visit a website. They allow a site to recognise your device, remember information about your visit, and enable features such as staying signed in. We also use similar technologies, including:

  • Local storage / session storage — used by the browser to hold data such as draft messages, UI state, or short-lived session tokens without sending it back to the server on every request.
  • Pixels / SDKs — small pieces of code embedded in emails or pages that confirm an email was opened or a page was loaded.
  • Device and session identifiers — used by our authentication and API infrastructure (e.g. secure one-time session-launch tokens, developer API keys) to recognise a signed-in session.

For simplicity, this policy refers to all of these collectively as "cookies."

3. Why We Use Cookies

We use cookies for the following broad purposes:

  • Authentication & security — to keep you signed in, protect against cross-site request forgery, and support Single Sign-On (Google / GitHub OAuth), LDAP, and SCIM-provisioned enterprise logins.
  • Core functionality — to remember chat sessions, threads, folders, and in-progress uploads so the product works as expected across page reloads.
  • Preferences & personalisation — to remember display, language, unit, and tone/response settings, custom instructions, and which optional tools (e.g. Google Calendar, Health Connect) you have enabled.
  • Performance, feedback & analytics — to understand feature usage, aggregate thumbs-up/down feedback, and monitor product performance and reliability.
  • Billing & subscriptions — to support secure checkout, plan entitlements, and fraud prevention through our payment processor, Stripe.
  • Admin & enterprise administration — to support administrator sessions, audit logging, and role-based access for Admin / Reviewer / Trainer / Super-Admin roles.

4. Categories of Cookies We Use

4.1 Strictly Necessary Cookies

These cookies are essential for the Services to operate — for example, keeping you logged in, authenticating API and admin sessions, and protecting your account. They cannot be switched off without breaking core functionality, and under most privacy laws they do not require consent.

Cookie / IdentifierPurposeType & Duration
Session / auth cookieMaintains your authenticated session after you log in with email/password, SSO (Google, GitHub), or enterprise LDAP.1st party — Session
OAuth state / PKCE cookieProtects the SSO login handshake with Google or GitHub from interception or forgery.1st party — Short-lived (minutes)
CSRF tokenPrevents cross-site request forgery on account, billing, and admin actions.1st party — Session
Secure one-time session-launch tokenHands off an authenticated session to an external or embedded app for a limited time.1st party — Single-use / short-lived
SCIM / admin session cookieMaintains authenticated sessions for enterprise administrators managing provisioning and access control.1st party — Session
Load-balancing / routing cookieEnsures requests within a session are routed consistently across our server infrastructure.1st party — Session

4.2 Functional & Preference Cookies

These cookies remember choices you make so the assistant behaves the way you expect — without them, features such as personalisation and memory would reset every visit.

Cookie / IdentifierPurposeType & Duration
UI preference cookie / local storageRemembers display language, units, theme, and layout (e.g. sidebar/folder state).1st party — Persistent (up to 12 months)
Personalisation settingsStores your "custom instructions," tone/verbosity/citation-style settings, and enabled tool preferences (e.g. Calendar, Health Connect, plugins).1st party — Persistent (up to 12 months)
Consent / cookie-banner preferenceRemembers the cookie choices you make on this site so we don't ask again on every visit.1st party — Persistent (up to 12 months)

4.3 Performance, Feedback & Analytics Cookies

These cookies help us understand how the Services are used in aggregate — for example, which features are used most, and how the assistant is rated — so we can improve reliability and quality.

Cookie / IdentifierPurposeType & Duration
Product analytics identifierCorrelates in-app events (e.g. feature usage, tool invocations) to improve product quality; used in aggregate, not to build advertising profiles.1st party — Persistent (up to 12 months)
Feedback / ratings correlationLinks thumbs-up/down ratings and quality scores to the relevant message context for internal evaluation.1st party — Session
Evaluation arena voting cookiePrevents duplicate voting when comparing model responses head-to-head in the internal evaluation arena.1st party — Session

4.4 Billing & Payment Cookies

Subscriptions and plan upgrades are processed by our payment provider, Stripe, which sets its own cookies during checkout for fraud prevention and to keep your payment session secure. Xevyo does not process or store your full card details.

Cookie / IdentifierPurposeType & Duration
__stripe_mid, __stripe_sid, and related Stripe cookiesFraud prevention and session continuity during checkout, set by Stripe on Stripe-hosted checkout pages.3rd party (Stripe) — Session to 12 months

4.5 Third-Party Integration Cookies

If you choose to connect optional integrations, the relevant third party may set its own cookies during the connection (OAuth) flow. These are governed by the third party's own cookie and privacy policies, not this one.

Cookie / IdentifierPurposeType & Duration
Google OAuth / Calendar / Health Connect / Fit / DriveAuthenticates and maintains your consent when you connect Google Calendar, Health Connect, Fit, or Drive as an optional tool or file source.3rd party (Google) — Varies
Microsoft OneDriveAuthenticates and maintains your consent when you import files from OneDrive as an optional file source.3rd party (Microsoft) — Varies
GitHub OAuthAuthenticates SSO login or GitHub-based repository ingestion into a knowledge base.3rd party (GitHub) — Varies

Xevyo's core chat, voice, retrieval, memory, and image-generation features run on our own self-hosted models and do not route conversational content through third-party AI APIs. The cookies above relate to web-application functionality (login, billing, optional integrations) — not to model inference.

5. We Do Not Use Advertising Cookies

Xevyo does not display third-party advertising and does not use cookies to build cross-site advertising profiles or sell personal information to ad networks. Any analytics we use are for the internal product-improvement purposes described above.

6. How Long Cookies Last

  • Session cookies — deleted automatically when you close your browser or log out.
  • Persistent cookies — remain on your device for a set period (noted in the tables above) or until you delete them, so we can remember your preferences on your next visit.

8. Your Rights & Regional Disclosures

Depending on where you are located, you may have specific rights regarding cookies and the personal data associated with them:

  • European Economic Area / UK — under the ePrivacy Directive and UK/EU GDPR, we ask for your consent to non-essential cookies before they are set, and you may withdraw consent at any time. You also have rights of access, correction, portability, and erasure over related personal data.
  • India — under the Digital Personal Data Protection Act, 2023, we process personal data collected via cookies only as necessary and consistent with the notice provided at collection, and we provide region-appropriate consent and grievance-redressal mechanisms.
  • Other jurisdictions — where applicable state or national privacy laws (e.g. relating to the "sale" or "sharing" of personal information) grant additional rights, we honour opt-out requests submitted through the mechanisms in Section 7 or via the contact details in Section 11.

Because Xevyo may process health-related information you share with the assistant, we apply additional safeguards described in our Privacy Policy, including redaction of protected health information from logs where applicable and honouring data export and erasure requests for stored memory.

9. Children's Privacy

The Services are not directed to children under the age required by applicable law to consent to data processing on their own behalf, and we do not knowingly set non-essential cookies for such users.

11. Contact Us

Questions about this Cookie Policy, or wish to exercise your rights? Email [email protected], or write to Xevyo Technologies Inc., 330 5 Ave SE #1010, Calgary, Alberta, Canada. Data Protection Officer / Grievance Officer: Viswateja Yetukuri.