VaultProof

VaultProof Support

Get help without exposing a secret.

Support covers VaultProof accounts, billing, protected provider routing, scanner results, and MCP connections. Send the smallest amount of operational context needed—we will never ask you to email an API key, password, session token, or MFA code.

Email support Check service status
Before you send
  1. 1Remove API keys, passwords, tokens, cookies, and authorization headers.
  2. 2Include the affected feature, approximate time, provider, and visible error.
  3. 3Use the dedicated security or abuse address for urgent risk reports.

Product help

One support address for account and product questions.

Email [email protected] for login, subscription, usage-limit, scanner, CLI setup, dashboard, and protected-routing questions. If the service may be unavailable, check current status first.

MCP connections

Help connecting ChatGPT to VaultProof.

For authorization failures, include whether the error appeared before or after VaultProof consent, the approximate time, and the client name. Do not send access tokens, refresh tokens, session cookies, API keys, or copied authorization URLs containing temporary codes.

  • Restart the connection from ChatGPT after an authorization request expires.
  • Confirm you are signed in to the intended VaultProof account before approving access.
  • Review or revoke existing connections from the VaultProof MCP connections page.

Safe context

Useful details do not include credentials.

Helpful context includes the feature, provider name, approximate UTC time, HTTP status, redacted request ID when specifically requested, browser or CLI version, and whether the issue affects one project or several.

Never send secrets Do not send raw API keys, VaultProof token values, passwords, private keys, payment-card numbers, MFA codes, session cookies, or full authorization headers. Rotate a credential immediately if it was exposed outside its intended environment.

Security and abuse

Use the channel that matches the risk.

Security vulnerabilities

Send responsible vulnerability reports to [email protected]. Review the security page and security.txt before testing production.

Stolen keys or abuse

Send suspected stolen-key use, fraud, or platform abuse to [email protected]. Include redacted evidence and the time window.