useSignal plugin privacy policy
Effective October 2, 2026. This policy covers the useSignal MCP plugin, its workbench, and these plugin information pages. The plugin is operated by Sanket Naik (useSignal).
Data you provide
The plugin receives the inputs you choose to send to its tools: JSON objects and form settings, JSON documents to format or compare, hex colors, regex patterns, sample text and test cases, text to encode, decode or hash, JSON Web Tokens to decode, cron expressions, timestamps and time zones, QR code content (such as links, contact details or Wi-Fi network names and passwords), placeholder image settings, and code or steps for flowcharts. These inputs may contain personal information or secrets if you include them; use test tokens and test passwords where you can. They are used only to generate the requested result, validate inputs, and return errors. Avoid credentials and sensitive data.
Placeholder images are served from usesignal.dev at the URL the tool returns. When a page or app displays one, the viewer’s browser requests it from our server like any other image.
Where processing happens
Initial tool inputs are transmitted to useSignal’s server hosted on Vercel. The server processes inputs in memory and returns results. Form preview edits after generation regenerate exports locally in the workbench using the same form generator. The standalone browser preview sends generation requests directly to the same server. Other tools on the main useSignal website can have different processing behavior.
Storage and retention
The plugin application does not save tool inputs or outputs to a database, write them to disk, or intentionally log their contents. Request data is held for processing and is not intentionally retained by the application after completion. Form edits and rendered results remain in the current page until you close or reload it. Exports you copy or download remain wherever you save them.
Hosting infrastructure can process IP addresses, request metadata, timings, and operational logs for delivery, reliability, and abuse prevention. Infrastructure retention depends on the hosting plan and configuration; Vercel describes its runtime log retention in its runtime logs documentation. This policy does not promise immediate deletion from provider logs. Short-lived in-memory request counters support rate limiting and expire after inactivity or an instance restart.
Service providers and sharing
Vercel provides hosting and handles network traffic. The AI assistant you connect the plugin to, such as Claude (Anthropic) or ChatGPT (OpenAI), processes your conversation and tool inputs and outputs under its own account settings and policies. The plugin does not send tool inputs to other external APIs, sell tool data, use it for advertising, or implement its own AI training. We may disclose support records when necessary to meet a legal obligation.
Cookies and analytics
The plugin workbench and these static plugin information pages do not add application cookies, analytics trackers, or local-storage persistence. The separate main website uses Vercel Analytics; its traffic measurement is outside the plugin workbench. Your host browser and AI assistant may retain their own history or cookies.
Support messages
If you email support, we receive your email address and the details and attachments you send. We use them to respond and investigate your request. Support correspondence is kept until the issue is resolved and for up to 12 months afterward, unless a legal obligation requires longer retention.
Your choices
You can stop using or disconnect the plugin, close the workbench, delete your downloaded files, and manage conversation retention in your AI assistant. For access, correction, or deletion of support correspondence, contact 1100sanket@gmail.com. Rights vary by location. The stateless plugin has no saved user workspace or input history to retrieve or delete.
Changes and contact
We update this page when plugin data practices change. Questions can be sent to 1100sanket@gmail.com or through the support page.