ThrottleProxy

Customer support

A clear human path when setup or traffic does not behave as expected

Support is handled by our team. Choose the closest category, include privacy-safe context, and never send credentials, invitation links, or sensitive request bodies.

Email supportBrowse setup guides
Manual supportNo ticket portalPrivacy-safe context

Choose a category

Send the right context without sending secrets

Setup and onboarding

Workspace creation, verified email, API keys, allowlist patterns, member roles, or manual invitation handoff.

Please describe the setup step, expected result, actual result, and any safe status code. Do not include keys or credentials.

Ask a setup questionGetting started guide

Technical issue

Unexpected status codes, route behavior, configuration sync, or a reproducible dashboard or proxy-path problem.

Please include the affected page or lifecycle stage, approximate timestamp and timezone, safe status code, and reproduction steps.

Report a technical issueRequest lifecycle guide

Billing and plan review

Checkout, reviewed plan activation, public pricing questions, invoices, or usage context.

Please include the workspace name, current tier, intended usage shape, and a safe reply address. Do not include payment credentials.

Request plan activationPlan activation and billing guide

Security concern

Suspected credential exposure, cross-workspace visibility, unsafe routing, authorization behavior, or sensitive data in logs.

Please include the approximate time, affected workspace or stage, sanitized correlation ID if available, and containment already performed. Do not send the suspected secret.

Report a security concernSecurity best practices

Invitation or account issue

Wrong-account messages, verification problems, expired or revoked links, missing workspace access, or role questions.

Please describe the visible invitation/account state and the intended workspace role. Never include the invitation link, token, password, or session details.

Get account helpManual invitation guide

Helpful context to include

  • A short description of what you expected and what happened
  • Approximate timestamp and timezone
  • Safe HTTP status code or high-level error category
  • Sanitized request or correlation ID, when available
  • Affected page or lifecycle stage without query values
  • Browser and viewport for a visual issue

Never include these

  • ThrottleProxy or provider API keys
  • Authorization, Cookie, or session headers
  • Invitation links or raw invitation tokens
  • Stripe, Supabase, Redis, database, webhook, or email-provider secrets
  • Raw customer request or response bodies
  • Personal data that is not required to understand the issue

Support expectations

Messages are reviewed by our team. Support does not include an automated ticket portal or guaranteed response-time SLA. Include a safe reply address and clear reproduction steps so the team can triage efficiently.

Plan changes are also manual. Never send payment credentials by email.

Active security incident?

Deactivate affected keys, suspend questionable workspace access, stop traffic when needed, preserve sanitized timestamps and correlation IDs, then report the concern immediately.

Email a security concern

Keep the first message simple and sanitized

A timestamp, route stage, status code, and clear expected behavior are usually enough to begin. Support will ask for additional safe context if needed.

Email support@throttleproxy.com