Last updated: 24 August 2026
Overview
BuildAPlugin is a local-first REST client and plugin workspace. Requests, collections, environment variables, and installed plugins remain on your device unless you export them, deliberately send a request, use an external integration, or submit information to us.
Information we collect
- Information you submit through support, feedback, account, or checkout forms.
- Basic website and download analytics, including pages viewed, referral source, browser type, and download events.
- Transaction, licensing, and account information when paid services are enabled.
- Operational email records needed to deliver account, support, security, and service messages.
How we use information
We use collected information to operate and secure the website, provide downloads and support, deliver requested communications, understand product usage, improve BuildAPlugin, and meet legal obligations. We do not sell personal information.
MCP and ChatGPT integration
When you use BuildAPlugin tools in ChatGPT, ChatGPT sends the tool arguments you supply to the BuildAPlugin MCP service. These arguments may include plugin names and messages, API collection names, folder names, request URLs, headers, and raw request bodies. The service processes this content to generate plugins, convert collections, or summarize their structure and returns the result to ChatGPT. It does not read your desktop workspace, execute supplied JavaScript, or send the API requests contained in a collection.
The MCP service temporarily holds request source IP addresses and request counts in a bounded in-memory map to limit abusive traffic. Quota windows last one minute; expired entries are purged on subsequent traffic. These entries are not written to application storage or application logs.
The MCP service does not write tool arguments or results to application storage or application logs. Hosting and network infrastructure may retain operational request metadata under its configured policies. ChatGPT processes your conversation and tool results under its own terms and privacy settings. Do not include passwords, API keys, tokens, private customer data, or confidential payloads in tool arguments. Use variable placeholders where possible.
The desktop MCP client sends only the JSON arguments you explicitly enter to the server you select. Tool calls may change data on a third-party server; review the server and arguments before confirming a call. Desktop MCP inputs and results are session-only and excluded from workspace persistence and exports. Third-party MCP servers handle submitted data under their own policies.
Third-party services
We use service providers such as Amazon Web Services for hosting and transactional email, and may use platform providers such as Google and YouTube for approved marketing and publishing activities. Those providers process information under their own privacy terms.
Security and retention
We restrict access to operational data and retain it only as long as reasonably necessary for the purpose for which it was collected. Do not submit passwords, API keys, production secrets, private customer data, or confidential request payloads through support forms.
Your choices
You may request access, correction, or deletion of personal information you submitted to us, subject to applicable legal and operational requirements.
Contact
Privacy questions may be sent to privacy@buildaplugin.com. Mail to this address is routed to the BuildAPlugin operator.