Kodariby Natsu Labs
AboutFeatures
Projects
Kodari / Product policy

Privacy

How the current Kodari beta handles local work, account-linked cloud projects, shared snapshots, diagnostics, and optional analytics.

Current beta notice
Reviewed for RC5.20
This page describes the product paths implemented today.
ON THIS PAGEProjectsSharingSearch visibilityAnalyticsDiagnosticsFirebaseYour control

Kodari is in beta. This notice will be reviewed again before Public Beta and whenever material cloud or community behavior changes.

Projects

Guest projects are stored in your browser. Kodari also keeps local recovery snapshots in browser storage so a failed or damaged local save has a recovery path. When you sign in and cloud sync is available, project metadata and source files can be stored in the Kodari Firebase project so they can follow your account across devices.

Signing out does not erase local projects from that browser. Account-linked local projects are hidden from the normal Kodari workspace while signed out or while a different account is active; this is an application privacy boundary, not encryption of the browser profile. Projects already linked to one cloud account are not automatically uploaded into a different signed-in account. Device-only projects are never attached to the next signed-in account automatically; you must explicitly choose Connect local projects.

Shared projects

Publishing creates an unlisted snapshot that anyone with its link can run. You choose whether the share page also exposes source viewing and remix controls. Shared snapshots contain the project title, display author name, project metadata, and project data required by the browser preview. Output-only mode hides source and remix in the Kodari viewer, but it is not source-code DRM because the preview executes client-side. Shared snapshots do not intentionally include your email address.

Search visibility of shared projects

Kodari marks its shared-project viewer as noindex so share links are intended to remain link-accessible rather than discoverable through general web search. Search engines control their own processing, so do not treat an unlisted share URL as a secret.

Usage analytics

Kodari asks before enabling optional usage analytics. Beta instrumentation is designed to record product events rather than source code or project content. You can decline and continue using Kodari.

Diagnostics

Kodari keeps a small local history of client errors to help with recovery. Exporting diagnostics is your choice. The diagnostics export intentionally excludes project source code.

Firebase services

Kodari uses Firebase Authentication and Cloud Firestore for account and cloud-project functionality. App Check support is included for beta protection and becomes active after it is configured in Firebase.

Your control

  • Use Kodari locally without an account.
  • Export workspace backups.
  • Unpublish shared snapshots.
  • Decline optional analytics.

This notice may change as Kodari moves toward Public Beta, especially when new cloud or community features are introduced.

Kodari by Natsu Labs
HomeTerms