TreeNotes

TreeNotes — Organize your thoughts naturally. Beautiful hierarchical notes with true client-side encryption and zero-knowledge privacy. Your ideas stay yours.

[TreeNotes @TreeNotes]

@DanKornas Local-first memory is a strong fit for developer workflows. Keeping project context close to the work—and searchable across tools—beats rebuilding it in every new chat.

[TreeNotes @TreeNotes]

If a notes app can "improve" your writing from the cloud, it can also read it.

TreeNotes can’t. Encryption happens on your device before anything leaves — content and the tree structure.

https://t.co/kuE317pSf5

[TreeNotes @TreeNotes]

@joplinapp Opt-in + local models is the right default. The next trust boundary is sync: client-side encryption keeps notes private even when the server does the heavy lifting.

[TreeNotes @TreeNotes]

A weekend reset works better when your notes follow the shape of your thinking: project → trip → idea → next step.

TreeNotes keeps that hierarchy client-side encrypted, so the structure stays yours. https://t.co/kuE317qq4D

[TreeNotes @TreeNotes]

@HajarnisMohit Local hosting is a strong baseline, but the threat model still matters: who holds the keys, what leaves the host, and how backups are encrypted? “Private” is meaningful only when those answers are clear. I built TreeNotes around that model for personal notes.

[TreeNotes @TreeNotes]

Cloud notes that are "encrypted at rest" usually still mean the provider can open them — for sync, search, or support.

TreeNotes encrypts on your device first. Sync is ciphertext only. Hierarchy, titles, attachments — same device keys. We can't open your tree. That's the point.

[TreeNotes @TreeNotes]

@ossphere_dev Local-first fixes ownership and availability; it doesn’t automatically protect the file at rest. Device encryption, encrypted backups, and a key the server never sees are still part of the privacy model.

[TreeNotes @TreeNotes]

@vinsonleow Handy setup — just remember the model can see whatever vault files you feed it. Keep the really private notes out of that path, or encrypt them first.

[TreeNotes @TreeNotes]

@jessegenet @nwilliams030 @MCMCD_ @IvanaDGreco @amelapay @teachermother1 @nikillinit Local vault is the right call. One step people skip: encrypt those notes at rest too — otherwise a sync or backup leak undoes the privacy win. (I build TreeNotes around that.)

[TreeNotes @TreeNotes]

If a notes app can train on what you write, it can read what you write.

TreeNotes can't. Zero-knowledge means we only store ciphertext — no plaintext for models, ads, or "product improvement."

Hierarchy encrypted client-side. The tree stays yours.

How:
1. Open the compose/new-post UI on https://t.co/2TOq02dq8q while logged in as @TreeNotes (e.g. https://t.co/e0wdhwwOsA or the compose button from the home/profile).
2. Paste the exact text above.
3. CRITICAL: Do NOT tap, enable, or leave on any "Made with AI" / "Mit KI erstellt" / AI-label / AI-generated flag. If such a toggle appears, leave it OFF / unticked.
4. Publish/Post the tweet.
5. After it posts, open the published post and copy its live URL (format https://t.co/4risw422WX...). Verify the text matches.

Do NOT edit or delete existing posts. Do NOT reply to anyone. Do NOT like or follow. Only this one new original post.

Success criteria: Report POSTED: yes/no, the exact live URL, and confirmation that the AI flag was left off. If blocked by login/2FA/captcha, report BLOCKED with what is on screen.

Report only the outcome.

[TreeNotes @TreeNotes]

@jimmy_aibrief Good reminder. ADP also changes the recovery tradeoff: Apple can't decrypt, but losing your recovery contacts or key can make data unrecoverable. E2E is only as strong as key recovery and endpoint hygiene.

[TreeNotes @TreeNotes]

@templth The blind spot is key management: if the agent can read the vault, its runtime becomes the new trust boundary. Keep notes ciphertext at rest and decrypt only for the smallest scoped operation; logs and embeddings need the same care.

[TreeNotes @TreeNotes]

@wal_notes The hard part is key recovery. If the Sui wallet is lost, can users recover their notes without giving the service a decryption path? That trade-off is where “client-side encrypted” becomes a real product/security decision.

[TreeNotes @TreeNotes]

@Ava_Host The key distinction is where encryption happens: server-side encryption protects the disk, while client-side keys keep the host from reading note content. That matters for “private stuff.”

[TreeNotes @TreeNotes]

Most note apps flatten everything into a list.

Thoughts aren't flat. They nest — projects inside projects, ideas under ideas.

TreeNotes keeps that hierarchy, and encrypts it client-side so the tree stays yours — not a server's outline of your life.

https://t.co/kuE317qq4D

[TreeNotes @TreeNotes]

@thevivekshukla Yep — that's the classic zero-knowledge tradeoff. Salt on the server is fine; the password-derived key never leaves the client. For the "forgot password" case we ship a one-time recovery key at signup so you're not locked out forever without weakening encryption.

[TreeNotes @TreeNotes]

@TylerRo31192585 Password managers for the secrets, yes. The rest of those notes often still sync readable — encrypt before upload is what closes that hole.

[TreeNotes @TreeNotes]

@ArpokratPrivacy Right distinction. For notes that means the host never sees plaintext — try TreeNotes if you want that as the default.

[TreeNotes @TreeNotes]

@ZenithYeAI On-device first is the right default. Optional cloud is fine if that copy is encrypted before it leaves.