Privacy Policy

Last updated: October 7, 2026

Toolport is a local-first MCP gateway. This policy explains what data we do and don't collect across the Toolport desktop app, the marketing site at toolport.app, and the hosted Toolport Teams service. Toolport is operated by South Forge AI ("we", "us"). Questions: support@toolport.app.

The short version

The Toolport desktop app and its gateway run entirely on your machine. Toolport stores upstream credentials in each person's OS keychain and sends them to their configured upstream server when needed. Teams is designed to sync configuration and credential references, not upstream credential values. It strips recognized secret fields and rejects known secret patterns; do not paste secrets into shared commands, URLs or instructions. The desktop app needs no account and has no usage telemetry on its own. The one exception is hosted Teams. If you sign into a Team, the gateway reports operational status and aggregate usage (managed-call successes/failures, configuration versions, readiness, and estimated schema token-equivalent avoided; no prompts, arguments or results) so your team dashboard works. Otherwise we only receive data when you use our website.

The desktop app and gateway

• Credentials stay local. Keys and tokens for the MCP servers you connect live in your OS keychain (macOS Keychain, Windows Credential Manager, or the Linux Secret Service) and are injected at runtime. They are sent to the configured upstream service when needed for authentication, not to the Teams control plane.
• No telemetry from the app on its own. The desktop app and local gateway don't collect usage analytics or send your servers, tools, or call contents to us. The one exception is hosted Teams: if you sign into a Team, the gateway reports operational status and aggregate managed-call successes/failures and schema estimates, attributed to team, member, shared server and an opaque device identity so your team dashboard works. Diagnostics you export are shown to you first and sent only if you choose to.
• Activity stays on your device. Toolport keeps recent local logs so its Activity views work: a rolling audit log (about 5,000 entries), discovery traces (~500), inspector history (~50), and a savings log (~2,000), plus a running savings total. These live in your Toolport data folder. Teams operational aggregates are separate. If your organization enables optional per-call audit export, tool name, time, duration, outcome and an argument hash may be sent to its control plane; argument and result contents are excluded. You can export or delete local logs.
• Updates. To check for new versions, the app requests a small release manifest from GitHub. That request is subject to GitHub's own privacy practices.

The website (toolport.app)

• Analytics and advertising measurement. We use PostHog to understand aggregate traffic and which pages are useful. We use X's Pixel on download, client and comparison pages to measure ad conversions. We do not send X your team configuration, tool calls, API keys, or other credentials, and we do not sell this data.
• Contact / lead forms. If you submit an email through a form (for example, a Teams inquiry), we store it to reply to you and may send it to ourselves by email.

Hosted Toolport Teams

If you create or join a hosted Teams account, we store what's needed to run it:

• Account identity: your email address and, if you sign in with GitHub or Google, the identifier and basic profile that provider returns.
• Team data: team and membership records, roles, seat count, and the team's shared MCP server configuration. Teams strips recognized secret fields and rejects known secret patterns. Do not paste secrets into shared commands, URLs or instructions.
• Billing state: subscription and seat status. Card details are handled by Stripe; we never see or store them.
• Sessions and devices: login cookies, session and connection records, device names and IP addresses used for device approval and management.
• Security and team operations: 2FA seed and recovery material, audit events, configuration proposals, notification delivery records and webhook configuration and delivery records. Visitor records may be derived from IP addresses and user-agent strings.
• Optional error reporting: when configured, Sentry or a compatible GlitchTip service receives error details and diagnostic breadcrumbs. The fields depend on the configured integration.
• Usage stats: for the team dashboard we record aggregate call successes/failures and estimated schema token-equivalent avoided per shared server, plus member/device contact, applied configuration versions and coarse setup readiness. Server receipt times establish first/latest reported success. Required reporting does not include prompts, arguments, results, credential values or filesystem inventory. Optional per-call audit export is separate. Account deletion removes aggregate usage; team audit/call history remains under the team's retention policy. Self-host records are stored on your server; configured external email, analytics or error-reporting providers receive relevant data.

Sub-processors

Hosted Teams and the website rely on a small set of providers, each handling only what their function requires:

• Cloudflare: website hosting, transactional email delivery for the website and Teams, and Turnstile bot checks.
• PostHog: product/website analytics.
• X: advertising conversion measurement (pixel on download, client and comparison pages).
• Stripe: payment processing.
• Linode: Hosted Teams infrastructure, including its SQLite database for account and team records.
• Sentry or GlitchTip, when configured: error details and diagnostic breadcrumbs.
• GitHub and Google: optional OAuth sign-in.

Retention

We keep hosted Teams account and team data while your account is active. Before deleting an account, transfer or delete teams you own. Account deletion removes profile, sessions, memberships, devices and aggregate usage; team audit/call history remains under the team's retention policy and may still identify the actor. We may also retain records we are legally required to keep, such as billing history. Contact support@toolport.app about records that remain in a team's history.

Your rights

Profile export includes your profile and owned-team list. Team audit/usage exports are separate. Before deleting an account from your profile settings, transfer or delete teams you own. You can also request access, export, or deletion of the personal data we hold about you by emailing support@toolport.app. Depending on where you live, you may have additional rights under laws such as the GDPR or CCPA; we honor those requests.

Children

Toolport is a developer tool and is not directed to children under 16. We do not knowingly collect their data.

Changes

We'll update this page and the date above when this policy changes. Material changes to the hosted service will be communicated by email where appropriate.

Contact: support@toolport.app