Privacy Policy
Last updated November 15, 2026
OutMCP ("we") runs hosted MCP servers that let your AI assistant (Claude, Cursor, ChatGPT and others) act on services you connect, starting with your own LinkedIn account. This policy explains what we collect, why, and what you can do about it. The controller is Damien Armourdom, Entrepreneur individuel (EI) trading as OutMCP (SIRET 844 015 966 00022), 8 rue Pierre Gourdault, 75013 Paris, France. Contact: support@outmcp.com.
Summary
- We collect only what we need to run your account, connect your LinkedIn session and bill you.
- Your LinkedIn session cookies are encrypted (AES-256-GCM) and are never shown to your browser or your AI client.
- We don't store the content your AI assistant reads or sends through LinkedIn (profiles, messages, search results).
- We don't sell your data, show ads, or use tracking cookies.
- Our database and servers are in the European Union.
What we collect
Your account. Your name, email address and password (stored as a one-way hash). If you sign in with Google or GitHub, the name, email and profile picture they share with us.
Sign-in sessions. The IP address and browser user agent of each signed-in session, to keep your account secure.
Your LinkedIn connection. When you click Connect LinkedIn, the OutMCP Connector extension sends us your LinkedIn session cookies (li_at and JSESSIONID) and your browser's user agent. We store the cookies encrypted and use them only to make the requests your AI assistant asks for, on your behalf. We also keep your LinkedIn member id, name, profile URL and headline to show which account is connected.
Usage records. For each tool call: the tool name, the AI client's name, whether it succeeded, how long it took and the credits used. Not the content of the request or the answer.
Billing. Your plan, credit balance and Stripe customer id. Card details go directly to Stripe; we never see them.
Emails we send you. Account emails (such as the email confirmation link) are delivered by Resend, which records delivery status.
LinkedIn data you work with
When your AI assistant searches people, reads a profile, lists your conversations or sends a message, OutMCP fetches that data from LinkedIn and passes it to your AI client. We don't keep it, apart from short-lived technical logs (errors and request metadata) kept by our hosting provider for a few days.
For personal data about other LinkedIn members that you process this way, you decide what to do with it and are responsible for it (you are the controller); OutMCP processes it only on your instructions. Your AI provider's own privacy policy applies to what it receives.
Why we use it (legal bases)
- To provide the service you signed up for (contract): your account, your connections, tool calls, credits and billing.
- To keep the service safe (legitimate interest): preventing abuse and fraud, limiting the free sign-up credits to one per person, pacing LinkedIn requests to protect your account.
- To meet legal obligations: invoices and accounting records.
Who processes it for us
- Vercel: hosting (servers in Paris, France).
- Neon: database (Frankfurt, Germany).
- Stripe: payments. Stripe acts as the reseller and merchant of record for purchases and handles taxes and invoices.
- Resend: sending account emails.
- Decodo: a residential proxy, so that LinkedIn requests for your account come from a stable IP address in your country. The traffic to LinkedIn stays encrypted (HTTPS) end to end.
Some of these providers are based in the United States. Transfers outside the EU rely on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses.
How long we keep it
- Account, usage records and settings: as long as your account exists.
- LinkedIn session cookies: until you disconnect the account or delete your OutMCP account.
- Sign-in sessions: until they expire (30 days) or you sign out.
- Invoices and payment records: as long as accounting law requires (up to 10 years).
- A one-way hash of your email address, after your account is deleted, so the free sign-up credits can't be claimed again with the same inbox.
The OutMCP Connector browser extension
The extension reads your LinkedIn session cookies only when you click Connect LinkedIn on an OutMCP page, and sends them only to outmcp.com, together with a single-use token tied to your workspace. Its popup checks whether you're signed in to LinkedIn without sending anything. The extension stores no data, doesn't read your browsing history, and doesn't run on any other website.
The use of information received from the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements: it is used only to provide the LinkedIn connection you asked for, never sold, never used for advertising, and never read by people except to fix a problem you report, for security, or when the law requires it.
Cookies
outmcp.com uses only the cookies needed to keep you signed in. No advertising or tracking cookies, so there is no cookie banner.
Your rights
You can ask to access, correct, export or delete your data, and object to or restrict how we use it. Email support@outmcp.com from the address on your account and we'll answer within 30 days. You can disconnect a LinkedIn account at any time from your dashboard; this deletes its stored cookies immediately. You can also complain to your data protection authority (in France, the CNIL).
Security
Connections use HTTPS. LinkedIn session cookies are encrypted at rest. API keys and connect tokens are stored only as hashes. Access to production systems is restricted.
Children
OutMCP is a business tool and isn't meant for anyone under 18.
Changes
If we change this policy in a way that matters, we'll email you before it applies. See also our Terms of Service.