Kml / Kmz files viewer Visual

Effective Date: February 2026

Last Updated: February 2026

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

Introduction

This Privacy Policy explains how the KML/KMZ Viewer Visual for Microsoft Power BI ("the Visual") handles data and protects your privacy. We are committed to transparency and protecting your information.

Data Collection and Usage

What Data the Visual Accesses

The KML/KMZ Viewer Visual only accesses data that you explicitly provide:

• Geospatial Files: KML and KMZ files you upload directly to the visual for map display

• Feature Customizations: Colors you assign to points, lines, and polygons

• Visibility Settings: Show/hide states for individual features

• Map Configuration: Selected map type (Street, Satellite, Terrain, etc.)

• View Settings: Zoom level, pan position, and map bounds

• Layer Panel State: Open/closed state and feature organization

• Appearance Settings: Line thickness, toolbar visibility, button visibility, colors, and font preferences

• Control Settings: Zoom enable/disable, pan enable/disable, control visibility preferences

What Data We Do NOT Collect

• No Personal Information: The visual does not collect, store, or transmit any personal information

• No User Analytics: We do not track user behavior, usage patterns, or viewing analytics

• No External Transmission: No data is sent to external servers or third parties

• No Browser Data: We do not access cookies, local storage (beyond Power BI's framework), or browser history

• No System Information: We do not collect device information, IP addresses, or system specifications

• No Location Tracking: We do not track user's physical location or GPS coordinates

• No Geospatial Analysis: We do not analyze, index, extract, or monitor the content of your KML/KMZ files

• No Usage Metrics: We do not track which features are viewed, interaction patterns, or user engagement

• No Geographic Intelligence: We do not collect or analyze geographic data for any purpose beyond display

Data Processing

Local Processing Only

All data processing occurs locally within your Power BI environment:

• KML/KMZ parsing and feature extraction happen entirely within Power BI Desktop or Power BI Service

• Map rendering performed by Leaflet library client-side

• Geospatial content stored using Power BI's built-in property persistence mechanism

• No data leaves your Power BI tenant or organization boundaries

• All map display, navigation, and feature management functions are performed client-side

• Map tile loading uses publicly available tile servers (OpenStreetMap, Google) but does not transmit your KML data

Data Storage

KML/KMZ Files:

• Stored locally within your Power BI report using Microsoft's persistence framework

• Files under 30MB are embedded in the report permanently

• Files 30-200MB are session-only (not persisted beyond current session)

• Files over 200MB may experience performance issues but can be loaded

Feature Customizations:

• Feature colors stored within your Power BI report

• Visibility settings (show/hide) saved with the report

• All customizations persist with the report file

Map Settings:

• Selected map type persisted with report

• Line thickness setting saved

• Control configurations stored

• Appearance preferences retained

View State:

• Current map zoom and pan position may be saved

• Layer panel state (open/closed) persisted

• Feature bookmarks (fit to feature positions) stored

No External Storage:

• No data is stored on external servers, databases, or cloud services

• Temporary Processing: KML/KMZ data temporarily held in memory during parsing and display

• Object URLs: Temporary blob URLs created for file handling are automatically cleaned up and revoked

Data Security

Security Measures

• Power BI Security: The visual operates within Power BI's security framework

• No Network Transmission: No KML/KMZ content or user data transmitted to external services (except public map tiles)

• Isolation: The visual operates in isolation from other applications and services

• Standard Compliance: Follows Microsoft Power BI custom visual security standards

• Limited External Connections: Only connects to public map tile servers (OpenStreetMap, Esri, Google) for base map imagery

• Memory Management: Efficient processing to prevent memory-related security issues

• Data Integrity: Triple-backup persistence system ensures data integrity without external transmission

Access Control

• Data access controlled entirely by Power BI's permission system

• Users can only view maps within reports they have been granted access to

• The visual respects all Power BI row-level security (RLS) configurations

• No additional authentication or access control implemented by the visual

• KML/KMZ content visibility follows standard Power BI sharing and permission rules

• Embedded geospatial data subject to same security controls as the Power BI report

Third-Party Services

Microsoft Power BI

This visual operates as a component within Microsoft Power BI:

• Subject to Microsoft's Privacy Policy and Terms of Service

• Data handling governed by your organization's Power BI configuration

• Microsoft's security and privacy protections apply

• File persistence uses Power BI's native property storage

Map Tile Providers

The visual uses publicly available map tile services for base maps:

OpenStreetMap (Street Map):

• Open-source mapping project

• Tiles loaded from public servers

• No user data transmitted except tile requests based on map bounds

• Subject to OpenStreetMap's usage policies

Esri (Satellite View):

• Commercial satellite imagery provider

• Tiles loaded from Esri public servers

• No KML data or user information transmitted

• Standard tile service - anonymous requests

Google Maps (Satellite, Hybrid):

• Google's mapping service

• Tiles loaded from Google servers

• Tile requests only - no personal or KML data transmitted

• Subject to Google's mapping terms of service

Leaflet Library

• Open-source JavaScript mapping library

• Runs entirely client-side

• No external data transmission

• No analytics or tracking

No Other Third Parties

• The visual does not integrate with any other third-party services

• No external APIs or web services accessed beyond map tiles

• No external fonts, libraries, or resources loaded from remote sources during operation

• No geospatial analysis services contacted

• No CDN or external asset loading beyond map tiles

Data Retention

Visual-Specific Data

KML/KMZ Content:

• Retained within your Power BI report until manually removed or replaced

• Files under 30MB persist permanently with the report

• Files 30-200MB exist only during active session

• Automatic cleanup when visual is removed from report

Feature Customizations:

• Persist with the report indefinitely

• Can be reset by uploading new file or manually changing settings

• Cleared when visual is deleted

Map Settings:

• Current map type, line thickness, and configurations persist with report

• Can be modified at any time through Format pane

• Reset to defaults when visual is removed

View State:

• Current zoom and pan position may persist

• Layer panel state saved

• Cleared on session end or visual removal

No Historical Data:

• The visual does not maintain historical records, logs, viewing history, or version history

• No change tracking or audit trail (handled by Power BI if enabled)

Session Data:

• Temporary session data cleared when Power BI session ends

• Large files (30-200MB) cleared from memory on session end

Power BI Data

• Data retention managed by Power BI according to your organization's policies

• The visual does not influence or modify Power BI's data retention behavior

• Users can remove the visual and all associated data at any time

• Deleting the visual from a report removes all stored KML/KMZ content and settings

User Rights and Control

Data Control

You maintain complete control over your data:

• Upload/Replace KML/KMZ: Upload new files or replace existing ones at any time

• Delete Visual: Remove the visual and all associated content from reports

• Customize Features: Change colors, visibility, and appearance of all features

• Reset Settings: Return to default settings through Format pane

• Clear Data: Upload new file to clear previous data

• Configuration: Modify all visual settings through Power BI's formatting panel

• Export: Standard Power BI export functions work with the visual

• File Management: Full control over which files are uploaded and when

Transparency

• All visual functionality is transparent and configurable

• No hidden data processing or background operations

• Open communication about visual capabilities and limitations

• No automatic data collection or background syncing

• Clear file size limits and persistence behaviors communicated to users

• Warning notifications for large files

International Data Transfers

No Data Transfers

The KML/KMZ Viewer Visual does not transfer geospatial 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 KML/KMZ content by the visual

• Geospatial content remains within your organization's Power BI boundaries

• Map tiles loaded from public servers (may be international) but contain no user data

• Compliance with data sovereignty requirements depends on your Power BI configuration

Children's Privacy

General Use

The visual is designed for business and professional use:

• Not specifically designed for use by children under 13

• Does not collect personal information from any users, including children

• Parental controls managed through organizational Power BI policies

• Content appropriateness of uploaded KML/KMZ files is the responsibility of the user

• No targeted features or data collection aimed at children

Updates and Changes

• Changes to this privacy policy will be communicated through visual updates

• Significant changes will be highlighted in release notes and documentation

• Users can review the current policy at any time

• Material changes to data handling will require explicit user consent

• No changes to core privacy principles without notification

Visual Updates

• Visual updates may include new features but will not change core privacy principles

• No new data collection will be introduced without explicit user consent and notification

• Security improvements may be implemented transparently

• Map rendering and persistence mechanisms may be improved for performance

• Feature additions will maintain the same privacy-first approach

Compliance

Standards and Regulations

The visual is designed to support compliance with:

GDPR (European General Data Protection Regulation):

✓ No personal data collection

✓ User control over all data

✓ Right to deletion supported

✓ Data minimization principles followed

✓ Processing occurs locally (no cross-border transfers)

✓ Transparency in data handling

CCPA (California Consumer Privacy Act):

✓ No sale of personal information

✓ Transparent data practices

✓ User rights respected

✓ No sharing of geospatial data

SOX (Sarbanes-Oxley Act) - for applicable organizations:

✓ Data integrity through persistence system

✓ Audit trail through Power BI's native logging

✓ No external data manipulation

HIPAA (Health Insurance Portability and Accountability Act):

✓ Can be used with non-PHI geospatial content

✓ Organizations must ensure appropriate use

✓ No transmission of protected data

Organizational Compliance

• Compliance responsibility remains with your organization

• The visual supports but does not guarantee regulatory compliance

• Organizations should assess visual usage within their specific compliance requirements

• Users are responsible for ensuring uploaded KML/KMZ content complies with organizational policies

• IT departments should review data handling for alignment with corporate governance

Sensitive Content

User Responsibility

When using the KML/KMZ Viewer with sensitive or confidential geospatial content:

• Ensure appropriate access controls are configured in Power BI

• Follow your organization's content classification and handling policies

• Consider sensitivity of location data when sharing reports

• The visual does not provide additional encryption beyond Power BI's standard protections

• Review content for compliance with data protection regulations

• Consider national security implications of detailed geographic data

Recommendations

Do NOT upload KML/KMZ files containing:

✗ Classified or restricted location information

✗ Sensitive infrastructure locations (without authorization)

✗ Protected facility coordinates

✗ Personal home addresses or private locations

✗ Confidential business locations without proper security

✗ Military or security-sensitive geographic data

Best Practices:

✓ Review Power BI sharing settings before distributing reports containing maps

✓ Use Power BI's built-in security features (RLS, workspace permissions)

✓ Compress or simplify KML files to reduce data exposure

✓ Document geographic content and approval in accordance with organizational policies

✓ Consider using generalized locations rather than precise coordinates for sensitive data

✓ Apply appropriate access controls for reports containing location data

✓ Regular review of shared reports containing geospatial information

File Size and Persistence Privacy Implications

Data Persistence Tiers

Understanding how file size affects data retention:

Under 30MB (Full Persistence):

• KML/KMZ saved permanently in Power BI report

• Subject to Power BI backup and disaster recovery

• Included in report exports and migrations

• Remains accessible across all sessions

• Suitable for public or approved geospatial content

30-200MB (Session-Only Persistence):

• Data exists only while Power BI session is active

• Not saved in Power BI report file

• Must be re-uploaded each session

• Reduces long-term data storage and exposure

• Better for sensitive or temporary geographic data

Over 200MB (Performance Considerations):

• May experience slower loading

• Consider splitting into multiple files

• Assess necessity of detailed geographic data

Privacy Considerations

• Larger files (30-200MB) offer enhanced privacy through non-persistence

• Sensitive location data may benefit from session-only approach

• Permanent embedding (<30MB) suitable for public or approved geographic content

• Organizations can enforce size limits to control data retention and exposure

Contact Information

Privacy Questions

If you have questions about this privacy policy or the visual's data handling:

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

Email: AbdallaDabes@AbdallaAIsolutions.onmicrosoft.com

Organization: Abdalla AI Solutions

Support Response

• Privacy inquiries: Responded to within 2 business days

• Data handling questions: Detailed responses within 3 business days

• Compliance support: Available for organizational requirements

• Security assessments: Consultation available for enterprise deployments

Disclaimer

Limitation of Liability

• The visual is provided "as-is" without warranties regarding data security

• Users are responsible for appropriate data handling within their organizations

• Security depends on proper Power BI configuration and organizational policies

• KML/KMZ content security is the responsibility of the uploading user

• The developer is not liable for inappropriate use or data breaches resulting from organizational security misconfigurations

• Geographic data sensitivity assessment is user's responsibility

Best Practices

We recommend:

Security:

✓ Regular review of Power BI security settings

✓ Appropriate user training on geospatial data handling

✓ Regular updates to the visual for security improvements

✓ Network security for map tile requests

Content Management:

✓ Review of KML/KMZ content sensitivity before uploading to shared reports

✓ Simplification and compression of files to optimize performance

✓ Documentation of geographic content and approval workflows

✓ Regular audit of embedded location data

Compliance:

✓ Compliance with organizational data governance policies

✓ Assessment of regulatory requirements (GDPR, HIPAA, etc.)

✓ Regular audits of embedded geospatial content

✓ Consideration of data sovereignty and geographic restrictions

Performance:

✓ Use of recommended file sizes and formats

✓ Testing KML/KMZ files before embedding in production reports

✓ Monitoring of report performance with embedded maps

✓ Optimization of geospatial data complexity

Transparency Report

Data Flow Summary

1. Upload: User selects KML/KMZ file from local system

2. Processing: File parsed and features extracted locally

3. Storage: Geospatial data stored in Power BI properties (if <30MB) or session memory (if 30-200MB)

4. Display: Map rendered using Leaflet library client-side

5. Map Tiles: Base map images loaded from public tile servers (no user data transmitted)

6. Persistence: KML/KMZ and settings saved with Power BI report (if enabled and <30MB)

7. Deletion: User removes data by uploading new file or deleting visual

External Connections:

✓ Map tile servers (OpenStreetMap, Esri, Google) - for base map imagery only

✗ No user data transmission

✗ No analytics services

✗ No tracking services

✗ No third-party APIs beyond map tiles

Third-Party Services:

✓ Map tile providers (public servers, no user data)

✗ No analytics platforms

✗ No data processing services

✗ No external storage

Data Transmission:

✓ Map tile requests only (based on visible map bounds)

✗ No KML/KMZ content transmission

✗ No user information

✗ No tracking data

✗ No analytics data

Version History

Version | Date | Changes

--------|------|--------

1.0 | February 2026 | Initial privacy policy for KML/KMZ Viewer Visual

Document Version: 1.0

This privacy policy applies specifically to the KML/KMZ Viewer Visual for Power BI. For information about Microsoft Power BI's privacy practices, please refer to Microsoft's Privacy Statement.