Khesh
Privacy policy
Last updated: 6 September 2026
Khesh is a household ledger that runs entirely in your browser. There are no accounts to create, no server of ours behind it, no telemetry, no cookies and no advertising. Your book stays on your device unless you export it yourself or connect the optional Google Drive sync - in which case it goes to your own Google Drive and nowhere else.
What stays on your device
- The book itself - accounts, journal entries, budgets, amounts, currencies and every name you type - in the browser's IndexedDB storage.
- The interface language, in
localStorage. -
If you connect sync: whether sync is connected, the id of the file it created in your
Drive, the email address of the connected Google account and the time of the last
sync, in a separate IndexedDB database named
khesh-sync.
None of this is sent to us; there is no server of ours to send it to. Clearing the site's data in your browser removes all of it.
Optional Google Drive sync
Sync is off until you connect it in Settings. When you do:
-
Khesh requests a single scope,
drive.file. That scope covers only the files the app itself creates - the onekhesh-book.jsonit writes - or a file you explicitly open through it, which is how a second Google account joins a book someone shared with them. The rest of your Drive stays invisible to it. - Your book is stored in that file as plain, unencrypted JSON in your own Google Drive. Anyone with access to that Drive account, or anyone you have shared the file with in Drive, can read it. Google's own terms and privacy policy govern the copy stored there.
- Khesh reads the connected account's email address once, from Google's Drive API, so that Settings can show which account is in use. It is kept on your device only.
- The access token authorizing these requests is held in memory for as long as the tab is open and is never written to storage. There is no refresh token and no session on any server.
Limited use
Khesh's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice nothing is transferred at all: your data moves between your browser and your own Google Drive, and no copy reaches us or any third party.
Deleting your data and revoking access
- Disconnect in Settings stops syncing and forgets the connection on this device. The file in your Drive stays where it is.
-
Delete
khesh-book.jsonin your Google Drive to remove the synced copy. - Revoke Khesh's access to your Google account at myaccount.google.com/permissions.
- Clear the site's data in your browser, or uninstall the app, to remove the book and everything listed above from the device. Export a backup from Settings first if you want to keep it.
Hosting and logs
The app's files are served as static files by Vercel, which - like any web host - records ordinary request information such as IP address and user agent. Khesh adds no analytics, no tracking pixels and no third-party scripts beyond Google Identity Services, which loads only if you connect sync. Those host logs are not combined with anything else.
Changes to this policy
If this policy changes, the date above changes with it. The page is part of the app's public source code, so its full history is visible in the repository.
Contact
Questions about this policy or about the app's data handling: github.com/anatolykhelmer/khesh/issues.