Language
English

Data, privacy, and residency

Icon Map for Fabric works on your data, in your tenant. Two kinds of data are involved, and they are handled very differently:

  • Your data: maps, Lakehouse tables and files, and everything else in your Fabric tenant and OneLake. It stays in your tenant. Tekantis does not receive or store it.
  • Operational data: the records Tekantis keeps to run its business and the service, such as your account, your licenses and how much they are used. It never contains your map content.

Your data stays in your tenant

  • Icon Map reads your data in place from OneLake and your Fabric sources. It doesn't copy or move your data to build a map.
  • When you publish a map, the frozen configuration and any data snapshot are written to your own OneLake (under a Files/_published/ folder), not to Tekantis infrastructure. The published-map service reads them at view time and keeps nothing.
  • Write-back edits are saved back into your OneLake (an annotations store or a layer file).
  • Data you buy from the data store is written into your OneLake and is then yours. Tekantis never deletes anything from your Lakehouse or OneLake. When a store license ends, you are asked to stop using the copy and delete it yourself.

What Tekantis holds

Tekantis keeps operational data only:

  • account and contact details;
  • the tenant, capacity and workspace IDs and names your licenses apply to;
  • license and usage records (identifiers and counts, no content);
  • data store orders, including the outline of any area you buy;
  • delivery records, which note the path a data store copy was written to, never its content;
  • upgrade and trial extension requests, and the name and email address recorded when a trial starts;
  • work-account sign-in identifiers.

It is held in Microsoft Azure in UK South, whatever your Fabric region. Contact records are also kept in HubSpot, our CRM, in its EU data center. Payments on icon-map.com are taken by Paddle as merchant of record. The security whitepaper, section 12 lists every flow, the Tekantis service that receives it, where it is held and the third parties involved.

Identity and access

Icon Map acts using your Microsoft Entra identity and inherits your Fabric permissions, so it can only ever reach data you're already entitled to see. Access to layers and catalogs is governed by the same Fabric and OneLake permissions you use elsewhere, including row-level security on Power BI semantic models. See Security & permissions configuration for the specifics.

Hosted services

Some parts of the experience are hosted by Tekantis. The basemaps, the public Icon Map Catalog tiles and the embedded viewer serve map styling and published, view-only content; they don't hold your source Fabric data. The workload's backend also calls the Tekantis licensing service and website API to check licenses, record usage counts and handle the data store. Those services hold operational data only.

Compliance resources

For formal security and compliance material, see:

Next steps