How MentionFox handles your data when you connect via ChatGPT, Claude Desktop, Cursor, or any other MCP client.
This document describes data handling specifically for the MentionFox connector — the MCP endpoint at mentionfox.com/mcp and any submitted-but-not-yet-approved variant in OpenAI's ChatGPT App directory, Anthropic's Claude Connector directory, Cursor's Composer MCP directory, or Continue.dev's tool registry. For all other product surfaces, the master Privacy Policy applies.
Where this document is silent, the master Privacy Policy controls. Where this document specifies a tighter rule (for example, narrower retention than the master policy), the tighter rule applies inside the connector context.
When you authorize a connector — by clicking "Connect" inside ChatGPT, Claude Desktop, Cursor, or any other MCP host — MentionFox issues your AI host an OAuth 2.0 access token tied to your MentionFox account. The token carries exactly the scopes you approved on the consent screen.
| Scope | What it grants |
|---|---|
research:read | Run research, scans, comparisons, and reports on your behalf. Returns the same data you would see in the MentionFox dashboard. |
pipeline:write | Append leads to your Dealflow pipeline via the save_to_my_pipeline tool. Append-only — never modifies or deletes existing leads. |
No other scope is requested. We do not request access to your email inbox, calendar, files, or any third-party services.
Each tool call from the AI host includes:
tool: get_dossier, args: { name: "Brian Armstrong", company: "Coinbase" }.chatgpt-app/1.0, claude-desktop/2.x, etc.) and Cloudflare/Supabase trace headers.We do not receive the user's full ChatGPT or Claude conversation. We see only the structured tool call your AI host generates from the conversation. If your conversation says "find Brian Armstrong's email and tell me what he had for breakfast", we receive only the enrich_person tool call with { name: "Brian Armstrong" }; the rest of the conversation never reaches us.
When you call a research tool, MentionFox may run an enrichment pipeline against public sources and cache the result in person_profiles. Cached enrichments are shared across users (privacy-preserving — only public data is cached) so subsequent lookups are faster and cheaper. Cache hits cost zero credits.
You can request deletion of any cached profile that is about you personally via /privacy/data-deletion.html.
The connector touches the following third-party services:
| Processor | Purpose | Data shared |
|---|---|---|
| Supabase (Postgres + Edge Functions) | Database + serverless compute | Tool call logs, user profiles, OAuth tokens (encrypted at rest) |
| Cloudflare | Edge routing for foxapis.com / mentionfox.com | Standard request metadata (IP, user-agent) |
| Anthropic API | LLM-backed report generation (founder reports, dossiers) | The subject's public-data enrichment payload — never your conversation history |
| Serper / Google | Public-web search for enrichment | The subject's name + disambiguation hints |
| OpenAI API | Optional fallback LLM for select tools | Same as Anthropic — public-data enrichment payload |
| Stripe | Subscription billing | Email + payment metadata. Not invoked on free-tier connector calls. |
| Resend | Transactional email (account, billing receipts) | Email address only |
The full processor list is in the master Privacy Policy. We do not use AI-host conversation data to train any model — neither our own nor any third party's.
| Data type | Retention |
|---|---|
| Tool call logs (name + args + response summary) | 90 days |
| Cached entity enrichments (public data) | Indefinite, refreshed on demand. Subject can request deletion. |
| OAuth access tokens | Until revoked by user or 1 year, whichever is sooner |
| OAuth refresh tokens | Until revoked by user |
| Billing events | 7 years (accounting requirement) |
| Account metadata (email, plan, credit balance) | Until account deletion + 30 day grace period |
| Saved leads in your Dealflow pipeline | Until you delete the lead OR the account |
To disconnect at any time:
Revocation is instant. Cached entity enrichments and saved Dealflow leads are not affected by token revocation — they're tied to your account, not the connector. Delete the account to wipe everything.
MentionFox is operated by RiteKit Inc., a Delaware C-corp. Production infrastructure runs on Supabase (US-East primary, EU read-replicas) and Cloudflare (global edge). Data may be transferred between the US, EU, and Japan as part of normal operation. We rely on standard contractual clauses (SCCs) for EU-to-US transfers and on Japan's adequacy decision for JP transfers.
If you are a connector user, you have the same rights as any MentionFox account holder:
MentionFox is not directed at users under 16. We do not knowingly process data of users under 16 via the connector or any other surface.
OAuth tokens are stored encrypted at rest. Tool calls travel over TLS 1.3. Internal database access is gated by row-level security policies (Supabase RLS). Service-role keys live only in Edge Function secrets and are never exposed to clients. Pre-commit hooks block accidental secret commits.
Security incidents are reported to security@mentionfox.com. Confirmed breaches are disclosed to affected users within 72 hours, per GDPR Article 33.
Privacy questions: privacy@mentionfox.com
Security questions: security@mentionfox.com
General contact: osakasaul@gmail.com
Postal: RiteKit Inc., 8 The Green, Suite 7000, Dover DE 19901, USA