Cookies policy.

1. What this policy covers

This Cookies Policy explains how RuneShips ("we," "us," or "our") uses cookies and similar technologies on runeships.com. It complements our Privacy Policy, which describes the broader handling of your personal information.

If you continue to use the platform after reading this policy, you agree to the use of cookies as described here. You can change your mind at any time using the Cookie settings entry point in the footer.

2. What are cookies

Cookies are small text files that a website places on your device when you visit it. They let the site remember things between page loads (for example, that you're signed in).

Similar technologies include browser local storage and session storage. These don't get sent back to a server with every request the way cookies do, but they serve overlapping purposes. This policy covers both.

We don't use Flash cookies, web beacons, fingerprinting, or any cross-site tracking technology.

3. How we use cookies

RuneShips uses cookies for essential purposes only. There are three categories of cookie use you'll see across the web:

• Essential: required for the platform to function (authentication, session, security). You can't opt out of these without breaking sign-in.
• Functional: remember preferences (theme, language). We don't currently use any.
• Analytics / Advertising: measure usage or target ads. We don't use any of these.

Every cookie we set falls in the essential category.

4. The cookies we set

That's it: three cookies, all first-party (set by runeships.com), all strictly necessary.

The Supabase cookies (sb-kbokzwvnqeuxkcxigkdh-...) are set by our database and authentication provider, Supabase. The project identifier kbokzwvnqeuxkcxigkdh is our specific Supabase project reference. These cookies travel only between your browser and runeships.com; they aren't shared with Supabase's other customers or with any third party.

5. Third-party cookies

We don't use third-party cookies. Specifically:

• No advertising cookies (Google Ads, Meta Pixel, etc.)
• No third-party analytics cookies (Google Analytics, Mixpanel, Segment, etc.)
• No social media cookies (Twitter/X, LinkedIn embeds, etc.)
• No tracking pixels of any kind

Our hosting provider Vercel does not set tracking cookies in the configuration we use. Vercel may serve our pages from its CDN, but no Vercel-controlled cookie is placed on your device by browsing runeships.com.

6. Do Not Track signals

Some browsers can send a "Do Not Track" (DNT) signal with each request. There's no industry consensus on how websites should respond to DNT, so we don't behave differently when we receive it; but since we don't track you in the first place, this doesn't change what gets set on your device.

We also honor the Global Privacy Control (GPC) signal where it's a legal requirement. For users in jurisdictions where GPC is recognized as a valid opt-out (e.g., California, Colorado, Connecticut), receiving the signal has no practical effect on RuneShips because we don't sell or share personal information for advertising, but we respect the signal as a matter of policy.

7. Local storage and similar technologies

We use a small amount of browser local storage for transient UI state, for example, remembering which informational popovers you've dismissed within a session. These values:

• Live only on your device
• Aren't sent to our servers
• Don't contain personal information
• Can be cleared from your browser settings at any time

We don't use IndexedDB, Service Worker caches, or other persistent client-side databases for personal data.

8. How to control cookies

You have several ways to control cookies on RuneShips:

• Reset your cookie banner. Use the Cookie settings link in the footer of every page, or the button at the bottom of this policy. This clears your acknowledgment so the banner reappears on your next page load.
• Clear cookies in your browser. Every modern browser lets you delete cookies for a specific site. Doing this for runeships.com will sign you out and bring the cookie banner back. See your browser's help docs:
  • Chrome
  • Firefox
  • Safari
  • Edge
• Block cookies entirely. You can browse our marketing pages (the home page, /story, /proof, /companies marketing) without cookies. Signed-in features (dashboard, profile, submissions) require the Supabase auth cookies to work.
• Sign out. Signing out from /profile?tab=account clears the Supabase auth cookies.

9. How long cookies last

Cookie lifetimes are listed in the table in section 4. In summary:

• runeships_cookie_consent: 12 months from acknowledgment.
• Supabase auth cookies: persist as long as you stay signed in, with periodic refresh. Clearing them or signing out removes them.
• The PKCE verifier cookie: deleted within minutes, automatically.

We don't intentionally set any cookie with a lifetime longer than 12 months.

10. Changes to this policy

We may update this policy from time to time (for example, if we add a new essential cookie or change how an existing one works). Material changes will be posted at runeships.com/cookies with an updated "Last updated" date, and we'll re-show the cookie banner so you can review the change.

11. Contact

Questions about cookies? Email us at hello@runeships.com. For broader privacy questions, see our Privacy Policy or contact the same address.