Security

Clear permission rules and honest boundaries

Esha runs locally on your own computer. She works inside strict boundaries for safe tasks and waits for your explicit confirmation before anything irreversible.

Data flow

What leaves your laptop and what does not

Stays on your laptop

Local

Personal folders, Word documents, spreadsheets, and slide decks.
Task checkpoints and execution logs in local SQLite storage.
API keys and configuration credentials kept inside your local .env file.
Generated exports and backups written inside permitted directories.

Sent externally only when required

Explicit

Task prompt text or short snippets sent to the configured AI model provider for reasoning.
Status replies, approval prompts, and finished files sent back to your Telegram chat.
Public web page fetches when you ask for online research or a site check.
Outbound emails or posts only after your direct confirmation.

Controls

Permission levels, approvals, and secrets

Five permission levels

Every action is sorted into one of five tiers before running: Read (auto), Write in workspace (auto), Run code in a sandbox (auto), Send or post (you approve), and Delete or overwrite (you approve).

Telegram approvals before external risk

External messages, uploads, or destructive file edits pause cleanly until you tap approve in Telegram. The interactive Telegram approval runner is currently in build alongside the v3 task engine.

Secrets handling and redaction

Runtime keys live only inside local environment configuration and never ship inside logs, Telegram alerts, or website builds. Structured log redaction filters tokens and credentials automatically before storage or display.

Current stage disclosure

Esha is a personal project in active build. Independent security audits, enterprise cloud key vaults, and multi-user authentication are not part of the current local-first version.