How We Handle Client Data

The Short Version

Calisomnia treats private creative work like client data, not like ad inventory. The browser can show the interface, but the server decides identity, ownership, access, prices, tickets, payouts, rights, and final workflow state.

What We Minimize

• Attribution is limited to safe campaign keys: ref, utm_source, utm_medium, utm_campaign, utm_content, and utm_term.
• Private pages should render only the data needed for the current view.
• Public pages use public projections. We do not expose whole internal user records just to build profiles or SEO tags.
• Precise location, raw IP addresses, proxy-chain values, fraud signals, and internal database IDs should not be hydrated into public browser payloads.

What Stays Server-Side

• Service-role keys, database credentials, signing secrets, and provider keys.
• Payment amounts, ticket authority, payout state, wallet balances, and ledger entries.
• Contract authority, rights state, collaboration membership, and private file access.
• Plan, credit, quota, generation-limit, and entitlement decisions.

Browser-visible labels such as plan, role, or UI state are presentation only. Sensitive endpoints verify the current user and derive authority from server state.

Consent And Tracking

Optional analytics are off by default. Calisomnia stores first-party consent as cali_consent, respects Do Not Track, and exposes an event hook so analytics can load only after consent. Private workspaces are not places for ad pixels, behavioral marketing, or broad session replay.

Unreleased Work

Drops, stems, lyrics, prompts, generated media, cover art, edits, private comments, client notes, contracts, rights records, and collaboration-room state are private by default unless the creator intentionally publishes or shares them.

Generated or transformed assets need provenance: who created them, what inputs were used, the workflow type, rights declarations, consent records, publication state, and applicable terms.

Recommendations And Progress

Recommendations and work-progress records can reveal private intent. Last playback position, selected stems, private markers, unfinished comments, contract sections, notes, and draft state are user data, not ordinary ad analytics.

Exports And Support

Authenticated browser exports, HAR files, copied page source, local-storage dumps, and diagnostic archives can contain active capability material. We treat them as restricted evidence, not ordinary screenshots. Support should ask for narrow, redacted diagnostics rather than full authenticated page dumps.

Auditability

Sensitive business actions should create audit records with opaque request IDs. Request IDs are for support, debugging, and incident response. They must not encode account IDs, payment state, private object IDs, emails, or route secrets.

Deletion Language

We avoid vague promises. Hidden, archived, expired, soft deleted, scheduled for deletion, cryptographically erased, permanently deleted, and legal hold mean different things. Calisomnia's standard is to describe retention and deletion honestly, including backups, logs, legal records, provider copies, exports, and support evidence where they apply.