Privacy
Your words stay yours
GlissNotes is local-first by design. This page explains exactly what leaves your machine, and when.
Local by default
Documents, settings, and the automatic recovery snapshot are stored on your computer. GlissNotes does not include analytics, crash reporting, or telemetry. With sync and AI switched off, the app makes no network requests.
Optional cloud sync
If a build is configured for sync and you choose to sign in, your open documents and editor settings are stored in a Supabase Postgres table scoped to your account. Row-level security ensures only your authenticated session can read or write that row.
- Identity comes from Google, GitHub, Apple, or an email link through Supabase Auth.
- Desktop session tokens are encrypted with the operating system’s secure storage.
- You can sign out everywhere or delete all cloud data from the account panel at any time.
- Local documents remain on your machine after you sign out.
Sync requires the person who builds or hosts GlissNotes to run a Supabase project. The setup is documented in docs/cloud-sync.md.
Optional AI tools
AI features call an OpenAI-compatible endpoint that you configure. GlissNotes sends document content to that endpoint only when you explicitly run an action, and only the text involved in that action.
- Your API key is kept in memory for the current session and is never written to disk.
- The endpoint and model are yours to choose, including self-hosted models.
- The endpoint provider’s own privacy policy applies to the requests you send.
This website
This site is a static marketing page hosted on Vercel. It sets no cookies of its own. Download links point to GitHub, which has its own privacy policy.
Contact
Questions or concerns can be raised on the issue tracker.