Only the data the service needs.

Content and metadata

Current Note Colab clients encrypt stored Markdown, titles, and supported images before upload. The hosted service stores that ciphertext. The service can see operational metadata such as share and room identifiers, access modes, timestamps, expiry, storage sizes, collaborator identifiers, image filenames, and MIME types.

Live collaboration text and collaborator state are visible to the relay while a room is active. Older share records may contain a plaintext title until an owner opens or updates them with a current client.

Accounts and credentials

The plugin can create an identity without an email address. The service stores a one-way hash of the plugin API key and the public half of the identity key pair. If you choose a public username, it is visible to the service and to people sharing an authorized room with you.

If you configure web access, the service stores a password hash, vault-key derivation salt, and hashes of independent browser-session credentials. The browser keeps its raw credential locally and the derived vault key for the tab session.

If the hosted service offers provider sign-in, it stores the provider name and stable public subject identifier linked to your Note Colab account. It does not use an email address as account identity and does not retain the provider access token. Provider sign-in authenticates the account but cannot derive your vault key or recover a plugin encryption key.

Service operation

Request data needed to run and protect the service may include IP addresses, timestamps, response status, and rate-limit state. Note Colab does not add advertising or product analytics telemetry to the plugin.

Data remains until it is deleted by the relevant product action, expires under a configured share policy, or ages out of service backups. Revoking a share disables server access but cannot delete copies already made by a recipient.

Your choices

• Use link expiry and revoke links that are no longer needed.
• Leave the public username blank if you do not want a recognizable name shown to collaborators.
• Use a compatible server you trust instead of the hosted service.
• Do not share complete note links, API keys, or recovery material with unintended recipients.