Last changed: 18 November 2026.
This policy covers every part of Kaal: the Kaal server (kaal-server,
however it is installed), the web app it serves, Kaal for iPhone and Kaal for
Chrome.
The person or organisation that runs the Kaal server you use (here called the operator) decides where it runs, who has an account, which optional features are on, and how backups are kept. The operator holds the key that Kaal’s encryption uses and can read every vault on their server. If you run Kaal yourself, that is you. Questions about your data, or requests to see, correct or remove it, go to the operator: Kaal’s authors cannot see or change anything on someone else’s server.
/v1/notes/{id}, never the actual one), the result, which token or account
id made it, and how long it took. Never what was sent or received, search
words, file contents, tokens or IP addresses. A proxy that the operator puts
in front of Kaal may keep logs of its own. The one the Docker install sets up
(Caddy) is set to keep no record of requests, failed ones included: it logs
its own starting up and what happens with its HTTPS certificate, which names
the domain. An installation made before that setting was added (November
2026) logged each request that failed, such as one made while Kaal was
restarting, with the visitor’s address, the address asked for and the
request’s headers, until it is updated (deploy/docker/kaalctl update);
Docker keeps at most 30 MB of those older lines and replaces them as new
ones are written.Nothing, unless the operator turns one of these on.
Reading receipts with a model. By default Kaal reads receipts with fixed
rules on the server. The operator can instead have a language model read each
medical receipt (KAAL_RECEIPT_AI). The receipt’s text and pictures of its
first pages are then sent to the model they chose:
| Choice | Where the receipt goes |
|---|---|
ollama |
A model the operator runs on their own machine or network. Nothing leaves it. |
anthropic or claude-cli |
Anthropic, which makes Claude. |
openai |
The service at the address the operator gives: OpenAI, OpenRouter, or a program they run themselves. |
Only medical receipts are sent, one at a time as they arrive or when you ask for one to be read again; notes and other files never are. A paid service handles them under the operator’s own account and its terms and data settings. The model is given no tools and is asked only which value on the receipt is which.
Signing in with Google (or another OpenID Connect service). When the operator offers it and you choose it, your browser goes to Google’s sign-in page, and Google tells your Kaal who you are: an id, your email address and your basic profile, of which Kaal uses only your name. Kaal asks for nothing else, and gets no access to your mail, files or contacts. To finish the sign-in, the server checks with Google and fetches Google’s published signing keys. Google learns that you signed in to this Kaal, as it does whenever you sign in somewhere with Google.
HTTPS certificates. If the operator lets the Docker install set up HTTPS for a domain name, it asks a certificate authority (Let’s Encrypt or ZeroSSL) for a certificate. That request carries the domain name only.
Kaal never checks for updates or contacts its authors. Installing and updating it downloads software from where the operator chooses.
The web app is served by your Kaal server and loads nothing from anywhere else; the server tells the browser to refuse anything that is not its own.
It keeps one cookie, which holds your session: __Host-kaal_session over
HTTPS (kaal_session when the operator is trying Kaal out over plain http).
Page scripts cannot read it, it is sent only to your Kaal, never from another
site, and it lasts 30 days or until you sign out. Signing in with Google adds
a second cookie for the few minutes that trip takes. The only other thing the
web app puts in your browser is a code held, for that tab only, while you
sign the iPhone app or the Chrome extension in; it is removed once that is
done.
The app talks only to the Kaal address you type in. You sign in on your Kaal’s own page in Apple’s sign-in sheet, so the app does not see your password when you sign in. It asks for your password only in Settings, when you change it, make new recovery codes or a token, or delete your account; it sends it to your Kaal for that one request and does not keep it.
“Save to Kaal” in other apps. The app adds itself to the iPhone’s share menu. When you choose it there, what you chose to share (pictures, a PDF or other file, a web page’s title and address, or some text) is sent to your Kaal as a note or a receipt, and to nowhere else. In Safari it reads only the page’s title and address. It uses the session the app keeps, which the two share through the keychain; it works only after you have signed in to the app.
What it keeps on the phone:
Signing out deletes the session and what the app knew about your account. Anything still waiting to be sent stays on the phone (the app says so before you sign out) and is sent when you next sign in. Deleting the app removes what it kept, with one exception that is the iPhone’s doing: the session in the keychain stays until the app is next installed and opened, when the app removes it. Deleting the app does not end the session at your Kaal either; sign out first, or end it under Settings → Signed-in browsers and apps.
While “Save to Kaal” is open it holds a copy of what you shared in a folder of its own, protected like the rest of the phone’s files, and removes it when the sheet closes.
Safari stays signed in. Apple’s sign-in sheet shares Safari’s cookies, so that someone who signed in to their Kaal in Safari in the last ten minutes need not type the password again (after that, Kaal asks for it once more before letting the app in). Signing in there therefore also leaves Safari on the phone signed in to your Kaal, for up to 30 days, listed with your other browsers as “Safari on iPhone”. Signing out of the app, or deleting it, does not end that: sign it out under Settings → Signed-in browsers and apps, or open your Kaal in Safari and sign out there.
What it asks permission for, and why:
The extension sends what you save to the Kaal server named in its settings, with a token for that server, and to nothing else.
Connecting it. “Connect with my Kaal sign-in” opens your Kaal’s own sign-in page in a window of its own. You sign in there as you usually do and press Allow (if that browser was signed in more than ten minutes ago, your Kaal asks for your password again first); your Kaal then makes a token for the extension (to read, reveal and write in the vault you had open, as far as your role there allows) and hands it over. The extension never sees your password. You can paste a token you made yourself instead. Either way the token is listed in the web app under Settings → Tokens, where you can revoke it.
What a save sends: the page you are on as a PDF (printed by Chrome from
that tab), or the PDF or file you are saving, or the text you selected; with
it, the page’s title and address. Kaal keeps the address without the part
after ? or #, where sites often put session codes.
What it keeps in Chrome: your Kaal’s address and token, and the names of the sites that receipts in your vault were saved from, by you or by anyone who shares the vault (so it can offer “Save receipt” there), in this Chrome profile on this computer; and, while a save is under way, its progress, which Chrome forgets when it closes. Every ten minutes it asks your Kaal how many receipts are waiting to be checked, for the number on its icon, and for that list of sites. “Disconnect” in its settings removes the address and token; removing the extension removes everything it kept.
What Chrome asks you to allow, and why:
document.contentType, evaluated in that page), has Chrome
print the page, or loads the file and reads it. For a PDF that its site
will not send a second time, and only if you press “Load it again and
save”, it has Chrome load the tab again and copies the PDF as it arrives;
the site is asked again, as when you press Reload, and the tab is given
what the site sent, unaltered. Chrome describes this
permission in broad terms (“Read and change all your data on all
websites”) because a debugger could do more; this extension does nothing
else with it.chrome://extensions.The extension does not read your browsing history, runs nothing in a page you have not asked it to save, and does not look at a page until you save it.
Everything here is done in the web app, at the address of your Kaal, unless it says otherwise. None of it needs the operator, or Kaal’s authors.
receipts.csv). It is not
encrypted and needs no Kaal to read, so keep it as safe as the vault.kaal-server account remove.Kaal for iPhone has “Delete my account” under Settings, which does what the web app’s does and then signs the app out; a vault is deleted, and a copy downloaded, in the web app (“Open Kaal in the browser” in the app’s Settings). Kaal for Chrome has no such buttons of its own; open your Kaal’s address in a tab.
Kaal is not aimed at children. Its authors collect nothing about anyone, children included.
This policy is kept with Kaal’s source code, so every change to it is recorded there with its date. A change in what Kaal does with data will be described here before it is released.
For questions about Kaal itself, or this policy, open an issue on the project’s GitHub repository (see Getting help). For anything about your own data, ask the operator of your Kaal server.