Data handling
Ticket data is never stored
Section titled “Ticket data is never stored”Ticket, user and organization data goes straight from Zendesk to Power BI on each refresh. It isn’t saved to a database, a file or a cache. The service keeps only the list of your Zendesk custom fields in memory, for up to 10 minutes, so it can name the columns.
What is stored
Section titled “What is stored”| What | Why | How it’s protected |
|---|---|---|
| Your Zendesk subdomain and user ID | To know whose connection it is | — |
| Your Zendesk access and refresh tokens | To read Zendesk on your behalf | Encrypted with AES-256-GCM |
| Datasources: name, ticket filter, selected tables | To build your feeds | Visible only to you |
| API tokens: label, first characters, expiry, last use | To check Power BI’s sign-in | Only a SHA-256 fingerprint of the token is kept, never the token itself |
Where it runs
Section titled “Where it runs”The service and its database run at Hetzner in Germany (EU). Traffic reaches it through Cloudflare. See the Privacy Policy for the full list of providers.
Access
Section titled “Access”- The app asks Zendesk for read access only. It can’t create, change or delete anything in your Zendesk.
- Each agent connects separately. Datasources and API tokens are private to the agent who created them.
- Feeds require an API token. A feed URL on its own gives no access.
- Your Zendesk tokens are decrypted only inside the service, to call Zendesk. They are never sent to Power BI or to your browser.
Deleting your data
Section titled “Deleting your data”- Datasources: select Delete on the Datasources tab. This removes them for good.
- API tokens: select Revoke on the API Tokens tab. The token stops working immediately.
- Your connection and everything else: email [email protected] from the address on your Zendesk account, with your Zendesk subdomain. We’ll delete your stored connection, datasources and tokens.