Privacy Policy

infersurge is built on a simple promise: the gateway sees metadata, not content. This page explains exactly what we collect, what we deliberately never keep, and why.

Effective date: October 19, 2026

01 · Overview 02 · What we store 03 · Encryption 04 · Third parties 05 · Retention & deletion 06 · Contact
// 01 · Overview

Minimum data, by design

infersurge is a remote device gateway. It routes tool calls from your AI client — ChatGPT, Claude, VS Code, or any MCP-compatible harness — to machines you own, over an encrypted WebSocket maintained by a small agent running on each device.

To run accounts, meter usage, and keep the service secure, we collect the minimum: your account email, usage counts (how many tool calls succeeded), and a short audit trail of events. That is the entire list.

The content of your work — files, terminals, screens — flows end-to-end between your AI client and your devices. The gateway relays it in memory and stores none of it. See Terms of Service for the contractual side.

// 02 · What we store

Stored vs. never stored

The gateway is a zero-content-storage system. Here is the complete, honest inventory:

What we store

metadata only

  • Your email — sign-in identity, stored encrypted (see §03)
  • Device names — the labels you give enrolled machines (e.g. web1)
  • Usage counters — counts of successful tool calls per billing period, per plan limit
  • Audit events — timestamp, device and tool identifier, and outcome (success / failure) of each call
  • Token hashes — SHA-256 digests used to verify your device, session, and MCP tokens

What we never store

zero content storage

  • File contents — read or written on your devices
  • Terminal output — stdout/stderr of any command
  • Command contents — what your AI asked the device to run
  • Screenshots — screen captures pass through, are never persisted
  • Any payload your AI client and devices exchange
Why this matters: content travels live between your AI client and your device through the gateway's memory and is discarded once delivered. It is never written to disk or to our database. We could not hand your files, transcripts, or screenshots to anyone — including ourselves — because we do not have them.
// 03 · Encryption

Encrypted at rest, encrypted in transit

  • Email at rest — AES-256-GCM. Your email is stored as authenticated AES-256-GCM ciphertext. Because ciphertext cannot be searched, account lookup uses a separate one-way SHA-256 blind index. The database never holds your plaintext email.
  • Tokens — SHA-256 hashed. Device tokens, MCP tokens, and session identifiers are stored only as SHA-256 hashes. Plaintext tokens exist solely in your console session (in memory) and in your device agent's local credential file, which is written with owner-only permissions.
  • In transit — TLS everywhere. Browser → gateway traffic uses HTTPS; device agents connect over encrypted WebSocket (wss://). No inbound ports are opened on your machines: devices dial out to the gateway.
// 04 · Third parties

A short list, on purpose

  • Cloudflare — hosts the gateway API, edge network, and databases for api.infersurge.com and app.infersurge.com.
  • Google — sign-in via Google OAuth. We receive your name, email, and account identifier; Google's own privacy policy covers their processing.
  • Creem — payment processing for paid subscriptions. Card details go directly to Creem and never touch infersurge.

We do not sell or rent personal data. We run no advertising networks and no third-party analytics scripts on this site. And because we never store your content, your data is not used for model training — there is nothing to train on.

// 05 · Data retention & deletion

Your data, your exit

  • Removing a device deletes its record and revokes its access immediately; its live connection to the gateway is terminated at the same moment.
  • Deleting your account: email mail@infersurge.com and we will delete your account, encrypted email, devices, sessions, token hashes, and usage history.
  • Billing records are kept only as long as tax and accounting law requires, then deleted.
  • Usage counters reset with each monthly billing period; raw per-call audit events are the only per-call trace we hold, and they contain identifiers — not content.
// 06 · Contact

Questions

For any privacy question, data request, or deletion request, contact us at mail@infersurge.com. We aim to respond within two business days.