Help & FAQ/Import guides
Nextcloud Notes needs no export step: every note is already a plain file in one folder on your own server, and Nextcloud hands you that whole folder as a .zip. Both file extensions it uses are read here, so there is nothing to convert first.
Categories are stored as subfolders, so they arrive as real folders. Note dates come from the files themselves rather than from the import. Headings, tables, task lists, code blocks, footnotes and math survive, and bare URLs become clickable links.
This imports a copy. Nothing is deleted from your Nextcloud and nothing syncs back, so keep the server as your archive until you are happy with what landed here.
Notes writes .txt out of the box and .md when you or your administrator change the setting. Both are read here, along with .markdown, .mdown and .mkd, so you do not have to rename anything or touch the server before you export.
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.