Privacy Policy

EEditor is a local editor. It has no server, no account system and no analytics. The short version: we collect nothing, because there is nowhere for anything to go.

What we do not collect

• No analytics, usage statistics or telemetry of any kind.
• No third-party tracking, advertising or attribution SDKs.
• No automatic crash reporting.
• No accounts, sign-in, email addresses or identifiers.
• No access to contacts, location, camera, microphone or photos.
• No copy of your notes, ever, anywhere.

What the app touches on your device

• Your workspace folder. EEditor reads and writes files in the folder you choose, and in folders you explicitly open afterwards. It remembers which folder you last used so it can reopen it.
• Files you open from outside it. If you drag a file in or use Open With, EEditor can read and — if you choose to edit it in place — write that one file. Permission covers the files you hand it, for that session, and nothing else.
• A local database. Agenda items, categories, rules and any tables you create in EELisp are stored in an SQLite file in the application's own data directory on your device. Your notes are not in it.
• Small preferences. The theme you picked and whether the REPL is showing are stored locally.
• PDF exports are written to the location you pick in the system dialog.

Network access — the one exception, and it's yours

EEditor itself makes no network requests. It does not check for updates, phone home, or fetch anything at startup.

The EELisp language, however, includes two functions that can reach the internet: http-get and http-post. They run only when code you write or load calls them — for example, the optional standard-library module that looks up a Bitcoin price, or a script of your own that fetches a page. If you never call them, nothing leaves your machine. If you do call them, the request goes to the address you named, and EEditor is not involved beyond making it.

Platform sandboxing

On iOS and iPadOS, EEditor runs in the standard app sandbox and its workspace is the app's own Documents folder, which you can browse in the Files app.

Desktop builds distributed from this site run as ordinary desktop applications with the file access described above. They are not sandboxed by the operating system, so they are able to read and write the folders you point them at — which is exactly what an editor of local files needs to do, and no more than that.

Children

EEditor is not directed at children and collects no personal information from anyone, regardless of age.

Changes

If this policy changes, the date at the top changes with it. Since the app collects nothing, any change would be about what the app touches, not about data we hold, because we hold none.

Contact

Questions about this policy: roberto@santacroce.xyz.