Eisengrid

Privacy

Eisengrid stores account details, workspaces, projects, tasks, tags, attachment metadata, uploaded attachments, API tokens as hashes, sessions, and billing/subscription state needed to run the service.

Uploaded attachments are stored on the server filesystem and are included in operational backups. Account deletion removes local task data and queues attachment cleanup.

Private Vault is optional browser-side encryption for task titles, descriptions, comment bodies and mentions, tags, project and workspace names, attachment names, and attachment files. When enabled, that private content is encrypted before it is stored, backed up, exported by the server, shown to support impersonation, or returned to normal API tokens.

Private Vault still leaves operational metadata visible so the app can run: due dates, priority, effort, status, recurrence rules, timestamps, IDs, counts, file sizes, billing, and abuse-prevention signals. Reminder emails become generic, support cannot read private content, and local agents need an explicit local Private Vault bundle to decrypt or write ciphertext.

Eisengrid cannot recover Private Vault content if you lose both your vault passphrase and recovery key. Like any browser-based encrypted app, Private Vault requires trusting the app code delivered to your browser when you unlock and does not protect against device malware, compromised browser extensions, or same-origin XSS while unlocked.

Feedback messages and feedback attachments are emailed to the site admin for support and bug triage.

Payment processing is handled by LemonSqueezy. Email delivery is handled by Resend. Basic product analytics may be handled by PostHog when configured.

For privacy or data deletion questions, contact [email protected].