Security

How to report a problem,
and what we already do.

A short page for people who want to check ClearNote, or tell us what is wrong with it.

Reporting a problem

Email support@clearnote.app with the subject “Security report”. A person reads it. The same contact is in /.well-known/security.txt.

Useful to include: what you found, the steps to reproduce it, the version of the app or the URL involved, and what you think the impact is. Please:

Use accounts you own. Do not read, change or delete anybody else’s notes.
Do not run anything that degrades the service for other people — no load testing, no spam through the AI relay or the access-request form.
Give us a reasonable chance to fix it before you publish.

ClearNote does not run a bounty programme.

Checking the Mac download

The Mac app is signed with Developer ID Application: Jeff Moncrief (PL2JF9SKMQ), built with the hardened runtime and the App Sandbox, and notarized by Apple. The download page lists the exact SHA-256 and the three commands that confirm the file you have is the file we published. The app’s own updater applies the same rule: it only follows download links on clearnote.app, and it checks the size and SHA-256 in the update feed before it offers the file to you.

What the site does

HTTPS only, with HSTS. Every response carries a content security policy that allows scripts, styles, images and fonts from clearnote.app and nowhere else, and forbids framing, plugins and inline script.
No third-party scripts, fonts, analytics, advertising or tracking — not on these pages and not in the web app.
No cookies on the marketing pages. The web app’s one lasting cookie is your session, marked HttpOnly.
Sign-in is Google’s. ClearNote never sees or stores a password.

What the service does

Notes, tasks and attachments are sealed with AES-256-GCM before they are stored, with the account bound into each ciphertext. This is encryption at rest. It is not end-to-end encryption, and we do not call it that — the privacy page is explicit about what it does and does not protect against.
Share links are unguessable 256-bit tokens, can be revoked at any time, and are kept out of the web server’s access log.
The AI features are off until you turn them on, and send only the passages relevant to the question you ask.
Requests are rate-limited, and sign-in and the AI relay are limited much more tightly than the rest.

Machine-readable