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

# Privacy & Support

> How Neo handles Jira and Confluence data, and where to get support and trust information.

This is the trust and support reference for Neo in Jira and Confluence.

## What data Neo uses

Neo only uses Atlassian data to support the request you make, whether you mention `@neo` in Jira or ask Neo in a task. That includes:

* the issue (and comment) you asked Neo to work on, including its description, comments, and attachments
* site, project, and issue details needed to act in the right place
* Confluence pages Neo reads for context (read-only, and only when Confluence is connected)
* your identity, to route the request to the right Neo team

Neo uses this to run the task, reply in the issue, and keep it tied to your team.

## How Neo handles it

* **Neo never trains on your data**, including your prompts, findings, or Jira and Confluence content.
* Your data stays within Neo's customer-scoped environment.
* Credentials and sensitive data follow Neo's platform security controls.

For the full model, see [Security & Privacy](/concepts/security-privacy).

## The Neo bot

Neo acts as a native Atlassian app, running as a bot rather than a user. It uses no Jira seat or license and only acts when you direct it. Confluence access is read-only.

## Support

* [ProjectDiscovery Support](https://projectdiscovery.io/support)
* [ProjectDiscovery Contact](https://projectdiscovery.io/contact)
* `support@projectdiscovery.io`

## Privacy, legal, and trust

* [Privacy Policy](https://projectdiscovery.io/privacy)
* [Terms of Service](https://projectdiscovery.io/terms)
* [Trust Center](http://security.projectdiscovery.io/)

For deeper security or compliance questions, the [Trust Center](http://security.projectdiscovery.io/) is the best starting point, or reach out through the support paths above.
