Privacy

Short version: the visual doesn't collect or transmit anything. Everything below explains why, feature by feature, rather than asking you to take that on faith.

Your chart data

The org chart data you bind to the visual - billet titles, names, UICs, contact information, whatever your report contains - never leaves your Power BI environment. The visual has no network access of any kind (see below), so there is no path for that data to reach Customputing.com, any other server, or anyone else. It is processed entirely in memory, inside the browser tab or Power BI Desktop window rendering your report, for exactly as long as the report is open.

Why there's nothing to describe here

Most privacy policies exist to explain what happens to data once it leaves your control. This one is short because that never happens: the visual makes no HTTP, HTTPS, or WebSocket requests of any kind, to Customputing.com or anywhere else. This isn't a policy choice layered on top of code that could reach out - the capability isn't there. The visual's own declared privileges (visible in its capabilities file, part of the public source) are limited to exporting an image and reading/writing a small amount of data in your own browser's local storage (see below); no network privilege is requested or used.

License verification

Edit Mode requires a license token, entered in the format pane. Verifying that token happens entirely on your own device, using your browser's built-in cryptography (WebCrypto) to check a digital signature against a public key built into the visual. No token, license status, or usage information is ever sent anywhere to perform this check - there is nothing to phone home to, and nothing does.

Export changes and Email changes

Both of these are things a reader chooses to do with data that already exists on their own screen, not the visual communicating on its own:

• Export changes copies a summary of proposed edits to your own clipboard, or saves it as a file to your own device, depending on the format you choose in the format pane. Nothing is transmitted.
• Email changes opens your own email client (or Outlook Web) with an address and subject pre-filled, and the changes copied to your clipboard for you to paste in. The visual hands off to your email client the same way clicking a mailto: link anywhere else would - it does not send the email itself, and has no way to know whether you ultimately send it, edit it, or discard it.

Local storage

If you enable it, the visual can save an in-progress, unsaved draft of your edits to your own browser's local storage, purely so a draft survives an accidental tab close or refresh. This stays on your own device - it is never transmitted, and the visual has no way to read any other site's local storage or vice versa.

The Customputing.com website itself

This policy covers the visual - the code that runs inside Power BI. Registering for a license on Customputing.com is a separate, ordinary website interaction (the site needs a way to send you a token, typically by email), governed by whatever privacy notice appears on that site at the time. It is not part of the visual's own behavior and does not run inside Power BI.

Questions

Reach out to admin@customputing.com with anything this page doesn't answer.

Last updated: 2026.