Effective July 2026
Knogra does not collect, store, or transmit your personal data. Everything you create stays in your browser.
All graph data is stored locally in your browser using IndexedDB. Your graphs, notes, and settings are never sent to Knogra — there is no backend database storing your content.
You can export your data at any time from the app. You own everything you create.
The landing page (knogra.io) uses Vercel Web Analytics. This collects anonymous, aggregate data — page views and referrers. No personal data, no cookies, no fingerprinting.
The app (app.knogra.io) uses no third-party analytics. It sends anonymous, aggregate usage counts — how many times the app is opened, and how many workspaces are imported or exported — to a first-party Knogra endpoint. These are simple tallies: no personal data, no cookies, and no per-user or per-session identity, so they can never be tied back to you or your graphs.
The demo-library “like” buttons store an anonymous count per graph on a first-party Knogra endpoint. These are aggregate tallies only — no personal data and no per-user identity.
If you use AI features, you supply your own API key. Knogra supports the Google Gemini API and OpenRouter (which routes requests to a range of AI models). Requests are sent directly from your browser to Google or OpenRouter. Knogra never receives or processes these requests. The privacy policies of Google and OpenRouter apply to any data sent during those calls.
Knogra does not use tracking cookies. The app uses browser localStorage and IndexedDB to store your settings and graph data locally.
The landing page uses localStorage to remember which demo graphs you’ve liked, so you don’t double-count — this never leaves your browser and is not used for tracking.
The only third-party service on the landing page is Vercel Web Analytics. The app uses no third-party tracking or analytics services. No advertising networks, no social tracking pixels.
Questions? Email contact@knogra.io.