PRO TREND LINE CHART

Effective Date: March 2026 · Last Updated: March 2026

Abdalla Dabes, P.E, PSP, PMP

Abdalla AI Solutions

AbdallaDabes@AbdallaAIsolutions.onmicrosoft.com

1. Introduction

This Privacy Policy explains how the Pro Trend Line Chart custom visual for Microsoft Power BI ('the Visual') handles data and protects user privacy. We are committed to complete transparency: the Visual does not collect, transmit, or store any personal or project data outside your Power BI environment.

Core Privacy Commitment

The Pro Trend Line Chart makes NO external network connections.

NO project data, cost figures, or user information ever leaves your Power BI environment.

ALL computation and rendering are fully self-contained within the Power BI visual sandbox.

2. Data Collection and Usage

2.1 What Data the Visual Accesses

The Visual only processes data you explicitly provide through the Power BI Fields pane:

• Data Role Values — Time Axis, Actual Units, Planned / Estimated Units, Remaining Units, and Tooltip measures mapped from your Power BI data model

• Format Settings — All visual formatting choices (colors, line widths, curve style, axis settings, analysis panel configuration, etc.) made through the Format pane

• Interaction State — Analysis Panel open/closed state, crosshair position, and selection state during the active session

2.2 What Data We Do NOT Collect

✗ No personal information of any kind

✗ No user behaviour 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, planned/actual values, or cost figures sent externally

✗ No background syncing or hidden data operations

3. Data Processing

3.1 Local Processing Only

All data processing occurs entirely within your Power BI environment:

• Statistical calculations (averages, variance, achievement rate, rolling average, anomaly detection, regression forecast) are computed client-side from your mapped fields

• Chart rendering is performed by the D3.js library (v7.9.0) running locally within the Power BI visual sandbox

• No project data, planned/actual values, or statistics ever leave your Power BI tenant or organization boundaries

• Format settings and visual state are stored using Power BI's built-in property persistence mechanism

• The isFiltered / ghost-layer logic for cross-visual filtering is computed entirely in-memory at render time

3.2 No External Connections

The Pro Trend Line Chart makes zero external network connections. It does not load map tiles, web fonts, analytics scripts, CDN assets, or any remote resources. All computation and rendering are fully self-contained.

External Connections

External connections: None

Analytics services: None

CDN dependencies: None (D3.js is bundled in the .pbiviz)

Data sent to developer: None

4. Data Storage

4.1 Visual Format Settings

All formatting configurations are stored within your Power BI report using Microsoft's native property persistence framework. These settings:

• Persist indefinitely with the report file

• Are included in report exports, migrations, and shared workspaces

• Are cleared when the visual is removed from the report

4.2 Chart Data

Your time-series data (Actual Units, Planned Units, Remaining Units) resides in your Power BI data model and is governed by your organization's Power BI configuration and data policies. The Visual reads this data for rendering only — it does not create copies, cache values to external locations, or retain data between sessions.

4.3 No External Storage

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

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

✗ Temporary in-memory data used during rendering is released automatically when the visual re-renders or is removed

5. Data Security

5.1 Security Measures

✓ 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 and certification requirements

✓ No additional authentication or data access beyond what Power BI grants to the visual

✓ Cross-visual filtering logic reads only the highlights[] array provided by the Power BI host — no direct data access

5.2 Sensitive Project Data

Planned and actual performance data is often commercially sensitive. 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 data, we recommend:

✓ Configure appropriate Power BI workspace permissions and Row-Level Security

✓ Review sharing settings before distributing reports externally

✓ Follow your organization's data classification policies

✓ Apply Power BI sensitivity labels where required by your organization

6. Third-Party Services

6.1 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 security and privacy protections.

6.2 D3.js Chart Library

• Open-source JavaScript visualization library (v7.9.0), MIT licensed

• Bundled inside the .pbiviz file — loaded locally, not from a CDN

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

• No external data transmission, analytics, tracking, or telemetry

6.3 No Other Third Parties

✗ No external APIs, services, or platforms integrated

✗ No analytics platforms, tracking scripts, or remote assets loaded

✗ No geolocation, mapping, or tile services used

7. User Rights and Control

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

Right

How to Exercise

Modify Fields

Change, remove, or replace any mapped data field at any time through the Fields pane

Reset Settings

Return all formatting to defaults by deleting and re-adding the visual, or adjust individual settings via the Format pane

Delete Visual

Remove the visual from the report to clear all stored format settings associated with it

Export Data

Standard Power BI export functions (Export data, see underlying data) work with the visual

Control Access

Use Power BI workspace permissions and Row-Level Security to control who can view reports containing the visual

8. International Data Transfers

The Pro Trend Line Chart does not transfer any data internationally. All processing occurs within your local Power BI environment. Data residency follows your Power BI tenant configuration. No cross-border data transmission of project data occurs through this Visual.

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

Compliance Notes

GDPR

No personal data collected or processed. No cross-border data transfers. User control and deletion rights fully supported. Data minimization principles followed.

CCPA

No sale or sharing of personal information. Transparent data practices documented. User rights respected.

SOX

Data integrity through Power BI's native persistence. No external manipulation of financial or project data. Audit trail via Power BI's native logging (not the Visual).

HIPAA

Not applicable — the Visual is designed for project performance data, not protected health information.

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

10. Data Flow Summary

1. Fields Mapping

You map time-series columns from your Power BI model to the Visual's data roles in the Fields pane

2. Data Query

Power BI queries your data model and passes values to the Visual at render time via the dataView API

3. Local Compute

The Visual calculates statistics, variance, rolling average, anomaly flags, and forecast projections client-side

4. Rendering

Chart, axes, variance band, data points, analysis panel, and sparkline rendered entirely within the Power BI visual sandbox using D3.js

5. Filtering

Cross-visual filter highlights[] array is read from the Power BI host to partition data into active and ghost layers — no external call

6. Settings Save

Format pane settings stored in the Power BI report file using Microsoft's property persistence — no external storage

7. No Transmission

No project data, statistics, or user information leaves your Power BI environment at any step

11. Privacy Policy Updates

Changes to this policy will be communicated through Visual version release notes and updated documentation. Material changes to data handling practices will be highlighted in the changelog and users notified.

The core principle — no collection or external transmission of any user or project data — will not change.

12. Contact

For privacy questions or data handling inquiries:

Developer: Abdalla Dabes, P.E, PSP, PMP

Organization: Abdalla AI Solutions

Email: AbdallaDabes@AbdallaAIsolutions.onmicrosoft.com

Privacy Inquiries: Response within 2 business days

Compliance Support: Available for enterprise requirements

13. Disclaimer

The Visual is provided 'as-is.' Security of your project 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. Users are responsible for ensuring appropriate access controls are in place before distributing reports containing sensitive data.

Pro Trend Line Chart · Privacy Policy v1.0 · Abdalla Dabes, P.E, PSP, PMP · March 2026

This Privacy Policy applies specifically to the Pro Trend Line Chart for Microsoft Power BI. For information about Microsoft Power BI’s own privacy practices, refer to Microsoft’s Privacy Statement.