> For the complete documentation index, see [llms.txt](https://hiera.gitbook.io/hiera-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hiera.gitbook.io/hiera-docs/security-and-data-privacy.md). # Security & Data Privacy Hiera is built on Atlassian Forge, so security and privacy are part of the platform, not an add-on. This page explains where your data lives, what we can and cannot access, and how we support you without touching your data. ### Where your data lives * Hiera is a **Forge app**: it runs inside Atlassian's cloud infrastructure, within your own Jira site. There is no Hiera-hosted backend. * Your **native Jira data** (issues, dates, statuses, assignees) stays in Jira. Hiera reads only the issue data it needs (fields, statuses, links, dates) through Atlassian's official APIs and does not copy it anywhere else. **It does not read issue comments or attachments.** * Hiera's **own data** (the strategic hierarchy and Strategic Parents, view preferences, work plans) is kept in **Forge storage, scoped to your site**. ### No external servers * Hiera makes **no outbound calls to non-Atlassian servers**. It declares no external-fetch permission and uses only the Jira API and Forge storage. * Your data **never leaves Atlassian's infrastructure**. ### What the vendor can and cannot access * We **cannot access your Jira site or your business data**. We have no credentials to your instance and no way to read your issues, comments or content. * What we do see: **aggregated installation metrics** (such as number of installs) and **Forge production logs and error metrics** for the app, used only to detect and fix problems. These logs contain app error telemetry, not your business content. ### Support without accessing your data * When something fails, we diagnose it using **Forge's production logs and error metrics** in the developer console. These show the technical error, not your data. * We reproduce issues in our own environment to confirm a fix. We do **not** need access to your tickets or data to support you. ### Permissions Hiera requests the **minimum Jira scopes** it needs to work: reading work items, issue details, fields, projects, users, link types and boards; updating work items only for the date, link and hierarchy changes you make; and app storage. It declares no external-fetch permission. All scopes are listed on the Marketplace listing and were reviewed by Atlassian as part of approval. ### Data on uninstall Uninstalling Hiera removes the app and its Forge-stored data. Your **native Jira data is unaffected**, because Hiera never modified it. ### Questions For any security or privacy question, contact us at ****. See also our Terms of Service. Hiera runs on Atlassian Forge, so security and privacy are built into the platform. This page explains where your data lives, what we can and cannot access, and how we provide support without touching your business data. * Hiera is a **Forge app**: it runs inside Atlassian's cloud infrastructure, within your own Jira site. There is no Hiera-hosted backend. * Your **native Jira data** stays in Jira. Hiera reads issue data such as fields, statuses, dates, and links through Atlassian's official APIs. It does not copy that data anywhere else. * Hiera's **app data** — including the strategic hierarchy, Strategic Parents, view preferences, and work plans — is stored in **Forge storage scoped to your site**. * We **cannot access your Jira site or your business data**. We do not have credentials to your instance and cannot browse your issues, projects, or content. * We also do **not** read issue comments or attachments as part of Hiera's normal operation. * What we can see is limited to **aggregated installation metrics** and **Forge production logs and error metrics** used to detect and fix app problems. These logs contain technical telemetry, not your business content. * When something fails, we diagnose it with **Forge production logs and error metrics** in the developer console. These show the technical error, not your data. * We reproduce issues in our own environment to confirm a fix. We do **not** need access to your tickets or project data to support you. * Hiera requests the **minimum Jira scopes** it needs to work, including reading and updating work items for dates, links, and hierarchy, plus app storage. * Atlassian reviews these scopes as part of Marketplace approval. * Uninstalling Hiera removes the app and its Forge-stored data. * Your **native Jira data remains in Jira**. * Existing Jira data is unaffected by uninstall. For any security or privacy question, contact us at [**shv.support@germanmorales.org**](mailto:shv.support@germanmorales.org). See also our [Terms of Service](/hiera-docs/terms-of-service.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hiera.gitbook.io/hiera-docs/security-and-data-privacy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.