PRIVACY POLICY

P6 Resource Histogram  —  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 P6 Resource Histogram Visual for Microsoft Power BI ("the Visual") handles data and protects your privacy. We are committed to 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:

•      Excel file data loaded manually via the Open File button (Activity IDs, Resource Names/IDs/Types, unit values, and date columns)

•      Power BI field values mapped through the Fields pane (Activity ID, Resource ID/Name/Type, Data Date, Budgeted/Actual/Remaining Units)

•      Format settings configured through the Format pane (colors, bar types, axis widths, filter visibility, etc.)

•      Interaction state during the active session (active filter selections, timescale, filter bar values)

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, resource units, or cost figures sent externally

✓  No background syncing or hidden data operations

Data Processing

Local Processing Only

All data processing occurs entirely within your Power BI environment:

•      Excel parsing is performed client-side using the SheetJS (xlsx) library running within the Power BI visual sandbox

•      Chart rendering is performed by the visual's SVG engine running locally — no external chart service is used

•      Filter aggregations and timescale calculations are computed in-memory from the loaded data

•      No project data, resource names, or unit values leave your Power BI tenant or organization boundaries

•      Format settings and persisted Excel data are stored using Power BI's built-in property persistence mechanism

No External Connections

The P6 Resource Histogram Visual makes no external network connections. It does not load map tiles, fonts, analytics scripts, or any remote resources. All computation and rendering are fully self-contained within the visual sandbox.

Data Storage

Visual Format Settings

All formatting configurations (colors, bar type, axis settings, filter visibility, etc.) are stored within your Power BI report using Microsoft's native property persistence framework. These settings persist with the report file and are cleared when the visual is removed.

Persisted Excel Data

When an Excel file is loaded, the parsed 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 be available to colleagues opening the shared .pbix file. The data is stored entirely within the report — not on external servers. Maximum stored data is approximately 6 MB.

No External Storage

✓  No data is stored on external servers, databases, or cloud services controlled by the developer

✓  No historical records, logs, or audit trails are maintained by the Visual

✓  Temporary in-memory data used during rendering is released automatically when the visual is destroyed

Data Security

Security Measures

•      The Visual operates within Power BI's sandboxed visual security framework

•      No network transmission of any project or user data

•      Access controlled entirely by Power BI's permission system (including Row-Level Security)

•      Follows Microsoft Power BI custom visual security standards

•      No additional authentication or data access beyond what Power BI grants

Sensitive Project Data

P6 resource loading data may include commercially sensitive schedule and cost information. Because the Visual makes no external connections and all processing is local, your project data never leaves your Power BI environment through this Visual.

For reports containing sensitive P6 data, we recommend:

✓  Configuring appropriate Power BI workspace permissions

✓  Reviewing sharing settings before distributing reports externally

✓  Following your organization's data classification policies

✓  Applying Power BI sensitivity labels where required

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 is governed by your organization's Power BI configuration and Microsoft's security and privacy protections.

SheetJS (xlsx) — Excel Parsing Library

•      Open-source JavaScript library for reading Excel files

•      Runs entirely client-side within the Power BI visual sandbox

•      No external data transmission

•      No analytics, tracking, or telemetry

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

✓  No mapping, geolocation, or tile services are used

Data Flow Summary

Step

Stage

What Happens

1

File Selection

User selects a P6 Excel file; read locally by the browser

2

Local Parsing

SheetJS parses the file in-memory within the visual sandbox

3

Persistence

Parsed data serialized into Power BI report via persistProperties

4

Filter & Render

Visual filters data and renders SVG chart locally — no server calls

5

Settings Save

Format pane settings stored in the Power BI report file

6

No Transmission

No project data, resource names, or metrics leave the PBI 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 minimization principles followed

CCPA

✓ No sale or sharing of personal information  •  ✓ Transparent data practices  •  ✓ User rights respected

SOX

✓ Data integrity through Power BI's native persistence  •  ✓ No external manipulation of project data

HIPAA

Not applicable — Visual is designed for project schedule data, not protected health information

Note: Organizational compliance remains the responsibility of your organization. Assess Visual usage within your specific regulatory requirements.

User Rights and Control

You maintain complete control over all data associated with this Visual:

Modify Data

Change, remove, or replace the loaded Excel file or any mapped fields at any time

Clear Data

Click the Clear button in the toolbar to erase loaded data from memory and from the persisted report file

Reset Settings

Delete and re-add the visual, or use the Format pane reset options, to restore default settings

Delete Visual

Remove the visual from a report to clear all associated format settings and persisted data

Permissions

Use Power BI workspace permissions and RLS to control who can view reports containing the visual

Contact

Developer

Abdalla Dabes, P.E, PSP, PMP

Email

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 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.