Frihet reviewed connector privacy notice
Last updated: October 8, 2026
This notice applies specifically to the reviewed Frihet connector (the MCP endpoint that ChatGPT, Codex and Claude connect to when a user adds the Frihet connector) and supplements the general Frihet Privacy Policy. Where that general policy describes broader API or MCP integrations, this dedicated notice governs the narrower connector at openai-mcp.frihet.io.
Controller and contact
The controller is VICTOR BERTHELIUS PATO, who owns and operates the trade name Frihet in Spain. For privacy rights, contact ayuda@frihet.io.
Data categories and purposes
OAuth account and workspace identifiers are processed to authenticate and authorize access. At the user's request, the connector sends the provider of the connected AI assistant (for example, OpenAI for ChatGPT and Codex, or Anthropic for Claude) the tool inputs and reviewed result fields needed for the selected operation. Depending on the tool, these may include client, vendor, and contact names, email addresses, and phone numbers; record identifiers and document numbers; descriptions, notes, and CRM activity text; line items, quantities, prices, discounts, tax rates, totals, and deductible classifications; lifecycle, payment, and activity statuses and business dates; and workspace name, country, language, currency, defaults, plan usage, recent activity, top clients, and current-month totals. Dedicated government or banking identifiers, precise postal addresses, credentials, and raw documents are excluded from the reviewed MCP schemas. When a new invoice, quote, or expense is linked by a stored client or vendor name, Frihet may use the matched record's existing identity and contact details internally to link or snapshot the new record, even though those dedicated fields are not returned through this connector. If expense creation needs a new vendor, that vendor is created in a separate backend step and may remain even if the later expense write fails. Technical connection and security data is processed to operate, protect, and troubleshoot the service.
The sign-in page offers email/password and, when enabled for the Frihet project, Google, GitHub, or Microsoft sign-in through Firebase Authentication. Firebase and the selected identity provider process authentication credentials directly. The Frihet connector receives a Firebase ID token after successful sign-in; it does not receive the user's password, and authentication credentials are not sent to the AI assistant provider as MCP tool input or output.
The reviewed MCP schema has no dedicated input or output fields for precise postal addresses, government or banking identifiers, authentication secrets, raw document files, webhook configuration, or regulated filing/export payloads. User-entered names, labels, descriptions, line items, notes, and activity text may nevertheless contain personal data; do not place passwords, credentials, payment-card data, government identifiers, health data, or other special-category data in those free-text fields when you intend to access them through an AI assistant.
Recipients and external effects
Data is processed by Frihet and its necessary service providers: Cloudflare for the connector edge and operational security logging; Google Cloud/Firebase for Frihet infrastructure and authentication; the provider of the AI assistant the user connected, which receives the selected tool inputs and reviewed result fields when the user invokes a tool — for example, OpenAI for ChatGPT and Codex, or Anthropic for Claude; PostHog's EU-hosted analytics service for invoice-creation usage and activation analytics in the underlying Frihet service, including the Frihet user identifier, invoice identifier, document number, and source; and Novu when an invoice or expense creation generates a notification for an eligible workspace admin or accountant. This reviewed host does not send MCP tool telemetry to Langfuse. Novu delivery can include the recipient's Frihet identifier and, when stored, name/email, plus the workspace name and relevant document number, client name, expense description, or vendor name. If the workspace owner has separately configured active Frihet webhooks, one of the ten disclosed webhook-capable writes may deliver one or more full business events to those owner-designated endpoints. Those deliveries are outside the reviewed MCP response schema and can contain the complete underlying record, including fields this connector does not return to the AI assistant; disable the webhooks in Frihet before using write tools if those deliveries are not wanted. An invoice draft counts toward monthly invoice usage. For a referred workspace, its first invoice or expense may update existing referral records and award activation credits to the referring Frihet account.
Retention
Business records remain while the Frihet account exists. Cancelling a paid subscription downgrades the workspace and does not itself delete the account. An account-deletion request starts a 30-day grace and export period; after that period Frihet begins deletion, subject to technical completion and any records that must be retained for as long as law requires. OAuth authorization state is automatically deleted after 10 minutes. OAuth access tokens expire no later than one hour, refresh tokens no later than 30 days, and the bound backend credential no later than its grant; any can end sooner through expiry or revocation. Cloudflare security logs, PostHog analytics events, and Novu delivery records follow the provider-configured retention period needed for security, analytics, delivery, and troubleshooting, after which they are deleted or anonymized under the applicable Frihet and provider settings. Current provider-retention details are available through the privacy contact above. Anonymized aggregated usage data may be retained without a fixed end date. OpenAI and Anthropic each process the interactions in their own assistants under their own published privacy terms.
User controls
Users can choose which tool to invoke, decline any write, revoke OAuth access, edit or delete eligible workspace records, disable existing webhooks in Frihet, request a data export, or exercise access, rectification, erasure, objection, portability, and restriction rights by emailing ayuda@frihet.io.