> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getlago.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact Lago

> Find the correct Lago contact route for implementation help, community questions, sales, security, privacy, and service status.

Choose the channel that matches your request. Do not include API keys, customer records, invoices, payment details, or other sensitive data in a public message.

## Implementation and community questions

Join the [Lago community Slack](https://www.getlago.com/slack) to ask implementation questions, compare patterns with other Lago users, and discuss the open-source project. For a reproducible problem in the open-source product, search existing issues and open a new report in the [Lago GitHub repository](https://github.com/getlago/lago/issues). Include the Lago version, deployment method, relevant logs with secrets removed, and the smallest reproduction you can provide.

## Cloud support and account questions

Lago Cloud customers should use the support route included with their account. For general product, account, partnership, or commercial questions, email [hello@getlago.com](mailto:hello@getlago.com) or [book a demo](https://getlago.com/book-a-demo). Never send credentials or unredacted financial data by email.

## Security and privacy

For a security vulnerability, follow the private reporting instructions in the main [Lago repository security policy](https://github.com/getlago/lago/security). Do not disclose an unpatched vulnerability in a public issue or community channel. For privacy and data-protection questions, contact [dpo@getlago.com](mailto:dpo@getlago.com) and review the [privacy policy](https://getlago.com/legal/privacy-policy).

## Service health

Before reporting an availability incident, check [status.getlago.com](https://status.getlago.com/) for active incidents and maintenance notices. When contacting support, state whether you use Lago Cloud or self-hosted Lago, the affected environment, when the issue began, and any request ID returned by the API.
