Cookies & Local Storage at Kaisuki

Kaisuki Media LLC operates Kaisuki, a community chat platform built around servers, channels, DMs, voice and stage rooms, forums, and posts. To make all of that work, we store a small amount of data in your browser — some as cookies, and quite a lot as local storage. This page tells you exactly what we keep, why, who set it, and how to take control.

We don't run advertising networks or sell your data, so you won't find a wall of ad-tracking cookies here. Most of what we store is either strictly necessary to log you in and keep your session secure, or it's there to remember the way you've set Kaisuki up for yourself.

"Cookies" is shorthand for a few related browser technologies. Kaisuki leans more on local storage than on traditional cookies, so it's worth being precise about the difference:

• Cookies — small text files your browser sends back to us with each request. We use these mainly for session security and load balancing.
• Local storage — a larger, longer-lived store that keeps data on your device until you or your browser clears it. This is where most of your Kaisuki experience lives: your logged-in session, your interface preferences, and drafts.
• Session storage — the same idea as local storage, but cleared the moment you close the tab. We use it for short-lived interface state.
• Service worker cache — cached assets (scripts, icons, emoji) so the app opens fast and survives a flaky connection.

Everything falls into one of four buckets. Only the first is non-negotiable; the rest are there to serve you.

Essential & authentication — the platform will not run without these.

• Your signed session token (JWT), so you stay logged in across channels, servers, and reloads without re-entering your password.
• Security and anti-abuse signals that help us spot account takeovers, spam bots, and rate-limit floods before they reach your communities.
• CSRF and request-integrity tokens that stop other sites from acting on your behalf.
• Connection routing that keeps your real-time gateway (messages, typing, voice/stage presence) pinned to a healthy server.

Preferences — how you've made Kaisuki yours.

• Theme, language, and accessibility settings such as reduced motion.
• Interface layout: sidebar collapse state, member-list visibility, channel and server order, and which server you last had open.
• Notification and Do-Not-Disturb choices at the device level.
• Unsent drafts for messages, forum posts, and replies, so you don't lose a paragraph to an accidental refresh.

Product & commerce — for the paid corners of Kaisuki.

• State for Kaisuki Spark and Spark Pro premium tiers, your Ember balance display, and the cosmetics shop.
• Checkout continuity so a boost or Ember purchase can complete cleanly across pages.

Analytics & performance — aggregate, never sold.

• Anonymized, aggregated usage so we can see which features get used and where the app feels slow.
• Crash and error diagnostics that tell us a screen broke — without reading your message contents.

Each category earns its place. In practice these files let us:

• Keep you securely signed in so you're not re-authenticating every time you switch servers.
• Protect your account and your communities from bots, spam, and takeover attempts.
• Reopen Kaisuki exactly how you left it — same theme, same layout, same server.
• Hold onto drafts and in-progress work when your connection drops or you close a tab by accident.
• Power creator earnings, Spark subscriptions, Ember, and the shop reliably.
• Understand what's working and fix what's slow, using data that isn't tied to your identity.

First-party cookies and storage are set by Kaisuki itself. That's the overwhelming majority of what's on your device, and it covers everything essential — your session, your preferences, your drafts.

Third-party cookies are set by services we've chosen to work with, and only in the specific places they're needed:

• Google — when you choose "Sign in with Google," Google sets its own cookies to complete OAuth authentication.
• PayPal — on payment surfaces only, to process boosts, Spark subscriptions, and Ember purchases securely. These load when you check out, not while you're chatting.
• Our infrastructure and content-delivery providers — which may set operational cookies to route traffic and serve uploaded images, files, avatars, and banners quickly.

These partners act as data processors under our instructions. What each collects is governed by its own policy; our own handling is described in our Privacy Policy at /privacy.

You have two sets of controls: the ones inside Kaisuki, and the ones in your browser.

Inside Kaisuki — adjust what you can:

1. 1Open User Settings from your avatar in the bottom-left.
2. 2Under Privacy, opt out of analytics and diagnostics collection.
3. 3Under Appearance and Notifications, set the preferences you want remembered.
4. 4Sign out to clear your active session token from this device.

In your browser — clear or block storage for kaisuki.com:

1. 1Chrome: Settings → Privacy and security → Cookies and other site data → See all site data and permissions, then search for kaisuki.com.
2. 2Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data, then search for kaisuki.com.
3. 3Safari: Settings → Privacy → Manage Website Data, then search for kaisuki.com.
4. 4Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data → See all cookies and site data, then find kaisuki.com.

Clearing this data signs you out and resets your preferences, so you'll set up your layout again on next login.

Because there's still no shared industry standard for how sites should honor browser "Do Not Track" signals, Kaisuki doesn't change behavior based on the DNT header alone. We keep our footprint small either way: no ad networks, no cross-site behavioral tracking, and no sale of your data. Where the law requires us to recognize an opt-out preference signal such as Global Privacy Control, we honor it. You can always opt out of analytics directly in User Settings.

As Kaisuki grows and the tools we rely on change, we'll update this policy and revise the date at the top of the page. If a change is significant — say, we introduce a new category of storage — we'll flag it more prominently than a quiet edit. Continuing to use Kaisuki after an update means the current version applies to you.

If something here is unclear or you want to exercise a privacy choice, we're glad to help.

• Legal and formal privacy inquiries: [email protected]
• Support requests (login required): submit a ticket at /ticket/requests
• Guides and self-serve answers: the Help Center at /help

For the fuller picture of how we handle your information, see the Privacy Policy at /privacy, the Terms of Service at /terms, our Community Guidelines at /guidelines, and the Safety Center at /safety.