Privacy

The short version

Noo does not collect, transmit or sell any personal data. There is no account, no analytics, no advertising identifier, no crash reporting and no third-party SDK that gathers anything. The application works fully offline; it reaches a network only if you turn sync on or choose to download a transcription model, and both are things you do deliberately.

What Noo stores, and where

Everything you put into Noo — tasks, notes, time records, attachments and voice memos — is written to a single SQLCipher database file on your own device, encrypted with a password you choose. Nobody but you holds that password, and it is not recoverable: if you forget it, the data cannot be decrypted by us or by anyone else.

If you ask the application to remember the password, it is stored in the platform’s own credential store — Secret Service on Linux, Keychain on macOS, Credential Manager on Windows, the Android Keystore on Android. It is never written anywhere else and never leaves the device.

Synchronisation

Synchronisation is off by default. Nothing is sent anywhere unless you enable it and configure it yourself. When it is enabled there are two modes, and you choose which one you use:

• Directly between your own devices on the same network. No server is involved and no account exists. Data goes from one of your devices to another and nowhere else.
• Through a relay server, if you configure one. The relay stores opaque encrypted blobs. Encryption keys are derived on your device from your database password, which is never sent to the server, so the operator of the relay — including us, if you use ours — cannot read your notes, your task titles, your attachments or your time records. To the server, your data is bytes it cannot interpret.

If you register an account on a relay, that server holds the account user name and password you chose for it, and the encrypted blobs your devices upload. It holds nothing else about you.

Voice memos and transcription

Voice memos are recorded on your device and stored inside your encrypted database like any other attachment. Transcription runs on your device, in the application’s own process, using a whisper.cpp model you download once. Audio is never uploaded to a transcription service, and there is no API key because there is no service. Downloading a model is an ordinary file download and carries nothing about you beyond the request itself.

Permissions

The Android build declares exactly three permissions:

• Microphone (RECORD_AUDIO) — requested only when you record a voice memo. The audio goes straight into your encrypted database.
• Internet (INTERNET) — used only to reach a sync server or another of your devices when you have turned sync on, and to download a transcription model if you choose one. With sync off and no model downloaded, nothing uses it.
• Biometrics (USE_BIOMETRIC) — optional, and only if you switch on biometric unlock. The check happens on the device; nothing is transmitted.

Noo does not request location, contacts, calendar, camera, background location or any advertising identifier.

The agent server

Noo can expose your outline to AI coding agents on the same machine over the Model Context Protocol. It is off by default. When switched on it listens on the loopback address 127.0.0.1 only — never on a public interface — is gated by a token you can regenerate, can be limited to read-only, and lets you exclude branches of the tree so agents never see them. No data goes off the machine as a result of switching it on.

Children

Noo is a general-purpose notebook and is not directed at children. It collects no data from anyone, of any age.

Changes

If this policy changes, the date at the top of this page changes with it. As long as the application collects nothing, there is not much here to revise.

Contact

Questions about privacy, or about this policy: info@lab517.io.