Support & Contact
Help with ScrubMyText, LockMyAction, CatchMySignal, ApproveMyAction, API access, MCP connections, billing, and subscriptions.
Contact
Email is the primary support channel:
For faster troubleshooting, include the product, endpoint or MCP tool name, the HTTP status if available, and a non-sensitive example of what happened.
Do not send passwords, private keys, full API keys, payment-card numbers, live CatchMySignal webhook URLs, or live ApproveMyAction approval links.
Billing & subscriptions
Paid subscriptions are processed by Stripe. The same paid API key works across the text platform and the agent-infrastructure tools.
Developer support
See the developer docs, MCP guide, and agent infrastructure overview.
Before you contact support
These checks resolve the most common browser, REST, and MCP problems without sharing sensitive material.
Browser tool
Reload the page, confirm JavaScript is enabled, and try a short non-sensitive sample. Document scanning happens in the browser for supported formats; a very large or unsupported file can fail before analysis begins.
REST API
Record the endpoint, request method, response status, and request ID if one is returned. Confirm the base URL is https://api.scrubmytext.com and send credentials only in the documented authorization header.
Remote MCP
Reconnect the server, refresh its tool list, and note the client name and failing tool. Compare the behavior with the matching REST contract when possible; both surfaces use the same underlying operations.
What to include
Tell us what you expected, what occurred, whether it is reproducible, the approximate time with timezone, and the smallest sanitized input that demonstrates the issue. Screenshots are useful when they do not expose tokens or private data.
Security concerns
Do not test a suspected vulnerability against other users or production data. Email a concise description and reproduction steps. We will acknowledge the report and may ask for a controlled example before confirming impact.