privacy

Your plan stays on your machine.

Caladia is local-first by design. The app runs in your browser; the marketing site serves static HTML. No accounts, no analytics that identify you, no cross-site tracking. This page describes what that means concretely — both for the app at app.caladia.ai and for this site at caladia.ai.

The app — app.caladia.ai

  • No accounts. No sign-up, no login, no identity at all.
  • No backend. The app is static JavaScript. There’s no server it talks to with your plan data.
  • Plans live on your device. A project lives in browser memory while you’re working. Saving downloads a .cala file to your disk; opening reads it back. Nothing in between touches our infrastructure.
  • We don’t see your plans. Not the activities, not the durations, not the resources, not the simulation results. We have no way to.

This site — caladia.ai

Static HTML, served by Cloudflare Pages. Cloudflare provides aggregate page-view counts for this site (their privacy-friendly Web Analytics — cookieless, no identifier stored on your device). No Google Analytics, no Plausible, no Mixpanel, no advertising or marketing pixels. No cookies are set by Caladia.

One third party sees network-level data when you load a page:

  • Cloudflare hosts the site and runs the analytics on it. As the CDN, they see standard HTTP request data (IP, requested URL, browser user-agent) for routing and abuse mitigation; the analytics beacon also reports page URL, referrer, viewport size, and timing back from your browser. Cloudflare’s privacy policy covers their handling of all of that.

What we don’t do

  • We don’t store anything on your device that links your visits between sessions (no cookies, no localStorage IDs, no client-side fingerprint).
  • We don’t set cookies (the site is static; nothing client-side persists anything to document.cookie).
  • We don’t share data with advertising networks.
  • We don’t send your plan, or any derivative of it, anywhere.

Changes

If any of the above changes — for example, if we ever add opt-in analytics or a feature that talks to a backend — the change will be documented here, called out in release notes, and rolled out as opt-in rather than opt-out.

Contact

Questions about any of this: [email protected].