Privacy
This page describes the data the Ekord service handles. It is a product description, not a certification or legal guarantee.
Account and device data
Ekord stores the account identifier and login binding needed to sign you in, plus paired device identifiers, revocable device credentials, online/ last-seen state, and OAuth clients/grants/tokens required for the MCP connection.
Tool payloads
To execute a request, the Gateway relays tool arguments and results between the authenticated AI client and your paired Agent. Ekord does not use file bodies, command text, stdout/stderr, patches, or project snapshots as a durable project-history store.
Optional product telemetry
Product telemetry is disabled unless you explicitly enable it in Account. With telemetry disabled, Ekord does not create product-analytics events. Support diagnostics below are separate and do not depend on telemetry consent. Strictly necessary security/service logs may still exist to operate the service.
Support and feedback
Support and feedback text is stored because you submit it. A Support request may include up to 16 recent, content-free operational diagnostics for fault diagnosis and service security. Those diagnostics are limited to seven days and 128 events per pseudonymous support subject. A diagnostic snapshot attached to a support request is cleared after seven days.
Support diagnostics do not include prompts, paths, commands, file contents, outputs, credentials, tokens, or raw provider responses. Feedback does not attach diagnostics.
When enabled, Ekord records content-free operational metadata such as a pseudonymous user identifier, tool name, success/failure, sanitized error code/category, latency, coarse result-size bucket, truncation state, observed MCP/client version, Agent/Gateway version, and coarse activity/ reconnect state.
Telemetry never includes
- prompts, command text/arguments, or working-directory values
- paths, filenames/extensions, file/search/patch contents, stdout/stderr, or result bodies
- screenshots, clipboard contents, environment variables, tokens, secrets, or credentials
- raw error text when a sanitized error code/category is sufficient
Turning telemetry off
Disabling telemetry stops new product-analytics events. It does not imply that previously recorded telemetry is immediately erased.
Retention
The current staging implementation does not yet promise a fixed automatic deletion window for previously recorded telemetry. A production retention period must be published and enforced before public telemetry launch.
Contact
For privacy or access questions, use the Support page.