About Evergist

Updated ยท Markdown

Evergist is a free web app, CLI, and local MCP server for sharing text through end-to-end encrypted links that expire or burn after reading.

Why it exists

AI agents and scripts hand off secrets all day, and the quickest way to do it is to paste the secret into a chat, a ticket, or a pull request, where it stays. We wanted a handoff that takes one command or one MCP tool call, encrypts on the machine that runs it, and leaves our server holding only ciphertext. People get the same kind of link from the form on the homepage. Why we built Evergist has the longer version.

What it costs

Nothing. Evergist is free, with no accounts and no sign-up. Storing a few kilobytes of ciphertext for a few days costs very little, and there are no ads and no analytics to pay for.

Where it runs

Evergist runs on Cloudflare. One Worker serves the site and the API, and each note lives in its own Durable Object that wipes itself at expiry or after the last allowed view. Cloudflare handles your IP address to route the connection, as any host does. It never receives the key or your text, and a password typed into the password field stays on your device. A password put in the link as ?password= does reach the host, so send it separately and type it in. What Cloudflare can see spells out the rest.

What we don't collect

  • IP addresses, in storage or in logs. Request logging is off.
  • Cookies. The site sets none.
  • Analytics. There are no tracking scripts and no requests to other domains.
  • Anything that links a note to a person. There are no accounts and no creator field.

We keep three counters per day: page loads, notes created, and notes read. Their totals are public on the stats page. The privacy policy lists everything we store.

What you can inspect

The full source isn't public yet. These parts are, and they are enough to check the claims on this site:

How to reach us

Email contact@evergist.com for questions, corrections, and abuse reports.

Security reports go to the same address. Our security.txt names it as the contact, and the vulnerability reporting policy says what to expect.