Browse KazaKit docs

Data and privacy

Local-first and privacy

Understand where your creative workspace lives and what works offline.

Local-First and Privacy Positioning

Verified Product Characteristic

KazaKit is designed as a local-first desktop application.

Core behavior:

  • project data is stored locally;
  • the desktop build uses SQLite;
  • application-managed files live in local app data;
  • core workflows do not require cloud sync;
  • core workflows do not require a constant internet connection;
  • the macOS build is designed around Tauri and App Store sandbox constraints.

What the Website May Say

Good:

  • “Your creative workspace lives on your device.”
  • “KazaKit’s core workflow works without cloud dependency.”
  • “Projects, notes, tasks, documents, and project media are stored locally.”
  • “No cloud sync is required for the core experience.”

Avoid unless separately verified for the website release:

  • “End-to-end encrypted”
  • “Zero telemetry”
  • “Impossible for anyone else to access”
  • “Automatic backup”
  • “Cross-device sync”
  • “Real-time collaboration”
  • “Version history for every edit”

Important Browser-Mode Note

The Next.js development UI can render many global screens in a normal browser. Full project persistence and file behavior depend on the Tauri/SQLite desktop environment. The public wiki should document the desktop product, not the limitations of browser development mode.