MCP Privacy Information

SJinn MCP data handling

This page supplements the SJinn Privacy Policy with information about the remote MCP integration, including the OpenAI plugin. The SJinn Terms of Service also apply. Your AI client has its own privacy terms for the conversation and tool results it receives.

Account connection

You sign in and authorize the connection on SJinn. The MCP server associates OAuth authorization codes and tokens with your account, the client identifier, authorized scope and expiration information. Token values are hashed for server-side lookup. The service also stores negotiated client information and whether the client supports interactive MCP Apps UI.

The authorized client can access the account and task operations exposed by the MCP tools. The account-check result includes an account identifier, display name, masked email address, membership status and credit balance. Task and history tools are scoped to the connected account.

Tool inputs and media

SJinn processes the arguments the client sends to its tools, such as generation prompts, selected models, generation settings, task identifiers, and reference image, video or audio URLs. The MCP tools do not request the full chat history. Your client controls which information it includes in tool arguments, so avoid including unrelated personal information or secrets in prompts and searches.

When you use the upload tool, SJinn prepares signed upload URLs. Your browser or local client sends the selected files to SJinn's configured object storage. Uploaded media is then available through a stable asset URL for generation. Media and transcript result URLs can be accessible to anyone who has the link; do not treat a media URL as an account-protected document or share it publicly if it contains private material.

To fulfill generation and transcription requests, SJinn sends the necessary prompts, settings and media references to the service providers used by the selected operation. Task records retain inputs, status and output references so results can be queried and failures investigated. The connected client receives the task ID, status, generated media links or transcript data needed to present the result.

Model discovery and usage records

Model listing and full model details come from SJinn's catalog. Semantic model search sends the search query and catalog details to a server-side AI provider. Do not put credentials, private media URLs, account details or unrelated conversation content into a model search query.

SJinn records tool usage and task information to operate and troubleshoot the integration. These records can include the authenticated account, tool type, outcome, task references, timestamps and client User-Agent. Task creation also records the associated credit transaction. A status query does not start a new generation task.

Connection controls and data requests

Use your AI client's connection controls to stop using or remove the integration. Removing a connection does not by itself delete existing SJinn tasks or uploaded media, cancel an already submitted provider job, or refund a completed credit transaction. OAuth credentials are time-limited and processed through SJinn's token expiration and cleanup mechanisms.

For access, correction, deletion or connection-revocation requests, contact SJinn support and request a private channel for account-specific information. Do not send passwords or tokens. General retention and privacy terms are described in the SJinn Privacy Policy; this page does not promise immediate erasure from storage, providers or backups when a client disconnects.