Updated 11 September 2026. Provider: Noé Pérez Blanco, trading as NoeApps. Contact: support@noeapps.com.
Roles and purposes
NoeApps is responsible for its own data processing; Atlassian does not assume that responsibility for NoeApps. The apps process data on customer instructions to diagnose links, prepare repairs, and review or transfer responsibilities. The customer chooses spaces, projects, people, and domains. For customer content, NoeApps acts as a processor where applicable. The customer remains responsible for the legal basis, informing users, and authorizing operations. NoeApps acts as controller for support, security, and rights requests sent directly to it.
Data used by Leaver Guard
Leaver Guard uses account identifiers, visible names and active status, planned departure identifiers, metadata and owners of issues, projects, components, filters and dashboards, administrator and successor identifiers, and handover history. This supports reviewing responsibilities and verifying requested changes. The app does not request Atlassian passwords or personal tokens and does not use app content for advertising or AI model training.
Storage and recipients
Persistent operational state is stored in Atlassian Forge hosted storage, separated by installation and environment. Functions run on Forge and call Jira APIs. Atlassian supplies the app infrastructure. Leaver Guard declares no external network destinations in its app code.
The public documentation site is hosted on OpenAI Sites and includes a Google AdSense script. Visiting the site may send technical connection data to those providers. The website does not access Jira installation data or contain customer forms. Emails sent to NoeApps are handled through DonDominio and contain only the data supplied for the inquiry.
Location
Forge supports data storage in the United States, Australia, Canada, Germany, Ireland, India, Japan, Singapore, South Korea, Switzerland, and the United Kingdom, depending on supported locations and product configuration. The global option allows Atlassian to determine and change location. Function processing and technical logs may follow different rules from persistent storage. Leaver Guard's operational Forge state is the app data subject to residency. This candidate does not promise a fixed region or a PINNED badge. Check each installation in Atlassian administration and see Forge data residency. Support emails and visits to this website are not governed by an installation's Jira residency setting.
Retention and deletion
Reports, plans, and temporary records expire 30 days after writing or update. Operational previews expire earlier; Leaver Guard previews expire after 30 minutes. Forge physical expiry may be asynchronous. Configuration remains while the installation is used. Planned departure identifiers remain until removed by an administrator or an account-closure notice is processed.
A technical account registry supports Atlassian privacy reporting; exclusively transient references include up to 48 hours of grace for expiry. The apps poll Atlassian weekly for account privacy changes and run cleanup before uninstall. Platform limits or failures may delay cleanup; remaining data follows the Forge storage lifecycle. Changes already made in Jira and Jira history remain in the product after uninstall.
Rights and requests
Contact privacy@noeapps.com for applicable access, correction, deletion, restriction, or objection requests. For organization content, we work with its administrator to verify authorization and scope. You may complain to the competent data protection authority, including the Spanish Data Protection Agency. Support inquiries are used only to handle the request, legal obligations, and related incident resolution and can be deleted when no longer needed. Personal data is not sold. See the provider's legal notice and the data processing agreement.