Cassandra Cassandra Back to Cassandra
Legal

Privacy Policy

Last updated: July 7, 2026 Covers: Cassandra AI Chat

This Privacy Policy explains what information Cassandra collects when you use it, how we use it, who we share it with, and what choices you have. Cassandra is an AI chat service operated by Unaded (unaded.com). By using Cassandra, you agree to the practices described here.

This policy covers Cassandra only. If you use our radiology tools (image search, report/impression/protocol generators, the Desktop Companion), those are governed separately. This document is the source of truth for Cassandra. If anything elsewhere on the site contradicts it, this document governs.


1. What we collect

The table below covers every category of information Cassandra collects.

What
When
Where it goes
Chat messages & repliesEverything you type and every AI response generated.
Each message sent.
Our server (query log), the systems that generate replies, and your browser’s local storage. Logged-in users’ chat history also syncs to your account so it follows you across devices.
Conversation historyThe full thread stored client-side in your browser.
Continuously while you use Cassandra.
Your browser (all users). Also stored in your account data if you’re logged in, so history follows you across devices. Guests: browser only.
File attachmentsImages or documents you attach to a message.
On upload.
Our server (auto-deleted after 1 day), then the systems that generate replies.
Token & cost usageInput tokens, output tokens, and dollar cost per query (both the underlying cost and the marked-up amount charged against your balance).
After each query completes.
Our internal query log. Used for credit limits, the usage widget, per-reply cost display, and admin analytics. Never shared outside our organization.
Account informationEmail, hashed password, username. Created only if you register.
On registration.
Our database. Email may also be used for payment receipts.
Purchased credit balanceDollar amount of credits added after a successful purchase.
After a successful payment.
Our database: user meta (registered users) or a guest credits table (guests).
Payment recordSession ID, amount paid, email used at checkout. Card numbers never reach us.
After a completed checkout.
Our database (session ID + amount). Our payment processor retains the full payment record under its own policy.
Guest session IDA cookie holding a random 32-character string.
On first visit while logged out.
Our server (for credit tracking). 1-year cookie in your browser.
IP address & user-agentStandard HTTP request fields.
Each page load and request.
Our server logs and hosting infrastructure logs, plus the query log for analytics (device type, browser, OS parsed from user-agent).
Client fingerprintA one-way SHA-256 hash of your IP + user-agent + a site-specific secret. Not reversible into the original IP.
Computed on each guest request.
Our guest credits table. Used to detect returning guests across incognito windows / cleared cookies so free trial credits can’t be farmed. The raw IP is not stored in this hash — only the salted digest.
Approximate geolocationCountry, region, and city derived from your IP address.
Once per unique IP.
Looked up through a location-lookup service and cached on our server for 30 days. Stored on the query log row for admin analytics (aggregate geographic breakdowns).
Referrer URLThe page you came from before landing on Cassandra, when your browser provides one.
Each request.
Our query log row. Used to see which sites / pages drive Cassandra usage.
Claim tokensOne-time token to restore guest credits on a new device.
When a guest requests a claim link after purchasing credits.
Our guest credits table. Invalidated after single use.

2. What we don’t collect

We have the technical capability to collect each of these. We choose not to. Collecting any of them would require a material change to this policy.

No advertising trackers

No analytics pixels, no retargeting beacons, no ad networks on any Cassandra page.

No sale of data

We do not sell, license, or transfer your data to data brokers, advertisers, or any other party for commercial gain.

No cross-site tracking

Our session cookie is scoped to unaded.com only. We do not track you across other websites.

No keystroke logging

We see only what you deliberately type into Cassandra’s input field and submit. Nothing else.

No screen capture

Cassandra does not capture, record, or transmit anything visible on your screen beyond what you paste into the chat.

No card numbers

Our payment processor handles all card data. We never see, store, or process card numbers or CVCs.


3. How we use your information

  • To generate AI replies. Your message is sent to the systems that generate a response so it can be returned to you.
  • To enforce credit limits. Token and cost data is tracked in our query log so Cassandra can display your remaining budget and block queries when your balance is exhausted.
  • To process payments. We pass an internal reference ID during checkout so credits can be attributed to your account or guest session when a payment completes.
  • To maintain your account. Email and hashed password are stored so you can log in, recover your password, and persist your credit balance across devices.
  • To prevent abuse. A one-way hash of your IP + user-agent (the “client fingerprint”) lets us detect returning guest visitors and prevent unlimited free-trial farming via new browser windows. This hash never re-identifies you personally and is not shared outside our organization.
  • For admin analytics. Our administrator uses aggregate dashboards showing query counts, revenue vs. underlying cost, geographic distribution, and device breakdowns. Only administrators can view these dashboards.
  • To diagnose problems. Server logs (IP, user-agent, timestamps) help us investigate errors and detect abuse.
  • To improve Cassandra. Aggregate, anonymized usage patterns (query volume, average cost per query, popular features) inform product decisions. We do not use your individual messages for this.

We do not use your chat messages to train any AI model. The systems we use to generate replies also do not use your inputs to train their models, per their current data-use terms.


4. How your data is processed

A handful of external service categories touch user data during normal Cassandra operation. We choose providers carefully and limit what each one receives to only what’s needed to perform its function.

Reply generation

Every message you send is passed to the systems that generate replies. They never see your IP address directly — only the message content reaches them through our server. Per their current data-use policy: inputs are not used to train models, and are retained for up to 30 days for abuse-monitoring, then deleted.

Payment processing

When you purchase credits, you are redirected to a secure hosted checkout page. Our payment processor handles all card data under PCI-compliant infrastructure. We receive only a cryptographically signed confirmation containing the session ID, amount, and email you provided. We verify that signature before granting any credits.

Hosting

Our hosting provider stores our database and files, including all data described in this policy. They have infrastructure-level access to server logs and the database. They are not contracted as a HIPAA Business Associate and do not receive PHI by design.

IP geolocation

When a query is logged, the sending IP is looked up through a location-lookup service to derive an approximate country, region, and city for the admin analytics dashboard. The lookup is anonymous (no query content is transmitted), rate-limited, and the result is cached on our server for 30 days so the same IP is only looked up once per month.

Fonts

Cassandra pages load web fonts based on the font family you pick in Settings. No query content is sent as part of loading these fonts.


5. How data flows — chat message

You type a message and send → Cassandra sends it (plus conversation history and any attachments) to our server, authenticated as you (logged-in users) or by session cookie (guests) → our server checks your credit balance → if balance allows, our server opens a streaming connection to generate a reply → a reply streams back token-by-token → our server relays those tokens to your browser as they arrive → Cassandra renders the final reply once the stream completes → message and reply are logged in our own query log, saved to your browser’s local storage, and (for logged-in users) synced to your account.

Your browser never talks directly to the systems that generate replies. They never see your IP address, browser, or device information.

5b. How data flows — credit purchase

You click Buy Credits → Cassandra attaches an internal reference identifying your account or guest session to the checkout link → you’re redirected to a secure hosted checkout page → you pay → our payment processor sends a signed confirmation to our server once the payment completes → our server verifies that signature → credits are added to your balance → the usage widget updates on the next page refresh.


6. Cookies and browser storage

  • cassandra_chats_v1 (localStorage) — your full conversation history: messages, titles, timestamps, starred status, per-reply cost figures. Private to your device (also mirrored in your account data if logged in).
  • cassandra_theme_v1 (localStorage) — your light/dark theme preference.
  • cassandra_font_scale_v1 (localStorage) — your font-size preference (85%–120%).
  • cassandra_font_family_v1 (localStorage) — your font choice (Inter, System UI, DM Sans, Serif, or Mono).
  • cassandra_bg_variant_v1 (localStorage) — your light-mode background variant (white, blue tint, cool grey, warm grey, or solarized).
  • Guest session cookie (1-year expiry) — a random 32-character string identifying your guest session for credit tracking. Set by our server on first visit to /cassandra/ while logged out.
  • Account sign-in cookies — standard session tokens, set only after you log in. Keep you signed in across page loads.

Not a cookie: the “client fingerprint” described in Section 1 is computed server-side from your request headers and never stored on your device. There is nothing for you to clear locally.

All the browser-stored items above can be cleared by clearing site data for unaded.com in your browser settings. Clearing cassandra_chats_v1 removes your local chat history permanently (though logged-in users can still recover it from server-side sync). Clearing the guest session cookie removes your guest session — if you have purchased credits and no claim link was saved, those credits may become inaccessible via cookie alone, but our fingerprint lookup will typically reunite you with your balance from the same browser/device.


7. Data retention

Chat logs (server)

Query log rows are retained indefinitely. Request deletion by emailing us. Deleting your account triggers deletion of associated logs within 30 days.

Chat history (browser)

Persists in localStorage until you clear it. Logged-in users additionally have a server-side mirror (up to 4 MB), which is deleted when the account is deleted.

File attachments

Auto-deleted from our server after 1 day by a scheduled task. The systems that generate replies retain inputs for up to 30 days then delete them.

Account data

Retained while your account is active. Deleted within 30 days of account deletion, except financial records required for compliance (typically 7 years).

Credit purchase records

Our payment processor retains payment records per its own policy. We retain the session ID and amount for billing reconciliation.

Guest credit records

Retained in our database while the session has a non-zero balance. Contain only a session ID, credit balance, and the client fingerprint hash — no name, email, or other personal identifiers.

Geolocation cache

Country / region / city results are cached per unique IP for 30 days, then discarded if not renewed.


8. Security

  • TLS everywhere. All traffic between your browser and unaded.com, and between our server and the external services we rely on, uses HTTPS.
  • Signature verification. Every payment confirmation is cryptographically verified before any credits are granted. Forged confirmations are rejected.
  • Authenticated requests. Cassandra requests from logged-in users are authenticated so they’re attributed to the correct account.
  • Salted client fingerprint. The abuse-prevention fingerprint is a one-way SHA-256 hash including a site-specific secret, so raw IPs never enter our fingerprint column and the hash cannot be reversed even if the database leaked.
  • Upload execution block. Files uploaded to Cassandra are stored in a dedicated directory that is configured to refuse to execute anything with a script extension (.php, .py, .sh, etc.). Even if a malicious file is uploaded, the server will never run it.
  • Minimal data footprint. We don’t collect what we don’t need. No advertising trackers, no PHI, no cross-site tracking.

We have not undergone a SOC 2 audit. We are not contracted as a HIPAA Business Associate and do not execute BAAs. Cassandra is designed to operate outside the BAA pathway by not knowingly processing PHI.

To report a security issue, email admin@unaded.com with subject line Security.


9. Your rights

Regardless of where you are, you may exercise the following rights. We do not condition access to Cassandra on waiving any of them.

Access

Request a copy of data we hold — account info, chat logs, credit history, query logs. Email admin@unaded.com with subject Data Access.

Deletion

Request deletion of your account, chat logs, or guest credit records. Processed within 30 days. Financial records required by law are excluded.

Correction

If we hold incorrect information (e.g. wrong email), let us know and we’ll correct it.

Opt-out

Stop using Cassandra at any time. Clear site data for unaded.com in your browser to remove local history. Contact us to delete your account.

California (CCPA/CPRA)

Right to know what is collected (Section 1), right to know it is not sold (Section 2), right to non-discrimination for exercising these rights.

EU / UK (GDPR)

Lawful basis: legitimate interest (logs, fraud prevention) and your explicit request (AI queries, payments). Additional rights: portability, complaint to supervisory authority.


10. Changes to this policy

We may update this policy when Cassandra changes. Material changes will be noted at the top of this page and, for account holders, communicated by email. The “Last updated” date above reflects the most recent revision. Continued use after a change constitutes acceptance.

Children. Cassandra is intended for users 18 or older. We do not knowingly collect data from anyone under 18.

International transfers. Unaded is operated from the United States. The service providers we rely on may process data in multiple jurisdictions. Where required by EU/UK law, transfers rely on Standard Contractual Clauses with our subprocessors.


11. Contact

For privacy questions, data access/deletion requests, or security disclosures:

admin@unaded.com

Use subject lines Data Access, Data Deletion, or Security for faster routing. We reply within 2 business days. Data requests are processed within 30 days.

Privacy Policy · Cassandra · Effective July 7, 2026
Cassandra Terms of Service