Last updated: July 2026
Nothing on our servers. All your data (notes, to-dos, calendar, habits, clipboard history, settings) is stored locally on your Mac. It is never uploaded to us and we have no way to read it. There is no account and no analytics/telemetry built into the app.
To offer free updates, Cyanote periodically checks a public release file hosted on GitHub. This request is made directly from your device to GitHub and, like any web request, exposes your IP address and app version to GitHub (see GitHub's privacy statement). It contains none of your personal content. You can ignore update prompts if you prefer.
Payments are processed by Lemon Squeezy, our reseller (Merchant of Record). When you buy Cyanote, Lemon Squeezy collects the information needed to complete the sale (e.g. name, email, billing details, and tax location) under their own privacy policy. We receive only limited order information (such as your email and that a purchase was made) to provide support and deliver your download. We never see your full card details.
Our website is served by a static hosting provider, which may keep standard server logs (such as IP address and browser type) for security and reliability. We also use privacy-friendly, cookieless analytics to count visits and see which pages are read — it sets no cookies, stores no personal data, and cannot follow you to other sites. We don't add advertising trackers.
If you email us, we'll use your message and address only to help you and to keep a record of the conversation.
Because we hold almost no personal data, there is little to request — but you can contact us any time to ask what we have, or to have your support correspondence deleted. For purchase data, you can also contact Lemon Squeezy directly.
Cyanote is not directed at children under 13, and we don't knowingly collect their data.
We'll update this page if our practices change and revise the date above.
Questions? Email support@cyanote.app.
This document is a plain-language starting point, not legal advice. Review it (and fill in the placeholders — domain, email, and any jurisdiction-specific requirements) before publishing.