> For the complete documentation index, see [llms.txt](https://help.usehaystack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usehaystack.io/admin/security-and-privacy.md).

# Security & Privacy

Learn how we keep your data safe and meet compliance standards

We prioritize security and perform thorough audits of our applications, systems, and networks to safeguard your data. [Learn more](https://www.usehaystack.io/security)

## JIRA <a href="#h_10a7a31dfc" id="h_10a7a31dfc"></a>

List of data that is stored at Haystack:

<table><thead><tr><th width="206">Category</th><th>Data stored</th></tr></thead><tbody><tr><td>System  </td><td>Issue statuses, priority types, column types, etc.</td></tr><tr><td>Issues</td><td>Title, content, create/update date, assignee, creator, reporter, custom fields (e.g., story points, sprints), etc. </td></tr><tr><td>Issue history </td><td>Title changes, assignee changes, etc.</td></tr><tr><td>Issue comments </td><td>Content, author info, etc. </td></tr><tr><td>Projects  </td><td>Project name, type, key, issue types, etc.</td></tr><tr><td>Sprints</td><td>Start/end dates, title, state, etc. </td></tr><tr><td>Boards</td><td>Board JQL, title, column metadata, etc. </td></tr><tr><td>Members</td><td>Name, account ID, email, etc.</td></tr></tbody></table>

## Version Control (GitHub, GitLab, Bitbucket) <a href="#h_2322e933ed" id="h_2322e933ed"></a>

### Permissions needed

For Haystack to provide meaningful insights, it needs read-access to the git repositories you would like to include.

### Data usage

Haystack only uses metadata (messages, timestamps, status, tags) on pull requests, commits & comments.

{% hint style="success" %}
Haystack does **not** read, store, or persist source code.
{% endhint %}

## FAQ <a href="#h_ff99129c58" id="h_ff99129c58"></a>

<details>

<summary>Where can I see your security and privacy policies?</summary>

Here are the links to our [security](https://www.usehaystack.io/security) and [privacy](https://www.usehaystack.io/privacy) policies.

</details>

<details>

<summary>Do you store or read source code?</summary>

Haystack does **not** read, store, or persist source code.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.usehaystack.io/admin/security-and-privacy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.