Professional Calendar Visual

Effective Date: March 2026 Last Updated: March 2026 Developer: Abdalla Dabes, P.E., PSP, PMP

INTRODUCTION

This Privacy Policy explains how the Professional Calendar 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 information outside your Power BI environment.

DATA COLLECTION AND USAGE

What Data the Visual Accesses

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

Calendar Data Fields: Start Date, End Date, Event Title, Event Category, Event Value, Holiday Date, and Holiday Name values mapped by you from your Power BI data model
Format Settings: All visual formatting choices (colors, font sizes, holiday display style, view mode defaults, axis settings, header options, etc.) configured through the Format pane
Interaction State: Selected events, active view mode, current navigation position, and cross-filter selection state during the active session

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, event titles, 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:

Calendar rendering, event bar layout, and holiday display are computed client-side from your mapped fields
Cross-filtering and selection state are managed using Power BI's native ISelectionManager API, entirely within the Power BI sandbox
No project data, event information, or schedule details leave your Power BI tenant or organization boundaries
Format settings and visual state are stored using Power BI's built-in property persistence mechanism

No External Connections

The Professional Calendar 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.

DATA STORAGE

Visual Format Settings

All formatting configurations (colors, holiday display style, view mode, header options, event bar settings, etc.) are stored within your Power BI report using Microsoft's native property persistence framework. These settings:

Persist with the report file indefinitely
Are included in report exports, migrations, and shared workspaces
Are cleared when the visual is removed from the report

Event and Holiday Data

Your calendar data (event titles, dates, categories, holiday names, etc.) 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 beyond Power BI's standard model caching.

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

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

Calendar and schedule data may include commercially sensitive or confidential project information. Because the Visual makes no external connections and all processing is local, your event and schedule data never leaves your Power BI environment through this Visual.

For reports containing sensitive calendar data, we recommend: ✓ Configuring appropriate Power BI workspace permissions and RLS ✓ 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.

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 geolocation, mapping, or tile services are used

USER RIGHTS AND CONTROL

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

Modify Fields: Change, remove, or replace any mapped data fields at any time through the Fields pane
Reset Settings: Return all formatting to defaults by deleting and re-adding the visual, or through the Format pane
Delete Visual: Remove the visual from a report to clear all stored format settings associated with it
Export: Standard Power BI export functions work with the visual
Permissions: Use Power BI workspace permissions and RLS to control who can view reports containing the visual

INTERNATIONAL DATA TRANSFERS

The Professional Calendar Visual 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 or calendar events occurs through this Visual.

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.

GDPR (EU General Data Protection Regulation) ✓ No personal data collected or processed ✓ No cross-border data transfers by the Visual ✓ User control and deletion rights fully supported ✓ Data minimization principles followed

CCPA (California Consumer Privacy Act) ✓ No sale or sharing of personal information ✓ Transparent data practices ✓ User rights respected

SOX (Sarbanes-Oxley Act) ✓ Data integrity through Power BI's native persistence ✓ Audit trail via Power BI's native logging (not the Visual) ✓ No external manipulation of project or schedule data

HIPAA Not applicable — the Visual is designed for project schedule and event data, not protected health information.

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

DATA FLOW SUMMARY

Fields Mapping — You map event and holiday data columns from your Power BI model to the Visual's data roles in the Fields pane
Data Query — Power BI queries your data model and passes values to the Visual at render time
Local Compute — The Visual resolves event layouts, holiday markers, date ranges, and cross-filter state client-side
Rendering — Calendar grid, event bars, holiday indicators, and header controls rendered entirely within the Power BI visual sandbox
Settings Save — Format pane settings stored in the Power BI report using Microsoft's property persistence
No Transmission — No project data, event details, or user information leaves your Power BI environment

External connections: None Analytics services: None Data sent to developer: None

Changes to this policy will be communicated through Visual version release notes and updated documentation. Material changes to data handling will be highlighted and users notified. The core principle — no collection or external transmission of any user or project data — will not change.

CONTACT

For privacy questions or data handling inquiries:

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