Private by default, clear about the rest

SILONotes keeps your writing on your device. AI is optional, and you always decide what leaves the page. Here is exactly how it works.

Last updated 15 September 2026

The app, by default

Notes, audio, images, library books, and settings live in a plain database on your device.
No account is required to write, record, or read.
Nothing is uploaded in the background.
No analytics kits and no marketing trackers are in the app.
Backups are files you create and keep wherever you choose.

There is no SILONotes server

We do not run a model, a proxy, or a relay your writing passes through.
Every AI request goes from your device to the destination you configured, and nowhere else.
There is nothing for us to see, even if we wanted to.
There is no hosted plan to buy, and no feature is waiting behind one.

When you turn on AI

AI is entirely optional, and the app is complete without it.
Point at a model on your own machine, through Ollama, LM Studio, vLLM or llama.cpp, and nothing leaves the machine at all: the question, the notes and the answer never touch a network.
Or use a provider you already have an account with and already trust. It is your endpoint, your key, and your relationship with whoever is on the other end.
Only the text for that one run is sent. Your library is never uploaded, indexed elsewhere, or copied.
A token count and a context inspector show you what was sent.

What SILO Sam sends, and what it does not

Sam does not upload your library. The searching and the reading happen on your device, against the same local database your notes already live in.
Nothing is sent anywhere in order for Sam to find something.
Only the notes Sam actually opened travel with your question, and it opens at most five.
The trace line under every answer names what it searched and how many notes it read, so the boundary is printed under the answer rather than promised on a page.

One thing does work differently here, and it is worth being plain about. Everywhere else in SILONotes you pick the notes yourself, so you know exactly what will be sent before you send it. With Sam you ask a question and Sam chooses which notes to open, up to five of them, then sends those along with your question to your model. That is a delegation of selection and nothing else. It is still your device, still bounded at five notes, still your endpoint, and the trace line tells you afterwards exactly which ones it opened. If you would rather choose them yourself, the other chat modes still work that way.

When you turn on web search

Web search is off until you turn it on and choose one of three doors.
Your own SearXNG instance: the query goes only to a server you run.
Your own Brave Search key: the query goes to Brave, under your key.
Your model provider’s search: the query goes to that provider and its search partner.
Results appear under their own heading and are never mixed into what your notes say.

Syncing between your devices

Sync runs device to device through a folder you choose. There is no SILONotes server in the middle and no account.
What gets written into that folder is an encrypted archive, not loose notes.
If you point that folder at a cloud drive, that drive holds the archive under its own terms. That is your choice to make, and we would rather you made it knowingly.
Nothing syncs until you set this up.

Dictation and reading aloud

The built-in voice runs on the device, with nothing sent anywhere.
If you connect a speech server, the audio or text for that one request goes to the server you chose.
A speech server that stops answering is given fifteen seconds, and then SILONotes says so and reads on in the device voice.

Who runs this, and how to reach us

SILONotes is published by SILO Apps LLC.
The waitlist stores only the email address you enter, in a private database.
Your email is never sold or shared.
The waitlist is the only cloud touch on this marketing site.

For anything about this policy, or about your data, write to support@silonotes.app.