Privacy first · local first
Privacy by architecture
Elasticnote separates private notebook content from optional online services. Local notes stay in browser storage or a folder you connect unless you deliberately use a feature that needs data elsewhere.
Notes stay local by default
Browser notebooks and an optional Notebooks Folder are the normal working copies.
Online features are explicit
Hosted features receive data only when you invoke those features.
AI is your choice
Use no AI, supported Local AI/Ollama, or a configured BYOK/cloud provider. A failed local model does not silently fall back to cloud.
Analytics are separate
Elasticnote uses limited Statcounter analytics on public website pages. Private notebook contents, filenames and AI prompts are not analytics payloads.
Privacy
Elasticnote is local first. Project files, compiled PDFs, Paper Memory documents and vectors, datasets, Git credentials, local AI models, vendor AI keys and filesystem handles are not automatically uploaded to the Elasticnote account service. TexLab is an explicit authenticated server feature: only files you choose to send enter its isolated temporary session workspace, and generated files are available for authenticated download until session cleanup. Account features may store safe profile, entitlement, support, preferences and operational usage. Normal local project names, slugs, modes, inventory and filesystem handles are not stored as account project metadata; explicit online features may retain only the records needed for that feature.
Cookies and analytics
On non-admin production pages, Elasticnote uses Statcounter for basic website analytics regardless of the optional-cookie choice. If a Google Analytics / Google Tag ID is configured by the Elasticnote operator, Google analytics is loaded only after you select Accept cookies. Selecting Decline cookies keeps Google analytics disabled. Elasticnote stores the optional-cookie preference in your browser using local storage so the notice does not need to reappear on every visit.