PRIVACY

What Krate collects, in plain words.

Last updated 2026-08-29. This page is written from the source code, which is public; every claim here can be checked against it.

Apps you run

Krate apps run in a permission sandbox. An app can only touch what you granted on its consent screen, and the list you approve is the whole list. App data stays on your computer unless the app declares a network or shared capability and you approve it.

Anonymous usage counting

The Krate tool counts how many people use it, without learning who they are. What is sent: a random id generated on your machine, the Krate version, the operating system name, and which of a fixed set of actions happened (make, open, publish). What is never sent: app names, prompts, file paths, usernames, email, location, or any hardware identifier. The id is random bytes in a file; deleting the file makes your install a new anonymous one. The first run prints one line explaining this. Turn it off permanently with KRATE_NO_USAGE=1.

The website

krate.tech pages send one anonymous view event: the page path and the day. No cookies, no identifiers, no referrer, and no third-party analytics.

Publishing a link, if you sign in

Publishing an app to the shared gallery uses GitHub sign-in. We store your GitHub login and the apps you publish, because published apps are credited to their publisher. Nothing else about your account is read or stored. Shared-store data (an app feature you opt into per app) is synced through krate.tech and readable by anyone holding that store's invite code, which the consent screen says before you approve it.

Questions

Open an issue at github.com/incyashraj/krate -- the same place the code that this page describes lives.