Security
How we protect access, minimize the data we collect, and handle research questions.
Last updated: October 2026
Authentication & access
Access to TaxMCP is authenticated. MCP connections use OAuth 2.0 with scoped access tokens. Dashboard accounts require a verified email, and login attempts are rate-limited. Passwords are stored only as cryptographic hashes.
Your data
We keep only what we need to run and secure the service:
- Account and subscription details.
- Basic request records, such as the account or API key, time, and tool or endpoint called.
- Session data, which may include IP address and browser information.
We don't store your search text or conversation history in our application database or usage logs. HTTPS connections encrypt data in transit.
You can request deletion of your account data at any time. See our Privacy Policy for details.
Research questions & client data
TaxMCP doesn't need tax returns, source documents, or client identifiers. Use de-identified facts and follow your firm's data-handling rules.
To power search, we send your search text to OpenAI. OpenAI says it doesn't train its models on API data by default and may keep that data for up to 30 days to monitor for abuse. See OpenAI's data controls.
What you type into Claude, ChatGPT, or another AI client is handled under that provider's terms and your firm's settings.
Services we rely on
OpenAI processes search text as described above. Stripe processes payments, so we never see or store your full card number. Our Privacy Policy covers the other providers we use.
Reporting a vulnerability
Found a security issue? Email security@taxmcp.io with steps to reproduce. We'll confirm receipt, investigate, and provide updates. A machine-readable contact is available at /.well-known/security.txt.
Please coordinate with us before public disclosure and do not access data that is not yours. We will not pursue legal action against good-faith security research.