> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/using-oisy-wallet/notes.md). # Notes Notes let you keep short, private pieces of text alongside your wallet — a PIN reminder, a note about who an address belongs to, anything you want close at hand. Notes aren't attached to any transaction, address, or token; they're just yours. #### What are Personal Notes A note is a simple block of free-text, up to 2,000 characters. There's no separate title field — the first line of what you write is shown in bold as the note's title in your list, purely for display. Notes support any language, script, or emoji, and any http/https links you paste into a note become clickable when you view it. All your notes live together in one simple, searchable list, for as long as you want to keep them. #### Keeping Your Notes Private Your notes are private by default: no one but you can read them — not OISY, not the systems running the wallet, and not other users. They're scrambled the moment they leave your device, and only unscrambled again on your device when you open them, so what you actually wrote never travels anywhere in a readable form. Because your notes only exist in readable form on your own device, searching them works the same way — there's no way for anyone to search what your notes say from outside your device. #### Where to Find Notes in OISY Notes live in your user menu, right after Contacts. Opening it shows your list of notes, newest or most recently edited first, with a search field to filter them and an "Add note" button. **Add, View, Edit, and Delete a Note** Tapping "Add note" opens a plain text box — write what you want, then save. Tapping an existing note opens it read-only; from there you can edit it (which reopens the same text box, pre-filled) or delete it. Deleting asks for confirmation first, since it can't be undone. You can hold up to 1,000 notes at a time; past that, you'll need to delete one before adding another. #### Sharing a Note Any note you've successfully opened can be shared: a quiet "Share note" link on the note's view screen starts the process. Sharing creates a one-time public link that lets someone read that note's text — even if they don't have an OISY account and never sign in. When you create a share link, you choose how long it stays valid (1 hour, 24 hours, 7 days, or 30 days — there's no permanent option), and you can optionally make it self-destruct after it's opened once. Once you have the link, copy and send it however you like; OISY doesn't send it for you. A shared link is a snapshot: it captures the note's text at the moment you create the link. Editing or deleting the original note afterward has no effect on a link you've already shared — and importantly, **once a link is created, OISY can't recover or revoke it.** Anyone who has the link can read the note until it expires or is used up, so treat the link itself the way you'd treat the note's contents. **What the Recipient Sees** Opening a shared link shows a simple "A note was shared with you" screen with a single "Reveal note" button — nothing loads until that's clicked, which also protects single-use links from being burned by link-preview bots. Once revealed, the recipient sees only the note's text: no sender name, no timestamps, nothing identifying who shared it or when. If the link is single-use, the page tells the recipient to copy the note before closing or reloading, since it won't be retrievable again. An expired, already-used, or invalid link shows the same generic "This link has expired or already been used" message, regardless of which of those actually happened. #### Limits to Know About Each note can hold up to 2,000 characters, and you can keep up to 1,000 notes on your account at a time. If you reach that count, you'll need to delete an existing note before you can add a new one. #### Technical Details *For anyone who wants the underlying mechanics.* **Encryption Model** Notes use [vetKeys](https://internetcomputer.org/docs/building-apps/network-features/vetkeys/introduction), an Internet Computer primitive for threshold-derived, per-user encryption keys (vetKD). Each user's key is derived on demand from their identity and cached locally as a non-extractable browser key, so it only needs to be fetched once per device. Notes are stored in the canister via the vetKeys `EncryptedMaps` primitive, keyed by an opaque note ID — the canister and the node providers behind it only ever see ciphertext, never note contents. **Sharing Security Model** Sharing uses a second, independent encryption path, separate from your personal vetKeys key: creating a share generates a fresh, random AES-GCM-256 key entirely in your browser. That key is never sent to the canister — it lives only in the link itself, after the `#` fragment, which browsers never transmit to a server. The link's public part is an unrelated random token; the canister stores only the ciphertext, its expiry, its single-use flag, and basic access timing against that token — never the plaintext, never which note it came from, and never the recipient's identity. The principal who created the share is recorded only to enforce the per-user cap on active shares, and isn't exposed through any read path. This means the canister can observe that a share exists, roughly how large it is, when it expires, and when it's accessed — but not what it says. It also means there is no mechanism for OISY to reconstruct or invalidate a share link after the fact: possession of the full link (including the fragment) is the only thing that grants access, by design. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.oisy.com/using-oisy-wallet/notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.