When using the mapping functionality in Qlik Sense, geo data needs to be included in the app in order to use detailed spatial analysis, e.g. by postal code through a KML file. This geo data often needs to be purchased separately, as Qlik does not recognize ZIP codes out of the box (or at least not for all countries).
In a particular use case we have hundreds of users who could potentially use this data for their analysis. However, since the concerning data set required for enabling this analysis is relatively costly, I have some doubts. What prevents a user from pulling in all the geo data in a table and exporting it to Excel, potentially selling it?
I tried to hide the KML fields. This not only doesn't work for maps, but a savvy user would still be able to pull the field in a table and export to Excel.
Any ideas how export of this data can be restricted?
