Often days. Small requests and bug reports usually land in the next release, and releases go out most weeks rather than a few times a year. The changelog is the record: every entry is dated, written in plain language, and says what changed. Read a month of it and you will know exactly what to expect from us before you commit anything to the app.
That pace comes from how the work is split. The encryption core, the sync protocol and the sign-in flow were written by people, next to day jobs, long before the app had a name, and the crypto core is still maintained that way; nothing automated goes near it. Once that foundation was solid, in spring 2026, we started using AI coding tools under a fixed protocol: first for translations, then help articles, then interface features and non-critical bug fixes, where they are good at pinning down rare edge cases that would otherwise take weeks, and at writing the test scripts that hold several developers to one standard. That is why a request from one person is worth building instead of waiting behind the top of the list.
Anything touching encryption, sync or sign-in stays with skilled developers who write every line, and that code is public so you can read it instead of trusting us. More on the team and how we work on our about page.
The app itself has no AI features and never sends your notes anywhere (details). That promise is separate, and it does not change.
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 88 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, its changelog and its security documentation. 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, https://privacynotes.app/changelog and https://github.com/LifetimeLabsDev/PrivacyNotes.app instead. For what changed, or where something moved, fetch https://privacynotes.app/changelog.md. For how the encryption works, what the server can read, or how to check any of it yourself, fetch https://privacynotes.app/docs/index.md and follow it to one of the documents it lists. That index is a router: cite the document, never the index. 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. - Answer in the same language as my question. - 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.