Privacy Policy

Dynamic Matrix Heatmap — a Power BI custom visual by TCViz · Last updated: 3 August 2026

The short version

Dynamic Matrix Heatmap does not collect, transmit, store or share any data. It has no network access of any kind. Everything it does happens inside the Power BI rendering sandbox on your own machine or in your own tenant.

1. What the visual receives

Power BI passes the visual only the fields you place in its field wells, already aggregated according to your data model. The visual has no route to the rest of your dataset, your Power BI workspace, your account or your device.

Field well	What it receives
`Dimensions`	Category values for the fields you assign, used to populate the X and Y dropdowns and to build the matrix axes.
`Measures`	Numeric values for the measures you assign, plus their format strings and aggregation metadata.
`Distinct count of`	Raw column values (for example customer identifiers), used solely to count unique values in memory while rendering.

2. Network access

The visual makes no network requests whatsoever. There are no fetch or XMLHttpRequest calls, no external scripts, no fonts loaded from a CDN, no analytics, no telemetry, no error reporting and no advertising. Its privileges array in capabilities.json is empty, which means Power BI itself blocks any outbound connection at the platform level.

3. What is written, and where

The visual persists exactly three values, and only inside your own .pbix report file through the standard Power BI persistProperties API:

The field name chosen in the X axis dropdown
The field name chosen in the Y axis dropdown
The key of the entry chosen in the Value dropdown

These are field names, never data values. They exist so your selection survives saving and reopening the report. They travel nowhere else.

The visual also writes a standard Power BI filter when you click a cell, so other visuals on the page react. That filter lives in your report, exactly like a slicer selection.

What is not stored

No cookies, localStorage or sessionStorage
No browser fingerprinting or device identifiers
No copies of your data outside the current rendering pass
No personal information of any kind

4. Licensing

Pro entitlement is checked through Microsoft's official IVisualLicenseManager API, which is part of Power BI itself. TCViz operates no licence server and receives no call from the visual. The check asks Power BI whether the current user holds an active plan and returns a yes or no; no identity, account name or usage information reaches us. If the check fails for any reason the visual simply stays on the Free tier.

5. Purchases

Pro licences are sold and processed by Microsoft through AppSource. TCViz never sees your payment details. Microsoft's own privacy statement governs that transaction.

6. Support requests

If you open an issue on GitHub or email us, we receive whatever you choose to include — typically your description, the visual version and any screenshots you attach. Please redact anything confidential before sending. We use that information only to answer you, and we do not share it.

7. Children

The visual is a professional data tool, not directed at children, and collects nothing from anyone.

8. Changes

If this policy changes, the revised version will be published here with a new date and summarised in the changelog. Because the visual collects nothing, no change can retroactively affect data already handled.

9. Contact

Questions about this policy: tinocallarisa@gmail.com
Bug reports: GitHub issues