Edworking MCP privacy
Edworking MCP is Edworking’s connection service for MCP-compatible assistants.
Data used for your connection
We store OAuth client configuration, permission grants, credential expiry, and an encrypted Edworking API token. OAuth access and refresh tokens are stored as hashes. Your assistant receives the results of the tools you authorize, which can include project and task information, conversation content, participant names, and file metadata.
Retention and control
Connection records expire no later than the underlying Edworking API token. Cached mutation results are encrypted and retained for up to 24 hours to prevent duplicate writes. Expired records are removed periodically. Request logs contain operation names, timing, and outcomes, not credentials, message bodies, or tool results.
Revoke the dedicated connection token in Edworking’s Profile → API tokens to stop access. Your assistant provider controls the conversation history it stores. Contact Edworking through its website for privacy requests.