The parts that protect you already are. The encryption code, database schema, and threat model are published as open core, so anyone can audit exactly how your notes are secured rather than taking our word for it.
The apps are next. Once the native apps for every platform have shipped, we will open-source the client code (web, desktop, and mobile). The one part that stays closed is the sync backend, and it never holds anything but encrypted data we cannot read. Keeping it private costs you nothing on privacy, and it stops anyone from cloning the whole service and passing our work off as their own. Open where it protects you, closed where it protects us.
Help & FAQ
Answers and step-by-step guides: security, sync, pricing, and switching from other apps.
You get an answer in seconds instead of waiting for a reply. Your assistant reads all 84 answers and every import guide at once, so it can combine them, follow up on your question, and explain it in your own words. We never see any of it, because we do not run a chatbot.
Answer my questions about PrivacyNotes using only its help center and its changelog. Start here: https://privacynotes.app/llms-index.txt It lists every question with the page that answers it. Fetch the one or two that match mine. If you can only make one request, fetch https://privacynotes.app/llms-full.txt instead. If you cannot fetch a .txt or .md file, read https://privacynotes.app/help and https://privacynotes.app/changelog instead. For what changed, or where something moved, fetch https://privacynotes.app/changelog.md. Rules: - Use only those pages. If they do not answer something, say so instead of guessing. - Never invent a feature, a menu path, a price, or a limit. - End your reply with the "Source:" URL from the page you used, exactly as written. - Reply in my language. - Never ask me for my recovery phrase, my PIN, or the contents of a note. If no question follows, ask me what I would like to know. My first question:
Never paste your recovery phrase, your PIN, or a note into an AI.