Question 1

Where is my data hosted and stored when using QBeeQ Plugins?

Accepted Answer

All data remains within the customer’s Sisense environment and is never transmitted to external servers by QBeeQ plugins.

Question 2

Does QBeeQ ever access our data?

Accepted Answer

By default, QBeeQ does not access, collect, transmit, or store any of your data. All data processing happens entirely within your Sisense environment, and no data is ever sent to third parties.
We only access your data if you explicitly grant permission—for example, during a support session, troubleshooting, or a professional services engagement involving Sisense or Snowflake. Even in those cases, access is limited, temporary, and solely to resolve the issue or deliver the requested service.

Question 3

What happens to our data if we uninstall your plugin or cancel service?

Accepted Answer

Since we do not store or access data externally, there is no data to delete on our side. Once uninstalled, the plugin ceases to interact with your environment.

Question 4

How do you handle customer data privacy?

Accepted Answer

We operate under a data-minimization principle. Since no customer data leaves your Sisense environment, there is no external exposure. Our internal policies also reflect strong commitments to privacy and security best practices.

Question 5

Do your plugins support Data Security rules?

Accepted Answer

Yes. Our plugins inherit and fully comply with Sisense's data security rules.(https://docs.sisense.com/main/SisenseLinux/data-access-security.htm)

Question 6

Do your plugins support Role-Based Access Control (RBAC)?

Accepted Answer

Yes. Our plugins inherit and fully comply with Sisense's user roles and permissions.(https://docs.sisense.com/main/SisenseLinux/sisense-user-roles.htm?tocpath=Security%7CSecuring%20Users%7C_____2) Some plugins have additional layers of configurable access control.

Question 7

Do your plugins support SSO or authentication protocols?

Accepted Answer

Yes. Authentication and access are managed through Sisense, which supports SSO and industry-standard protocols.(https://docs.sisense.com/main/SisenseLinux/using-single-sign-on-to-access-sisense.htm)

Question 8

How does QBeeQ handle API keys or configuration data?

Accepted Answer

Most of our native plugins do not require API keys, and all configuration is stored locally within your Sisense environment. In cases where a plugin uses a third-party service (e.g., Super Map with Mapbox), you may need to provide your own API key. These keys are only used to enable the third-party service and are never transmitted or stored by QBeeQ.

Question 9

Can plugins be disabled or removed easily if needed?

Accepted Answer

Yes. Plugins can be disabled or removed at any time through the Sisense Add-ons (https://docs.sisense.com/main/SisenseLinux/sisense-add-ons.htm#EnablingandDisablingAddons)under Admin.

Are your analytics missing the “Where”? Join our upcoming webinar: Every Metric Happens Somewhere → 📍Save your seat

Security & Compliance