# Contact Celestia

For documentation corrections, open an issue in the
[Celestia docs repository](https://github.com/celestiaorg/docs/issues). Include
the affected URL, the instruction or example that needs attention, and the
software version and network involved. Remove credentials, private keys, and
other sensitive information before posting a public report.

For community discussions and help with using Celestia, join the
[Celestia Discord](https://discord.com/invite/YsnTPcSfWQ). If a managed RPC endpoint
rejects a request or an API key stops working, contact that endpoint's provider;
documentation contributors cannot change a provider's account permissions or quotas.

For partnership, integration, or other business enquiries, use the
[Celestia contact form](https://celestia.org/contact/).

Report security vulnerabilities privately. Follow the
[Celestia security policy](https://github.com/celestiaorg/.github/blob/main/SECURITY.md)
or email [security@celestia.org](mailto:security@celestia.org). Do not publish
vulnerability details in a documentation issue or community channel. Automated
tools can also read the [security.txt contact record](/.well-known/security.txt).