Codex
Open Codex
BACK TO CRYPTICA

Privacy Policy

Codex Cryptica is designed with a privacy-first, local-first philosophy. We believe your campaign data and creative work belong to you, not us.

1. Data Storage

By default, all data you create in Codex Cryptica (lore, chronicles, images, maps, and world configuration) is stored exclusively in your browser's Origin Private File System (OPFS) — a private storage area built into your browser, similar to a folder on your hard drive, but one only Codex Cryptica can open. It never leaves your device unless you explicitly export it, sync it to a folder, or use an AI feature.

  • No Server Storage: We do not host your campaign data on our servers.
  • User Control: You have full control over your data. Clearing your browser cache or deleting the application storage will remove your data.

2. Local Folder Synchronization (Optional)

You may choose to synchronize your campaign with a folder on your computer.

  • Direct Access: This mirrors your internal data to a directory you select using the Web File System Access API.
  • Third-Party Providers: If you choose a folder managed by a third-party service (like Google Drive, Dropbox, or iCloud), those providers will handle the transmission of your data according to their own privacy policies. Codex Cryptica does not directly communicate with these cloud providers.

3. AI Features (Optional)

If you use any AI feature (Lore Oracle chat, entity generation/revision, connection suggestions, Image Generation), your data is processed as follows:

  • OpenAI: Most AI features route through OpenAI's API by default. This includes conversational features (Lore Oracle chat, entity revisions, generator sessions) as well as one-shot analysis and generation features (such as detecting potential connections between entities, or generating a new entity related to an existing one).
    • For conversational features, requests can include a conversation/interaction identifier so follow-up turns can reference earlier context without resending it.
    • For one-shot features, each request is sent and processed independently, with no ongoing conversation identifier.
  • Google Gemini: Used for Image Generation, and as an automatic fallback for other features if OpenAI is unavailable. Snippets of your current campaign context (entities and chronicles) are sent to Google's Gemini API in these cases.
  • Data Usage: According to Google's and OpenAI's standard API terms, data sent via their paid/tier-based APIs is typically not used to train their global models.
  • Opt-out: You can disable all AI features by enabling "AI Disabled" in the settings.

4. Analytics and Telemetry

Nothing inside your vault is ever tracked. Creating, editing, connecting, or deleting anything in your campaign — lore, chronicles, entities, maps — generates no analytics of any kind.

Tracking is limited to our public marketing and generator pages (the pages you land on from search engines or ads, before you have a vault open):

  • Cloudflare Web Analytics: Anonymous, cookie-free pageview counts across the site.
  • Cloudflare Zaraz: Anonymous funnel events on marketing/generator pages only — a page visit, starting or completing a generator, and the moment you choose to save generated content to your vault (including whether that content had links to other entities). We also record which search engine, campaign, or referral link brought you to the site (via standard utm_* URL parameters), so we can tell which marketing efforts are effective. None of these events include your generated content, campaign data, or anything that happens after you land in the app.

5. Third-Party Services

  • Web Fonts: We may load fonts from Google Fonts.
  • Icons: We use icon sets which are bundled with the application.
  • Publishing Verification: When you create a public guest snapshot, we use Cloudflare Turnstile to prevent automated abuse of the publishing service. Turnstile processes limited browser and network signals as described in the Cloudflare Turnstile Privacy Addendum.

6. Changes to this Policy

We may update this policy to reflect changes in our storage architecture or feature set. The principle of "Local-First" will remain our core commitment.

Last Updated: August 2026