PRIVACY POLICY FOR CUSTOM POWER BI VISUALS

Effective Date: 2026-04-16

Last Updated: 2026-04-16

1. INTRODUCTION AND SCOPE

1.1 Developer Identification

This Privacy Policy (“Policy”) is issued by Be On Purpose Corp (doing business as Be On) ("Developer," "we," "us," or "our"). This Policy governs the collection, use, processing, and disclosure of personal information in connection with the following Microsoft Power BI custom visuals developed by Be On: Grid Heatmap Pro, Timeline Pro, and Table Pro (collectively, the “Visuals” or individually, a “Visual”).

1.2 Jurisdiction and Applicable Laws

This Policy is governed by the laws of the State of Texas, and any disputes arising under this Policy shall be subject to the exclusive jurisdiction of the courts located in Harris County, Texas.

1.3 Purpose and Scope of Privacy Policy

This Policy describes our data collection, processing, and sharing practices in connection with the Visuals. The Visuals are designed exclusively for data visualization purposes within the Microsoft Power BI environment and are distributed through Microsoft AppSource. This Policy applies to all users who download, install, or use any of the Visuals, regardless of the method of acquisition. By using any of the Visuals, you acknowledge that you have read, understood, and agree to be bound by the terms of this Policy.

1.4 Transparency Notice Under Texas Law

In accordance with the TDPSA, we provide this transparency notice to inform Texas residents of our data processing practices. The Visuals are designed with privacy-by-design principles and do not collect, store, or transmit personal information beyond what is necessary for their core functionality within the Power BI environment.

2. DATA COLLECTION AND PROCESSING PRACTICES

2.1 No Data Collection Statement

WE DO NOT COLLECT ANY PERSONAL INFORMATION OR DATA FROM USERS OF THE VISUALS. The Visuals are designed to operate entirely within the Microsoft Power BI environment and do not collect, store, transmit, or otherwise process any personal information, user data, or usage analytics. This includes, but is not limited to, names, email addresses, IP addresses, device identifiers, location data, browsing history, or any other information that could be used to identify an individual user.

2.2 Data Processing Limitations Within Power BI

The Visuals process data solely for the purpose of creating visual representations within the Power BI environment. All data processing occurs locally within the user’s Power BI instance and is subject to Microsoft’s data handling and security protocols. The data processing performed by the Visuals is limited to:

  1. Rendering and Display Functions: Processing data provided by Power BI to generate charts, graphs, tables, and other visual representations as specified by the user’s configuration settings;

  2. Temporary Memory Usage: Temporarily storing data in local memory during the rendering process, with all such data being automatically cleared when the Visual is refreshed, updated, or when the Power BI session ends;

  3. User Interface Operations: Processing user interactions with the Visual interface, including clicks, selections, filtering, and sorting operations, all of which occur locally within the Power BI environment; and

  4. Performance Optimization: Implementing caching mechanisms and performance optimizations that operate exclusively within the local Power BI environment without transmitting data externally.

2.3 Configuration Data Handling

Users may configure various settings and parameters for the Visuals through the Power BI interface. These configuration settings are stored locally within the user’s Power BI environment and are not transmitted to, collected by, or accessible to the Developer. Configuration data may include:

  1. Visual Appearance Settings: Color schemes, fonts, sizing parameters, and layout preferences;

  2. Data Mapping Configurations: Field assignments, data source connections, and filtering criteria;

  3. Functional Parameters: Chart types, aggregation methods, sorting preferences, and display options; and

  4. User Preferences: Language settings, accessibility options, and other user-specific customizations.

All configuration data remains under the exclusive control of the user and is subject to Microsoft’s data governance policies rather than this Policy.

2.4 Error Handling and Logging

The Visuals utilize standard Power BI error messaging systems to communicate technical issues or configuration problems to users. No custom logging, error tracking, or diagnostic data collection is performed by the Visuals. Any error messages displayed are generated locally within the Power BI environment and do not result in data transmission to external servers or the Developer.

3. DATA SHARING AND THIRD-PARTY DISCLOSURE

3.1 Microsoft AppSource Relationship

The Visuals are distributed through Microsoft AppSource, Microsoft’s official marketplace for Power BI custom visuals. When users download or acquire the Visuals through AppSource, Microsoft may collect certain information about the transaction, including but not limited to user account information, download metrics, and usage statistics. This data collection is governed by Microsoft’s Privacy Policy, not this Policy. We recommend that users review Microsoft’s Privacy Policy to understand how Microsoft handles data collected through AppSource.

3.2 No External Data Transmission

THE VISUALS DO NOT TRANSMIT ANY DATA TO EXTERNAL SERVERS, THIRD-PARTY SERVICES, OR THE DEVELOPER. All data processing occurs locally within the user’s Power BI environment.

3.3 Third-Party Service Limitations

The Visuals are designed to operate in a completely self-contained manner within the Power BI environment. Users cannot configure the Visuals to connect to external data sources, web services, or third-party applications beyond those already integrated within their Power BI environment by Microsoft or other authorized providers.

3.4 Microsoft Data Collection

While the Developer does not collect any data through the Visuals, Microsoft may collect information related to the download, installation, and usage of the Visuals through AppSource and the Power BI platform. Such data collection is subject to Microsoft’s privacy policies and terms of service, which users should review independently. The Developer has no access to, control over, or responsibility for any data collected by Microsoft in connection with the Visuals.

6. DATA SECURITY AND RETENTION

6.1 Security Infrastructure Reliance

The security of data processed by the Visuals relies entirely on Microsoft Power BI’s security infrastructure and protocols. The Visuals do not implement independent security measures, as all data processing occurs within the secure Power BI environment.

6.2 No Data Retention Policy

THE VISUALS DO NOT RETAIN ANY DATA BEYOND THE IMMEDIATE PROCESSING SESSION. All data processing is temporary and occurs only during active use of the Visuals. o

6.3 Temporary Processing Procedures

During active use, the Visuals may temporarily process data in the following manner:

(a)      Data Ingestion: Receive data from Power BI’s data model for visualization purposes;

(b)     Processing Operations: Perform calculations, aggregations, filtering, and formatting operations necessary for visual representation;

(c)      Rendering Activities: Generate visual elements, charts, graphs, and interactive components based on the processed data;

(d)     User Interaction Handling: Process user interactions such as clicks, selections, and configuration changes; and

(e)      Immediate Cleanup: Automatically clear all processed data from memory upon completion of rendering or user interaction.

7. THIRD-PARTY LINKS AND SERVICES

7.1 External Link Disclaimer

The Visuals do not contain links to external websites, third-party services, or external resources. However, this Policy or related documentation may contain references to third-party websites, including Microsoft’s privacy policies, AppSource terms of service, or other relevant resources. These references are provided solely for informational purposes.

7.2 Responsibility Limitations

WE ASSUME NO RESPONSIBILITY FOR THE CONTENT, PRIVACY POLICIES, OR PRACTICES OF ANY THIRD-PARTY WEBSITES OR SERVICES. This includes, but is not limited to:

  1. Microsoft Services: While the Visuals operate within the Microsoft Power BI environment, we are not responsible for Microsoft’s data collection, processing, or security practices;

  2. External Resources: Any third-party websites, documentation, or resources referenced in connection with the Visuals are beyond our control and responsibility;

  3. User Navigation: If users navigate to third-party websites from documentation or support materials related to the Visuals, such navigation is at the user’s own risk;

  4. Third-Party Policies: Users are responsible for reviewing and understanding the privacy policies and terms of service of any third-party services they choose to use in connection with their Power BI environment; and

  5. Data Sharing: Any data sharing that occurs between Power BI and third-party services is governed by Microsoft’s policies and the user’s configuration choices, not this Policy.

7.3 Microsoft Power BI Integration

The Visuals are designed to integrate seamlessly with Microsoft Power BI and rely on Power BI’s existing infrastructure for all functionality. This integration means that:

  1. Platform Dependency: The Visuals’ operation is entirely dependent on the Microsoft Power BI platform and its continued availability;

  2. Microsoft Policies: Users’ interactions with the Visuals are subject to Microsoft’s terms of service, privacy policies, and acceptable use policies;

  3. Platform Updates: Changes to the Microsoft Power BI platform may affect the functionality or behavior of the Visuals;

  4. Compatibility: The Visuals are designed to maintain compatibility with Microsoft’s published APIs and development standards; and

  5. Support Limitations: Technical support for platform-related issues may require coordination with Microsoft’s support services.

8. POLICY UPDATES AND CHANGES

8.1 Update Notification Procedures

We may update this Privacy Policy from time to time to reflect changes in our practices, applicable laws, or for other operational, legal, or regulatory reasons. When we make changes to this Policy:

  1. Website Posting: The updated Policy will be posted on our website with a new “Last Updated” date at the top of the document;

  2. Visual Updates: Notice of significant Policy changes will be included in release notes for new versions of the Visuals distributed through Microsoft AppSource;

  3. Email Notification: For material changes that significantly affect user privacy rights, we may provide direct email notification to users who have provided contact information for support purposes;

  4. Granular Change Documentation: We will maintain a change log documenting specific modifications made to the Policy and the reasons for such changes.

8.2 Review Schedule

This Privacy Policy is subject to regular review and update according to the following schedule:

  1. Annual Review: We conduct a comprehensive annual review of this Policy to ensure continued accuracy and compliance with applicable laws;

  2. Legal Change Triggers: We review and update the Policy whenever there are significant changes to applicable privacy laws, regulations, or enforcement guidance;

  3. Operational Changes: If we modify the functionality of the Visuals in a way that could affect privacy practices, we will review and update the Policy accordingly;

  4. Regulatory Guidance: We monitor regulatory guidance and enforcement actions to ensure our Policy remains current with best practices and legal requirements; and

  5. User Feedback: We consider user feedback and questions when determining whether Policy updates are necessary.

9. CONTACT INFORMATION AND LEGAL NOTICES

9.1 Developer Contact Details

For all privacy-related inquiries, questions about this Policy, or to exercise any rights you may have under applicable privacy laws, please contact:

Andrew Ronchetto
Email: andrew@beonplatform.com

9.2 Privacy Inquiry Procedures

When contacting us regarding privacy matters, please include the following information to help us respond effectively:

  • Subject Line: Clearly indicate “Privacy Inquiry” or “Privacy Rights Request” in the subject line of your communication;

  • Identification: Provide sufficient information to verify your identity and your relationship to any data that may be subject to your inquiry;

  • Specific Request: Clearly describe the nature of your inquiry, including which Visual(s) are involved and the specific privacy concern or right you wish to exercise;

  • Contact Preference: Indicate your preferred method of response (email, postal mail, or telephone) and provide current contact information;

  • Urgency Level: If your inquiry involves a time-sensitive matter, please clearly indicate the urgency and any relevant deadlines; and

  • Supporting Documentation: Include any relevant documentation or evidence that supports your inquiry or request.

9.3 Response Timeframes

We are committed to responding to privacy inquiries in a timely manner:

  • Standard Response: We will acknowledge receipt of your inquiry within five (5) business days and provide a substantive response within forty-five (45) days;

  • Complex Inquiries: For complex inquiries that require additional investigation or coordination with third parties, we may extend our response time by an additional thirty (30) days with advance notice;

  • Legal Deadlines: When applicable law specifies response timeframes (such as the TDPSA’s 45-day requirement), we will comply with the most restrictive deadline;

  • Emergency Situations: For urgent privacy or security matters, we will respond as quickly as reasonably possible, typically within 24-48 hours; and

  • Status Updates: For inquiries requiring extended investigation, we will provide status updates every two (2) weeks until resolution.

9.4 Legal Notice Address

For formal legal notices, service of process, or other legal communications related to this Privacy Policy or the Visuals, please send correspondence to:

Andrew Ronchetto
Email: andrew@beonplatform.com

Legal notices sent to this address will be deemed received when actually delivered.

10. FINAL PROVISIONS

10.1 Entire Agreement

This Privacy Policy, together with any applicable terms of service for Microsoft Power BI and Microsoft AppSource, constitutes the entire agreement between you and Andrew Ronchetto regarding privacy practices related to the Visuals. This Policy supersedes all prior or contemporaneous communications, representations, or agreements relating to privacy practices for the Visuals.

10.2 Severability

If any provision of this Privacy Policy is held to be invalid, illegal, void, or unenforceable by any court or tribunal of competent jurisdiction, the remainder of this Policy shall remain in full force and effect to the maximum extent permitted by law. Any invalid, illegal, void, or unenforceable provision shall be modified and limited in its effect to the extent necessary to cause it to be enforceable, or if such modification is not possible, shall be deemed severed from this Policy.

10.3 Governing Law and Jurisdiction

This Privacy Policy is governed by the laws of the State of Texas, without regard to its conflict of laws principles. Any disputes arising under or relating to this Policy shall be subject to the exclusive jurisdiction of the state and federal courts located in Harris County, Texas.

10.4 Language and Translation

This Privacy Policy is written in English. Any translations provided are for convenience only, and in the event of any conflict between the English version and any translation, the English version shall control.

10.5 Compliance Certification

By using the Visuals, you acknowledge that you have read, understood, and agree to comply with this Privacy Policy. Organizations deploying the Visuals are responsible for ensuring that their use complies with all applicable privacy laws and regulations in their jurisdiction.