# Support

> How Neural Inverse customers get help: the documentation, the contact form for existing customers, security reports, security documentation and privacy requests.

Source: https://neuralinverse.com/support/

---

Support

# Getting help.

How customers find answers, reach our team, report a security issue or make a privacy request.

For customers

## Where to start.

- **Read the documentation:** Installation, sign-in, each app, Govern's configuration, deployment and operation, with a troubleshooting page for each part.
- **Note the reason code:** When sign-in fails, the app says what happened and what to do, ending with a reason code in parentheses. The troubleshooting pages list the codes; give yours to your administrator, or include it when you contact us.
- **Ask your administrator:** Your administrator controls your organisation's Govern deployment, its policy and the models you may use, and can see what was decided and why.
- **Contact us:** Existing customers reach our team through the contact form with the topic “Support for an existing customer”. Include your organisation, the product and version, and what you tried.

Reach our team

## The right channel for each request.

- **Support for an existing customer:** Use the [contact form](https://neuralinverse.com/contact/?topic=support) with this topic.
- **Security vulnerabilities:** Email [security@neuralinverse.com](mailto:security@neuralinverse.com), not the contact form. The [vulnerability disclosure policy](https://neuralinverse.com/trust/vulnerability-disclosure/) sets out how to report, what we commit to and our safe harbour for good-faith research.
- **Security documentation:** For a security review or questionnaire, use the [contact form](https://neuralinverse.com/contact/?topic=security-docs) with the topic “Security documentation”.
- **Privacy requests:** Use the [contact form](https://neuralinverse.com/contact/?topic=privacy) with the topic “Privacy request”, or email [legal@neuralinverse.com](mailto:legal@neuralinverse.com). The [privacy notice](https://neuralinverse.com/legal/privacy/) explains your rights. For personal data in an organisation's own Neural Inverse deployment, contact that organisation first.
- **Legal and licensing:** Email [legal@neuralinverse.com](mailto:legal@neuralinverse.com).
- **Not yet a customer:** [Request access](https://neuralinverse.com/contact/?topic=access), or read the [questions buyers ask](https://neuralinverse.com/faq/).

Troubleshooting

## Fix common problems yourself.

[Editor →

Sign-in, policy and approvals, audit and models.](https://neuralinverse.com/docs/editor/troubleshooting/)[Agents app →

Sessions, refused actions, worktrees and automations.](https://neuralinverse.com/docs/agents-app/troubleshooting/)[CLI →

Installation, providers, sign-in and permissions.](https://neuralinverse.com/docs/cli/troubleshooting/)[Govern deployment →

Start-up, failing requests, the database, mail and evidence.](https://neuralinverse.com/docs/deploy/troubleshooting/)

![](/photos/team.jpg)

## Talk to our team.

Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.

[Request access](https://neuralinverse.com/contact/?topic=access)[Contact us](https://neuralinverse.com/contact/)