Updated 8 November 2026 · Project contact: Doron Ben David
The installed Atlassian app
DecisionGuard connects registered Confluence decisions to Jira work. Its application functions and persistent data run on Atlassian Forge. Your organization controls access to its Jira projects and Confluence pages.
When you use the app, it reads the projects, work items, source pages and profile information needed for the requested operation. Content reads use your Atlassian permission context. Optional Rovo reviews use Atlassian’s Rovo service and its applicable policies.
Information the app stores
- Registered decision titles, selected source passages, page identifiers and versions, project scope, rule configuration and timestamps.
- Review reasons, work-item references, material work snapshots that bind a review to the work and decision being reviewed, temporary exception details, and review history.
- Owner and reviewer attribution: an Atlassian account ID, display name and profile-retrieval timestamp. Business records use separate internal profile references.
- Comment identifiers for avoiding duplicate review requests, and content-free work-change timestamps that expire after seven days.
Registered passages, work snapshots and review notes may themselves contain information entered by your team. Do not treat archiving as deletion: archiving stops a decision’s checks and keeps its history.
Account privacy updates and your controls
The app periodically reports stored account IDs and profile-retrieval times to Atlassian’s personal data reporting API. It uses the responses to refresh invalidated profile information or remove closed-account attribution. Reporting and cleanup work is checkpointed for retry.
Inside the installed app, open How it works → Your stored attribution to remove your stored name and account reference from existing DecisionGuard attribution. Existing records then show “Former team member.” A future saved action can record fresh attribution.
This control preserves decision passages, rule definitions and review notes. Contact your workspace administrator and the project contact below to request correction or erasure of personal information contained in that business content.
Hosting, access and retention
DecisionGuard uses Forge-hosted storage. It does not configure a separate external application database, advertising service or model API. Its permission checks limit returned content to the requesting user’s accessible work and source pages.
Decision and review records are retained for workspace history unless removed through an authorized data-removal request. Atlassian governs storage retention and deletion following uninstallation under its Forge-hosted storage lifecycle. Atlassian’s own Privacy Policy applies to its platform.
The public browser demo
The website demo uses sample data stored in your browser’s local storage. It does not connect to live Jira, Confluence or Rovo. Resetting the demo replaces its sample workspace; clearing this site’s browser storage removes the locally saved demo data.
The website host may retain ordinary web-access logs. Downloaded evidence reports are saved by your browser. Treat any content you choose to enter or export according to your organization’s rules.
Questions and requests
For DecisionGuard support or a privacy request, contact doron@dreamview.co.il. Include the relevant Atlassian site and enough detail to identify the request. Keep passwords, API tokens and verification codes out of support messages.