MCP Connector Privacy

Scope

This page describes how PostQuickAI handles data when you connect it as a remote MCP connector to an MCP client. It supplements our main Privacy Policy, which continues to apply.

What the AI Client Sends Us

When you use the connector, the MCP client sends:

• An OAuth access token identifying you — issued only after you sign in to PostQuickAI and approve the connection.
• Tool call arguments — the parameters needed to perform the reviewed connector action you requested (for example, a content ID, a scheduled time, or selected publishing platforms).

The connector does not request a full conversation transcript. However, any information an MCP client includes in a tool-call argument is sent to PostQuickAI as request data.

What We Return to the AI Client

Depending on the permissions you approve and the tools you request, we return your content groups and saved brand context; connected account names, identifiers, follower counts and connection health; post, video and story content and schedules; and social performance metrics. Media tools return file names, file metadata and public image, video or audio URLs. Website research tools return scan status and research results. AI tools return generated text or media. These results are sent to the connected client so it can answer your request.

What We Store

• Content and research: drafts, schedules, generated media and audio settings are saved when the requested tool performs those actions. We store website scan identifiers with your user identifier to restrict access to your research results.
• OAuth client registration: the name and redirect URIs of the AI client you connected.
• Approved connections: your account identifiers, approved permissions, connection expiry and revocation status, so we can enforce the access you granted.
• Refresh tokens: stored only as irreversible SHA-256 hashes so they cannot be recovered from our database. Access tokens are not stored at all.
• Upload links: when an AI client asks you to upload a file, we store the link's status and, after you upload, the file in your PostQuickAI storage and its public URL, which is returned to that client. Files uploaded this way count toward your storage like any other upload.
• Request logs: the endpoint, timestamp, and status of each connector request, for security monitoring and rate limiting. We do not log the full content of your posts in these records.

How We Use This Data

• To authenticate you and perform the actions you request through the AI client.
• To enforce subscription, API access, and rate-limit checks.
• To detect and prevent abuse.

We do not use connector data for advertising, and we do not sell it. See our main policy for details.

Retention

• Authorization codes expire 60 seconds after issue.
• Access tokens expire 1 hour after issue and are never stored.
• A connection expires 30 days after authorization. Rotating its refresh token does not extend that expiry; revoking the connection invalidates its tokens sooner.
• Token expiry does not delete stored records. See our main Privacy Policy for data-retention and deletion information.

Sub-Processors

The remote MCP connector relies on the same infrastructure providers as the rest of PostQuickAI:

• Supabase — authentication and database.
• Vercel — application hosting.
• AI model providers receive the text, prompts, reference images and brand-profile details included in AI tool calls, only when you grant AI tool access. OpenRouter routes text and catalog image/video requests to the selected model provider. Built-in image and video models use Google or OpenAI; music generation uses Google Lyria.
• Website research services receive the website URL, requested scan type and your account identifiers when you start a scan. The service fetches website content and returns research results.
• The social platforms selected for a supported connector publishing action (for example LinkedIn, X, Threads, Bluesky, TikTok, YouTube, Instagram) receive content when an approved publishing action runs, including scheduled publication.

Revoking Access

You can disconnect the connector at any time:

• From within the AI client's connector settings, or
• By contacting us to revoke a specific connection.

Revoking invalidates the connection, so new tool calls are rejected even if an access token has not reached its expiry time. Calls already authorized may finish. Previously scheduled posts and accepted publishing jobs are not cancelled by disconnecting.

Contact

Questions about the MCP connector and your data? Reach us through the support options on the MCP page.