1. About this policy
This policy explains what personal data Toolstile collects when you use the managed service at https://toolstile.com, how we use it, how long we keep it, and the choices you have. "Toolstile", "we" and "us" refer to the operator of the managed service. Questions and requests go to support@toolstile.com.
This policy covers only the managed service. If you run the self-hosted edition, your instance's operator controls that data, not Toolstile.
2. What Toolstile does
Toolstile is a gateway between AI agents (such as coding assistants) and the remote MCP servers you connect. You add MCP servers, authorize agents, choose which tools, resources and prompts each agent may use, and Toolstile forwards permitted requests. In a team workspace, owners and admins also manage members, shared MCP entries and agent permissions.
3. Information we collect
Account information. Your name, email address, whether your email is verified, and your profile picture if your sign-in provider supplies one. If you sign up with an email and password, we store your password only as a one-way hash.
Google sign-in. If you choose Continue with Google, Google shares only your basic profile: name, email address, email-verified status, profile picture and Google account identifier. We request only the openid, email and profile permissions. We use them only to create your account and sign you in. Google also returns sign-in tokens, and we store them with your sign-in record. We encrypt the access token. We do not request offline access, and we do not use these tokens to call other Google services. Google sign-in does not give Toolstile access to Gmail, Google Drive, Calendar, Contacts or any other Google data.
Sessions and devices. When you sign in, we record the session's IP address and browser user agent. We also record the devices and agents you authorize, with the names you give them or that we generate.
MCP connections and credentials. For each MCP server you add, we store its label and URL. We also store any credentials you provide, such as API keys or headers, and any OAuth tokens issued when you authorize the server. Credentials and OAuth tokens are encrypted before we store them. Toolstile uses them to authenticate, maintain and refresh your connections, discover available capabilities, and forward permitted requests.
Permissions and workspace configuration. We store workspace names, memberships and roles, sharing approvals, agent grants and blocks, permission policies, custom roles and setup progress.
Requests forwarded through the gateway. When an authorized agent calls a tool or reads a resource or prompt, Toolstile processes that request and the server's response in order to forward them. The gateway temporarily holds request and response data while delivering requests, responses and resumable sessions. We do not routinely persist full request or response bodies in activity logs. Optional debug capture stores selected traffic as described below. Upstream error messages and diagnostic logs may also contain information supplied by a connected service.
Activity metadata. For each forwarded operation we record which agent and MCP entry were involved, the method and target (for example, a tool name), the outcome, the duration, the user and the time. We keep this so you can review activity and troubleshoot. Security and administrative audit records, such as membership, permission and billing changes, are separate from the activity log and may be retained longer where needed for security, accounting, disputes and legal obligations.
Debug capture (optional, off by default). You can turn on capture to inspect the arguments and results of specific agents' requests to specific MCP entries. A capture session stops after one hour unless someone extends it. Before storing a captured request, we size-limit it, redact fields and values that look like credentials, and encrypt it. Redaction is automatic and may not catch every secret, so avoid capturing traffic that contains sensitive data you don't need to inspect. In a personal workspace, only you can start or view captures. In a team workspace, only owners and admins can.
Usage and billing records. We count operations for each workspace to apply plan allowances, and we keep records of plans, billing periods, trials, consent to charges, invoices, refunds and billing notices. Payment card details are entered on the payment provider's hosted pages. Toolstile does not receive or store your full card number.
Messages you send us. If you email support@toolstile.com, we keep the message and our reply so we can help you.
Technical data. Our hosting and network providers process standard request data, such as IP addresses, request paths and timestamps, to deliver the service. Our application may log errors for diagnosis.
Optional analytics. If you allow analytics in this browser, we use PostHog to measure page visits, referrals, account creation and use of product features such as adding connections and saving permissions. Signed-in events use an internal user ID and may include an internal workspace ID, workspace type, role and plan. We normalize workspace paths and remove query strings and fragments before sending events. We do not send email addresses, display names, MCP server URLs or credentials, tool arguments or results, form contents, or captured debug payloads. Session replay and automatic click and form capture are disabled. We do not use advertising trackers.
4. How we use information
We use information to:
- create and secure your account, sign you in and let you recover access
- run workspaces, roles, sharing and agent permissions as you and your workspace administrators configure them
- forward permitted requests to the MCP servers you connect
- show activity and, when enabled, debug captures to the people allowed to see them
- count operations, enforce plan allowances, run trials and subscriptions, and send billing notices such as usage alerts and pre-charge reminders
- send service emails, such as email verification, account recovery and billing notices, where email delivery is enabled
- prevent abuse and enforce rate limits, investigate security issues, and keep the service working
- understand website and product usage when you choose to allow optional analytics
- respond to your requests and meet legal obligations
We do not sell personal data. We do not use it for advertising, and we do not use your content, MCP traffic or captures to train AI models.
5. Google user data
Toolstile's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use Google sign-in data only to provide sign-in and account features you can see. We do not transfer it to others except as needed to run the service, comply with law or protect security. People at Toolstile do not read it except where you agree, where security or abuse investigation requires it, or where the law requires it.
If you connect an MCP server operated by Google, or by anyone else, through Toolstile, that is a separate connection that you approve with that provider. Toolstile handles it like any other MCP connection described above.
6. Who can see your information
People in your workspaces. In a team workspace, owners and admins can see members, their roles, their agents' names, and activity metadata for that workspace. They can also revoke agents' access to the workspace. When you share one of your MCP accounts with a team, members whose agents are granted access can use it through Toolstile. The dashboard does not expose the stored credential to those members. You can hand an account's shared binding over to another member. After a handoff, that member controls the shared binding, and your personal entry stays yours. Billing details and actions are available only to workspace owners.
Service providers. We use these providers to operate Toolstile:
- Railway hosts the application and its database in the Amsterdam region (Netherlands). Railway privacy policy
- Cloudflare provides DNS for toolstile.com and redirects www.toolstile.com. Cloudflare privacy policy
- Autumn, backed by Stripe, handles subscriptions, checkout, payment-method collection, invoices and refunds. We identify your workspace to them by an internal workspace ID. You give your payment and billing details directly on their hosted pages. Autumn privacy policy, Stripe privacy policy
- PostHog provides optional website and product analytics. Events are sent to its US Cloud service when you opt in. PostHog privacy policy
- Resend delivers transactional emails, such as verification, recovery and billing notices. Resend privacy policy
- Google provides sign-in if you choose it. Google privacy policy
MCP servers you connect. Requests your agents make, and the credentials needed to authorize them, go to the MCP servers you or your workspace connected. The server's operator handles that data under its own terms and privacy policy.
Legal and safety reasons. We may disclose information if we reasonably believe the law, a valid legal process or the protection of people, the service or its users requires it.
Business changes. If Toolstile is reorganized or transferred, information may move to the successor under this policy or a successor policy that we tell you about.
7. Where information is processed
Our primary database and application run in the Netherlands. Our providers may process data in other countries, including the United States, under their own safeguards. Using Toolstile therefore involves transferring data outside your country.
8. How long we keep information
- Debug capture contents — Up to 24 hours, then deleted automatically
- Activity metadata, and records of which capture sessions ran (not their contents) — 30 days, then deleted automatically
- Account, workspace, connection and permission data — While your account or workspace exists, plus the 7-day recovery period after deletion
- Email recovery codes — 15 minutes, or until used
- Usage counts and billing records — Kept after deletion as needed for billing, accounting, tax, dispute and fraud-prevention purposes
- Support messages — As long as needed to handle your request and related follow-up
Deleting your account. You can delete your account in the app. Your access, sessions and agent authorizations stop right away. You have 7 days to recover the account. After that, we remove your name, email address, profile picture, sign-in records, sign-in tokens, recovery codes and personal MCP connections. We keep a minimal placeholder record ("Deleted account") so that historical billing, usage and team records stay consistent. An MCP account you handed over to a team stays with the member who received it. Activity metadata and captures expire on their normal schedules. Before a paid workspace can be deleted, Billing must confirm its subscription will not renew and any pending billing changes must be resolved. A team’s last owner must transfer ownership or delete the team before deleting their own account.
Deleting a team workspace. Owners can delete a team workspace. Access stops immediately, and the workspace can be recovered for 7 days. After that, its catalog, sharing, permissions, policies, setup, notifications and memberships are deleted. Its billing and usage records are kept as described above.
9. Security
We protect information with measures appropriate to the service. These include HTTPS for connections to toolstile.com, encryption of stored MCP credentials, upstream OAuth tokens and Google access tokens, one-way hashes for passwords and recovery codes, workspace membership checks on every request, and limited access to production systems. No system is perfectly secure, and we cannot guarantee that unauthorized access will never happen. If we learn of a security incident affecting your personal data, we will notify you and the relevant authorities where the law requires.
11. Your choices and rights
You can:
- update workspace settings, and remove connections, devices and agents in the app
- delete your account or a team workspace you own in the app
- stop debug capture at any time
- ask us for a copy of your personal data, or ask us to correct or delete it
- object to or ask us to restrict certain processing, or withdraw consent where we rely on it
- revoke Toolstile's access to your Google account at any time in your Google Account settings. This does not delete your Toolstile account.
To make a request, email support@toolstile.com from the email address on your account. We may need to verify your identity. We will respond within the time the law allows. Some data, such as billing records, may need to be kept even after a deletion request. If you are a member of a team workspace, some requests about that workspace's data may need its owners' involvement. You may also have the right to complain to your local data protection authority.
12. Children
Toolstile is a tool for developers and businesses and is not intended for children. If you believe a child has given us personal data, contact us and we will delete it.
13. Changes to this policy
We will post changes here and update the date above. If a change materially affects how we use your personal data, we will notify you by email or in the app before it takes effect.
14. Contact
Toolstile, support@toolstile.com