User guide · Software preview
Privacy
There is no Maisnie cloud
Maisnie runs entirely on hardware you control. There is no server operated by Maisnie that your notes, your mail, your calendar, or your questions pass through. The only network calls Maisnie makes on your behalf are the ones you explicitly set up: fetching a calendar feed, a mailbox, or the RSS/Atom feeds you follow, making the one live-test call when you press “Save and test,” and calling whichever model door you configured. Nothing about using Maisnie requires creating an account with Maisnie itself.
What Maisnie stores, and where
| What | Where |
|---|---|
| Your notes (from every source you’ve connected, plus anything else you keep there) | Your vault — a plain folder of Markdown files, at the location you chose during vault setup. |
| Configuration (which sources are on, which AI connection is chosen, bind addresses) | One document, config/majordomo.json, inside your data directory. |
| Secrets (a private calendar link, a mail app password, a model provider’s API key) | The same configuration document, in plain text (see security). |
| Per-source sync state (what’s already been fetched, so a re-run doesn’t refetch everything) | Your data directory, under a folder named for that source. |
| The search index | Your data directory, built from the same files your vault already holds — deleting it and letting Maisnie rebuild it loses nothing, since it’s derived, not a second copy of your notes. |
| Model usage records (which connection handled a call, how long it took, what it cost) | Your data directory, one file per month, one line appended per call. Never the content of a prompt or a reply — see the next section. |
| Logs | Your data directory, one file per component. |
All of it is on the disk you told Maisnie to use. Nothing here is uploaded, synced to a Maisnie-run service, or shared with Maisnie’s maintainers as part of using the product.
What Maisnie never records
Whichever model door you use, Maisnie’s own usage records never include the text of your prompt or the model’s reply, and never include the value of a secret (an API key, a password, a calendar link) — only that a call happened, which connection and tier handled it, how long it took, and what it cost. This is a hard rule in the code that writes those records, not a policy that depends on remembering to redact something after the fact.
What a connected provider sees
This is different from what Maisnie itself stores, and it depends on which door you chose in
choose a model — see security for the
specifics per door. In short: with the local door, nothing leaves your machine only if the
endpoint you typed is on this machine (127.0.0.1/localhost) — Maisnie does not check this,
it accepts any http:// or https:// address there, so pointing that door at another device
sends your prompt across your network just like any other door would; every other door always
sends your prompt (and whatever vault text Maisnie included with it) to that provider, under
that provider’s own terms, which Maisnie can’t override or see behind.
Turning things off
Every source is an independent toggle, and turning one off stops it from running without
deleting anything it already wrote — see turn on sources.
An AI connection can be removed from the wizard itself: press Change on it from the “Connect
an AI” page, then Remove this connection?, which deletes its details and any key from this
computer (Keep it backs out instead). You can also edit the configuration document by hand —
delete its entry under llm.lanes and its id from llm.tiers — if you’d rather do it that way.
Notes and past sync results are unaffected either way.