Troodo Support

Email vitor@madai.com.br from the address connected to your Troodo account. Include only the minimum information needed to identify the workspace and problem.

For invitation, role, login, or access-revocation issues, contact the workspace owner or administrator first. Troodo verifies account and workspace authority before discussing membership or changing access.

The workspace owner can view the current plan and open Stripe's billing portal from Plan & billing. If the portal cannot be reached or a charge appears incorrect, use the private Support route and include the date, plan, and non-sensitive Stripe invoice or session identifier. Never send full card details.

For GitHub, GitLab, Linear, Mixpanel, or New Relic issues, identify the provider, the affected Troodo screen, and whether the connection is cloud, enterprise, self-managed, or browser-direct. Revoke any token you believe was exposed before contacting Support.

A small, reproducible report is safer and faster to investigate. Remove customer secrets, source code, personal data, and raw production logs before sending anything.

• The date, time, and time zone when the problem happened.
• The Troodo page or feature, browser name, and any safe request or error identifier.
• What you expected, what happened, and the smallest steps that reproduce it.

Do not use a public issue, social media post, or shared channel for a suspected vulnerability, credential exposure, cross-tenant access, or customer-data incident. Follow the private reporting instructions on the Security page.

Pilot support is provided on a reasonable-effort basis without a guaranteed response or resolution time unless a signed customer agreement states otherwise. Confirm an incident escalation route and any required service level before relying on Troodo for production-critical operations.