Cookie Policy

Cookies are small text files stored in your browser by websites you visit. They help websites remember your preferences and maintain your login session. We use cookies sparingly — only what is strictly necessary to operate the Service.

• ·Session cookie (next-auth.session-token): A secure, HTTP-only cookie set by NextAuth when you sign in with GitHub. It contains an encrypted reference to your session. It is deleted when you sign out or when it expires (typically 30 days). This cookie is essential — the Service cannot function without it.
• ·CSRF cookie (next-auth.csrf-token): A security cookie used to prevent cross-site request forgery attacks during authentication. It is essential and set automatically by NextAuth.
• ·Callback URL cookie (next-auth.callback-url): Temporarily set during the OAuth redirect flow to remember where to send you after sign-in. It is deleted immediately after use.

• ·oryve-theme: Stores your selected theme preference ("dark" or "light"). This is a string value, not a cookie, and contains no personal data. It persists in your browser until cleared.
• ·No other data is written to localStorage or sessionStorage.

• ·No advertising cookies or tracking pixels.
• ·No third-party analytics cookies (e.g., Google Analytics).
• ·No social media tracking cookies (e.g., Facebook Pixel).
• ·No fingerprinting or cross-site tracking technologies.
• ·We do not sell cookie data or share it with advertisers.

During the GitHub OAuth sign-in flow, your browser communicates directly with GitHub (github.com). GitHub may set their own cookies on the github.com domain as part of their authentication process. These cookies are governed by GitHub's Privacy Statement, not ours. We have no control over or access to GitHub's cookies.

• ·You can delete cookies at any time via your browser settings. Deleting the session cookie will sign you out of Oryve.
• ·You can block cookies in your browser, but this will prevent you from signing in to Oryve since the session cookie is essential.
• ·To clear the theme preference, open your browser's developer tools, navigate to Application → Local Storage → your Oryve domain, and delete the "oryve-theme" key.
• ·Most browsers offer cookie management under Settings → Privacy → Cookies. Refer to your browser's documentation for specific instructions.

Under GDPR, we rely on the "strictly necessary" legal basis for our session and CSRF cookies — these are required to provide the service you requested and do not require a separate consent. The theme preference stored in localStorage is non-personal and requires no consent. We do not use any cookies that would require an opt-in consent banner under GDPR. If this changes in the future, we will update this policy and implement appropriate consent mechanisms.

We may update this Cookie Policy if we change how we use cookies. Updates will be reflected in the "Last updated" date. We will notify you via email of any material changes.