Project Templates for Jira privacy notice
Read these app-specific details alongside the company Privacy Policy.
Last updated: October 23, 2026.
AvanSaber Inc. publishes Project Templates for Jira. This app-specific notice is read alongside the AvanSaber privacy policy. Contact [email protected] about app privacy or security.
Platform and purpose
The app uses Atlassian Forge hosting, SQL and events, together with native Jira and Atlassian APIs. The current app has no external backend or external analytics or AI service for processing work-item content. Public website analytics are separate and follow this website’s consent and privacy controls.
Processing supports capture of accessible work, private revisions, resolved plans, authorised creation and recovery, receipts, access checks, maintenance and privacy requests. A user or organisation remains responsible for authority to process its Jira work and for personal information entered into that work.
Information processed
The app processes accessible work-item, project and type IDs and keys; summaries; supported descriptions; parent relationships; due dates; field configuration; and values supplied for a run. Work text can itself contain personal or confidential information.
Stored records include private revisions, initiating account IDs, resolved responsibility-role account IDs, frozen creation plans and operational intent or receipt state. Person display names are retrieved for the current picker; they are not stored as a separate profile directory.
Access and recipients
Reads and writes use the initiating Jira account with current permissions. Templates and runs are bound to their creator, environment and installation. Issue links and receipts are authorised again when requested. Native offline impersonation lets queued work continue as that initiating account after the browser closes; it is not an administrator fallback.
Atlassian supplies the Forge and Jira platform processing. AvanSaber is responsible for the app’s processing and support. Hosting on Forge does not mean the app processes no personal information, is certified for every regulation or removes the publisher’s privacy responsibilities.
Do not include unnecessary sensitive information in template text or support messages. Protect exports you save outside the app. A receipt already prepared in the browser or downloaded cannot be remotely erased from your copy by later access revocation.
Data residency scope
In scope: private template content, captures, previews, run plans, owner and mapped account IDs, and operational attempt and receipt records persisted in Forge SQL.
Out of scope for this app’s storage-residency commitment: transient compute, platform operational logs, customer-downloaded CSV files, separate support correspondence and this marketing website.
Forge SQL follows the host Jira app’s supported Atlassian residency location. Atlassian manages storage pinning and migration with the host app; no separate region setting is required in Project Templates for Jira. Forge compute can execute in another location. See Atlassian’s Forge data residency documentation.
Retention and privacy reporting
Unsaved captures expire after thirty minutes. Frozen previews are valid for ten minutes. Daily maintenance removes eligible expired captures and previews, and run content after ninety days from creation. Private revisions remain until erasure or a relevant privacy update.
The official Atlassian privacy-reporting flow checks stored account references on a seven-day cycle. Closure or update requests remove affected stored content. An uncertain dispatch can retain a minimal, content-free operational quarantine to prevent the app from blindly repeating a create; support reconciliation may be required.
Export, erasure and uninstall
Users can export their private revision content and prepare currently authorised run receipts. My app data offers exact-phrase erasure, which is blocked while the user’s work is active or uncertain. App erasure does not delete existing native Jira work items.
Uninstall retention and any recovery or relink process follow applicable Atlassian policy. We do not promise immediate physical destruction of every platform copy or automatic restoration after reinstall.
Contact support for privacy requests or unresolved recovery, sharing only necessary identifiers through an appropriate process. The company policy provides general rights and request information. We update this notice when processing changes and provide meaningful notice where required.