short, because there isn't much to say
An editable database is sensitive by nature: customer lists mid-correction, lab catalogs mid-cleanup, exports mid-migration. editsqlite is built so that data never has to leave your machine, and this page spells out exactly why.
Where your data goes, in full: your file → tab memory (the working copy) → your screen → your downloads folder (exports) and your browser's own local storage (the autosaved session, size-capped, on your device). The site is nothing but static files; there is no upload endpoint in the code, so there is no server to make promises about. Airplane mode is the acceptance test — everything keeps working with the network off.
About the autosave: sessions are kept in localStorage so a closed tab doesn't cost you an afternoon of corrections. That storage sits on your device, is readable only by this site, and is cleared by you — closing a file writes one final snapshot, and your browser's site-data controls erase it completely. Databases past a couple of megabytes skip autosave rather than strain it; that's stated here, not left for you to discover.
What we don't load: no analytics package, no advertising scripts, no tracking cookies, no account system — none of it is in the build. The two typefaces arrive from Google Fonts on first visit and then cache. Cloudflare, which serves the static files, keeps a plain visitor count; the contents of anyone's working copy stay invisible to everyone but the person editing.
questions → Contact · reviewed 5 july 2026