Skip to content

Data and privacy

The short version: items are team memory and visible to the whole organization; raw turns are evidence, private, and expire; credentials are masked on your machine before anything is sent. The binding text is the privacy policy.

Data Contents
Account Email and name from the sign-in provider (Google, Microsoft, or an email code through WorkOS), organization memberships and roles.
Raw turns The prompts you send to a connected agent and its replies, the repository and branch, the agent’s name, and the file paths it touched. Tool output is not stored.
Items The notes agents and people write: kind, title, body, and provenance (user, agent, time).
Presence Agent name, branch and touched paths while an agent is active; expires after 5 minutes.
Billing On Team, the Stripe customer and subscription ids, plan, seat count and status. Card details stay with Stripe.
Operational logs Request logs with IP address, user agent and timing, kept by the hosting provider for up to 7 days.
  • Items are visible to every member of the organization and are loaded into every connected session for that repository.
  • Raw turns are not shown in the console or returned by any API route today. They are stored for the retention period and then deleted.
  • Live activity (agent name, branch, file paths) is visible to every member while the agent is active.
  • Nothing is sold and nothing is used to train models. Staff read production data only to fix a problem you reported or to investigate abuse.
  • Raw turns: 7 days on Free, 30 days on Team.
  • Items: until someone in the organization retracts them or the organization is deleted. Retracted items stay visible under “show retracted” in the console.
  • Account and organization records: until the organization is deleted.

Before a turn or an item leaves your machine, the client replaces credentials it recognizes with [REDACTED:<kind>]:

  • key prefixes: AWS (AKIA…, ASIA…), GitHub (ghp_…, github_pat_…), Slack (xox…), Stripe (sk_live_…, rk_test_…, whsec_…), Google (AIza…), sk-… API keys;
  • JWTs and Meshpoint’s own tokens;
  • -----BEGIN … PRIVATE KEY----- blocks;
  • passwords inside URLs (postgres://app:[REDACTED:url-password]@host), Authorization: Bearer … headers;
  • values assigned to names containing api key, secret, token, password, passwd, pwd, private key, access key or credential, when the value is 8 or more characters with no spaces.

Git SHAs, short values and prose such as “the password field is required” pass through. The masking runs twice: in the hook before the turn is written to the local spool file, and again in the SDK before any request. The platform never sees the original.

Treat this as a safety net, not a guarantee. A bare random string with no name beside it is not recognized; entropy-based detection was left out because it also masks commit hashes and wrecks recall. If a secret does get captured, retract the item or let the turn expire, and rotate the secret.

  • Everything, as a copy: an owner or admin clicks Export data on the Org page. One JSON file with the organization, members, pending invites, projects, every item (retracted ones flagged) and checkpoints. Raw turns are not included; they expire on their own.
  • An item: retract it from the console or with meshpoint items retract <id>. Soft delete; it leaves recall at once.
  • Your sessions: meshpoint logout, or revoke from the console’s Org page.
  • Your membership: an owner or admin removes you; your account stays if you belong to another organization.
  • An organization: an owner types its name on the Org page. Projects, items, raw turns, keys, sessions, invites and the billing record go at once, the subscription is cancelled, and members with no other organization lose their accounts. A point-in-time database copy kept by the hosting provider for disaster recovery expires within 30 days.

The platform runs on Cloudflare Workers with per-project storage objects and a key-value edge cache. Sign-in is through WorkOS; payments through Stripe; invite email through Resend. The privacy policy lists each processor.