Edge / Privacy

Your data in Edge

Edge stores the searches your agent sends, to make Edge better. Here is all of it, in one table.

What Edge receives, stores, never receives, who else sees it, and how to delete it
What Edge receives	When your agent searches: your request as you wrote it (up to 300 characters, after the filters below) and optional keywords your agent adds (up to 120). Edge searches with your own words so it finds the skill for what you actually asked, not a paraphrase. Names of companies or products in your request can reach Edge. With it: a random install ID (the remote connector sends a session ID instead, and the Claude Code plugin also sends the install ID once Edge setup has created one), your Pro key if you use one, and the app name and version. In ChatGPT, Edge also gets ChatGPT’s anonymous user ID and keeps only a one-way hash of it as your install ID, so your conversations count as one person, keep your referral code and are deleted together. A referral code on your setup link (`?ref=`, a public creator or partner code) is kept with your install ID or session ID, and to match the link to your install Edge stores a hash of your network address whose key it deletes after two days, so the address cannot be recovered. Two daily signals from local Edge. The connector that runs on your computer (the npm package) sends “ready” once on each UTC day it starts and is ready for your agent, and “nudged” once on a day its prompt hook suggested an Edge search. Each has only your install ID, the date, the app name and version, and the connector version and type: no task text, prompt, skill name, key, count or time spent. They show whether Edge was running on days it was not used, so we can find out why people stop using it. Set `EDGE_TELEMETRY=0` to turn both off. When your agent loads or rates a skill: the skill name and, for a rating, the outcome, a 0 to 10 score and an optional note of up to 280 characters. An issue report adds its message and, only if you give one, a contact email. The npm connector removes emails, links, file paths, keys and phone numbers it finds on your computer, before anything is sent. The hosted connector (Claude app, ChatGPT, the Claude Code plugin) does the same on Edge’s server before anything is stored, and the server repeats it for npm searches too. Filters can miss things, so leave out what you would not want stored: names of people or candidates, client details, and anything confidential.
What Edge stores, and for how long	Search text: no scheduled expiry. Each search is kept with its keywords, your install ID or session ID, which skills were shown and loaded, and your rating. It stays in the service’s daily files for 31 days and in a compressed archive with no end date. The search text is stored encrypted (AES-256-GCM). Ratings, notes, issue reports and daily signals: no scheduled expiry. A Pro key is stored as a label (the start of its hash), never the key itself. Backups are encrypted: daily copies of recent records are kept 31 days, and an offsite copy of the archive has no end date. We keep this to improve Edge: which searches find a good skill, and which skills help.
What Edge never receives	Your files, your code, your conversation or your session logs. Edge only sees what your agent writes into the search. Your installed skills, unless you turn on ranking them. Then only their names and short descriptions.
Who else sees it	TypeSafe (api.typesafe.ai) ranks results. It gets the task description and the candidate skill descriptions, with no install ID, session or key. If you turn on ranking your installed skills, that includes their names and short descriptions. Cloudflare carries the connection. The web server log keeps IP address, time, the address requested and browser type for 60 days. Search text is not in it: it travels in the request body. On this website, PostHog analytics and session replays run only after you press Allow. Typed text is never recorded.
How to delete	Run `npx -y @getedge/mcp@0.6.14 forget` in a terminal. It deletes this install’s searches, loads, ratings, reports, daily signals and referral code from Edge’s service and its archive, and prints how many of each it removed. With `EDGE_KEY` set, it deletes everything stored under that Pro key too. In ChatGPT, ask your agent to delete your Edge data. It deletes the same records for your ChatGPT install ID. Daily backups expire within 31 days, and the command prints the date. The offsite copy of the archive is replaced within a day. A deletion record keeps only one-way hashes, so a restore from backup deletes your data again. Or email fede@getedge.cc with your install ID (in `~/.config/edge/install-id`), or for the remote connector the session ID if you have it. We delete it within 30 days. Uninstalling Edge stops new records but deletes nothing on the server.

One stored search

This is what Edge keeps for one search. The task is an illustration, not a real user’s search. The values in angle brackets stand for the real identifiers. The record also carries timing and ranking counters.

{
  "at": "2026-10-03T09:14:22.512Z",
  "event": "find",
  "queryText": "SVG candlestick chart component in React, no charting library",
  "keywordsText": "svg candlestick chart react",
  "queryHash": "<16 hex characters>",
  "queryLength": 62,
  "install": "<your random install ID>",
  "session": "<random session ID>",
  "client": "claude-code/2.1.4",
  "version": "0.6.14",
  "pro": false,
  "requestId": "<random request ID>",
  "presentedSkills": ["<owner/repo@skill>", "<owner/repo@skill>", "<owner/repo@skill>"],
  "ranker": "jev",
  "ms": 1840
}

A load adds a record with the skill name and the same request ID. A rating adds the outcome, the score and the optional note.

A daily signal is smaller. This is a “ready” one; a “nudged” one has nudge_fired_day as its event and the same fields:

{
  "at": "2026-10-07T08:02:11.904Z",
  "event": "connector_ready_day",
  "day": "2026-10-07",
  "install": "<your random install ID>",
  "client": "claude-code/2.1.4",
  "version": "<connector version>",
  "connectorTransport": "npm_stdio"
}

This website

Without your choice, getedge.cc sends PostHog a cookieless count of page views and key clicks, with no identifier stored in your browser. Press Allow and it also sends page events and a session replay; typed text is masked before anything leaves the browser. You can change this any time under Privacy choices in the footer.

Each page also tells Edge’s own server that it was opened, the setup page which app tab you pick, and any page when you copy the setup line or a setup command. Each record has the page, a random ID that exists only while that page is open, the referral code of the link you came from if it had one, and, while a page is being tested in two versions, which version you saw. Edge’s server adds a hash of your network address and one of your network address with your browser type, under a key it deletes after two days, so neither can be traced back afterwards, and a flag when the browser is automated; the address and browser type themselves are not stored. No cookie or stored identifier is used (the web server log above still applies). The records have no scheduled expiry. The setup line you copy ends its referral code with the first eight characters of that page’s random ID (for example --t3f9a0c1d), and, while a page is being tested, with the version letter before it (for example --vb--t3f9a0c1d); nothing else is added. When you set Edge up with that line, Edge’s server stores this short ID apart from the referral code, with the install’s other records, and sends it with the install’s usage events to PostHog, where it is joined to that one page visit’s analytics event for the copy. It identifies the page visit, not you, and is never stored in your browser. Deleting an install’s data deletes it too.

Global Privacy Control turns all of this off. Edge does not sell personal information.

Questions and requests

Email fede@getedge.cc to ask what we hold, to correct it or to delete it. Edge is published by Floom, Inc. More detail for developers: the full data flow.

Updated 7 October 2026.