Privacy Policy — Send to Supernote

What it does: Send to Supernote captures the current web page, converts it to a PDF or EPUB entirely on your device, and uploads it to the Supernote destination you choose the public Supernote Cloud or your own self-hosted Supernote Private Cloud.

What is stored, and where:
- A session token only (a JWT for Private Cloud) is stored in local extension storage on your device. Your password is never stored it is used in memory only to compute the sign-in hash and then discarded. For Supernote Cloud you sign in on Supernote's own page and only the resulting session token is read.
- Local settings (capture mode/format, target, destination folder) and a short local send history are stored locally for convenience and never leave your device except as part of a send you initiate.
- Nothing is stored in synced storage.

Where your data goes:
- Page content is converted locally (no server-side rendering) and uploaded only to the destination you choose: Supernote Cloud (cloud.supernote.com / viewer.supernote.com and Ratta's Amazon S3 storage via a pre-signed URL issued by Supernote's own API), or your own Private Cloud server.
- No third-party providers (no Dropbox/Google Drive/OneDrive). No server operated by this project is in the path. No third-party OAuth. No telemetry, analytics, or remote logging.

Permissions: Each permission maps one-to-one to a feature. The extension requests no debugger, no identity, and no <all_urls> host access.

Your control: Disconnect at any time to remove the stored token; uninstalling removes all locally stored data.

Contact: https://github.com/j-raghavan/send-to-supernote/issues
Full policy: https://github.com/j-raghavan/send-to-supernote/blob/master/docs/PRIVACY.md