refsee

Privacy for AI connections.

This notice supplements the Refsee Privacy Policy for connections to ChatGPT, Claude and other MCP clients.

Data exchanged

When you connect, Refsee records your account, the connecting application's identifier and supplied name, the permissions you grant, connection dates and the last API-use time. Refsee receives the tool arguments needed for an action, such as a search query, frame identifier or moodboard description.

Tool results may include your username, plan and remaining credits, requested reference metadata, and moodboards or search history covered by the granted permissions. The connecting AI provider receives these results and handles them under its own terms and privacy policy. Connecting does not give Refsee access to your entire conversation history.

Credentials

Your Refsee password and browser session cookie are not shared with the MCP client. Client tokens are stored as hashes. The MCP service's delegated Refsee credentials are encrypted at rest; Refsee stores only their hashes.

Usage and retention

Refsee uses this information to authorize requests, apply your plan and quotas, operate the service and investigate failures. Search and viewing actions may also appear in your normal Refsee usage history. This integration does not add a separate advertising tracker.

Access tokens last one hour. Refresh tokens expire after 30 days without renewal. A Refsee connection expires after 90 days and then requires reconnection. Expired authorization state is removed by scheduled cleanup. Connection records are retained for up to 30 days after expiry or revocation; normal Refsee account data follows the main Privacy Policy.

Your controls

Manage your connections to inspect permissions or revoke access. Revocation blocks further requests; it cannot erase results already delivered to an AI provider. Manage that provider's conversation history and data controls separately.

Contact hello@refsee.com for privacy, access or deletion requests.