Privacy

Privacy

The short version: the site has no accounts, no ads and no tracking. Connecting an AI tool needs a sign-in, and we keep an account id, not your email address or profile.

The website

Pages and data files are served as static files by Cloudflare. We set no cookies and run no analytics or advertising scripts on them. Cloudflare processes requests (IP address, user agent) to deliver the site and protect it from abuse, under its own privacy policy.

The MCP server sign-in

To connect an AI tool to the VC Within MCP server you sign in with GitHub, Google or a one-time code by email.

  • GitHub: we read your numeric GitHub user id and username once, at sign-in. We ask for no GitHub permissions.
  • Google: we read your Google account id (OpenID “sub”) once, at sign-in. We don't ask for your email or profile.
  • Email code: we use your address to send the code and then forget it. Your account id is a one-way hash of the address.

We store: that account id, when it first signed in and last signed in, and the OAuth records the connection needs (the app you connected, its permission, and hashed, expiring tokens). Per tool call we record which tool ran, whether it worked, how long it took and a hashed account id, to keep the service running and fair. We don't store your questions or the answers.

The sign-in and consent pages set short-lived, strictly necessary cookies that tie the sign-in steps together and protect them from cross-site requests. They hold no tracking data and expire when the sign-in is done.

A connection expires after 90 days without use. To end one sooner, remove VC Within from your AI tool; to have your account record deleted, write to contact@vcwithin.com.

Your AI tool

What you type into Claude, ChatGPT, Cursor or another tool is handled by that tool's provider under its own terms. VC Within only sees the tool calls the assistant makes to it.

Last updated 2026-11-16. Questions: contact@vcwithin.com.