PRIVACY POLICY
P6 XER Portfolio Analyzer — Power BI Custom Visual
Effective Date: April 2026 | Last Updated: April 2026 | Developer: Abdalla Dabes, P.E, PSP, PMP
Introduction
This Privacy Policy explains how the Pro XER Analysis Visual for Microsoft Power BI (“the Visual”) handles data and protects your privacy. We are committed to full transparency: the Visual does not collect, transmit, or store any personal or project information outside your Power BI environment.
Data Collection and Usage
What Data the Visual Accesses
The Visual only processes data that you explicitly provide:
• XER file content imported via the Import XER File button (WBS names, activity IDs, task names, task types, durations, dates, float values, resource assignments, and calendar definitions)
• Power BI field values mapped through the Fields pane (XER Files, Project Name, XER File Name)
• Format pane settings configured by the user (colors, column widths, DCMA thresholds, font options, etc.)
• Interaction state during the active session (active filter selections, active panel, expand/collapse state)
What Data We Do NOT Collect
✓ No personal information of any kind
✓ No user behavior analytics or usage tracking
✓ No transmission of data to external servers or third parties
✓ No cookies, browser history, or device information
✓ No IP addresses or system specifications
✓ No project data, activity names, cost figures, or schedule dates sent externally
✓ No background syncing or hidden data operations of any kind
Data Processing
Local Processing Only
All data processing occurs entirely within your Power BI environment:
• XER file parsing is performed client-side within the Power BI visual sandbox using a built-in JavaScript XER parser — no external parsing service is used
• Chart rendering, table building, Gantt timeline computation, and DCMA metric calculation are all performed locally by the visual’s rendering engine
• Filter aggregations and hierarchy traversal are computed in-memory from the loaded XER data
• No project data, WBS names, activity IDs, or schedule metrics leave your Power BI tenant or organization boundaries
• Format settings and persisted XER data are stored using Power BI’s built-in property persistence mechanism (persistProperties API)
No External Connections
The Pro XER Analysis Visual makes no external network connections whatsoever. It does not load fonts, analytics scripts, map tiles, CDN resources, or any remote assets. All computation and rendering are fully self-contained within the Power BI visual sandbox.
Data Storage
Visual Format Settings
All formatting configurations (colors, column widths, DCMA thresholds, font settings, etc.) are stored within your Power BI report file using Microsoft’s native property persistence framework. These settings persist with the report file and are permanently cleared when the visual is removed from the report.
Persisted XER Data
When an XER file is imported via the Import button, the parsed schedule data is serialized and stored inside the Power BI report file using Power BI’s persistProperties API. This allows the data to survive page navigation and to be available to colleagues opening the shared .pbix report. The data is stored entirely within the report — not on any external server. Maximum persisted data is approximately 15 MB (50 chunks × 300 KB each).
No External Storage
✓ No data is stored on external servers, databases, or cloud services controlled by the developer
✓ No historical records, access logs, or audit trails are maintained by the Visual
✓ Temporary in-memory data used during rendering is released automatically when the visual is destroyed or the report is closed
Data Security
Security Measures
• The Visual operates within Power BI’s sandboxed custom visual security framework
• No network transmission of any project, schedule, or user data under any circumstances
• Access is controlled entirely by Power BI’s permission system, including Row-Level Security (RLS)
• Follows Microsoft Power BI custom visual security standards and certification requirements
• No additional authentication or data access beyond what Power BI explicitly grants
Sensitive Project Data
XER schedule data may include commercially sensitive project names, activity descriptions, resource assignments, cost figures, and schedule logic. Because the Visual makes no external connections and all processing is strictly local, your project data never leaves your Power BI environment through this Visual.
For reports containing sensitive P6 schedule data, we recommend:
✓ Configuring appropriate Power BI workspace and dataset permissions
✓ Reviewing sharing and distribution settings before sending reports externally
✓ Following your organization’s data classification and handling policies
✓ Applying Power BI sensitivity labels where required by your organization
Third-Party Services
Microsoft Power BI
The Visual operates as a component within Microsoft Power BI and is subject to Microsoft’s Privacy Policy and Terms of Service. Data handling within the Power BI platform is governed by your organization’s Power BI configuration and Microsoft’s own security and privacy protections.
No Other Third Parties
✓ The Visual does not integrate with any external APIs, services, or platforms
✓ No analytics platforms, tracking scripts, CDNs, or remote assets are loaded at any time
✓ No mapping, geolocation, charting services, or AI inference APIs are used
✓ All chart rendering, table layout, and Gantt computation are performed by native browser SVG and JavaScript — no third-party chart library makes external calls
Data Flow Summary
Step
Stage
What Happens
1
File Selection
User selects a .xer file; read locally by the browser file API
2
Local Parsing
Built-in XER parser processes the file in-memory within the visual sandbox
3
Persistence
Parsed data chunked and stored in the Power BI report via persistProperties
4
Filter & Render
Visual applies filters and renders the active panel (Overview / Gantt / Dashboard / DCMA) locally — no server calls
5
Settings Save
Format pane settings stored in the Power BI report file on every change
6
No Transmission
No project data, activity names, schedule dates, or metrics ever leave the Power BI environment
External connections: None | Analytics services: None | Data sent to developer: None
Regulatory Compliance
The Visual is designed to support compliance with applicable data protection regulations. Because no personal data is collected or transmitted, compliance obligations introduced by the Visual itself are minimal.
Regulation
Notes
GDPR
✓ No personal data collected or processed • ✓ No cross-border data transfers • ✓ Data minimisation principles followed
CCPA
✓ No sale or sharing of personal information • ✓ Transparent data practices • ✓ User rights fully respected
SOX
✓ Data integrity through Power BI’s native persistence • ✓ No external manipulation of project or schedule data
HIPAA
Not applicable — Visual is designed exclusively for Primavera P6 project schedule data, not protected health information.
Organizational compliance remains the responsibility of your organization. Please assess Visual usage within your specific regulatory and contractual requirements.
User Rights and Control
You maintain complete control over all data associated with this Visual:
Right / Action
How to Exercise It
Modify Data
Change, remove, or replace the imported XER file or any mapped Power Query fields at any time
Clear Data
Click the ‘✕ Clear imported file’ link in the header bar to erase loaded data from memory and from the persisted report storage
Reset Settings
Delete and re-add the visual, or use Format pane defaults, to restore all settings to their factory values
Delete Visual
Remove the visual from the report canvas to permanently clear all associated format settings and persisted XER data
Permissions
Use Power BI workspace permissions and Row-Level Security (RLS) to control who can view reports containing the visual
Contact
Developer
Abdalla Dabes, P.E, PSP, PMP
AbdallaDabes@AbdallaAIsolutions.onmicrosoft.com
Organization
Abdalla AI Solutions
Privacy Inquiries
Response within 2 business days
Compliance Support
Available for enterprise requirements
Disclaimer
The Visual is provided “as-is.” Security of your P6 schedule data depends on proper Power BI configuration and your organization’s security policies. The developer is not liable for unauthorized access resulting from misconfigured Power BI permissions or inappropriate sharing of reports containing sensitive project data. Users are responsible for ensuring appropriate access controls are in place before distributing reports containing XER data.