Skip to main content Skip to complementary content

Home > Multi-tenant administration > Cross-tenant data residency, deletion, and PII

Cross-tenant data residency, deletion, and PII

Last updated: 2026-11-03

Cadence: Monthly (inventory) and Yearly (region planning, retirements)

Subscription model: Multi-tenant subscriptions

Roles: Tenant Admin (TA), Service Account Owner (SAO)

Last verified: 2026-05

Initial Recurring
Estimated time 1 day 30 min monthly / 4 hr yearly

Benefits:

  • Avoids surprises when a tenant is in a region that doesn't match contractual data-handling requirements
  • Tracks exported data so deletion obligations can be honored end-to-end
  • Plans tenant region selection up front, since region is immutable post-creation

Goal

Tenants in different regions hold data subject to that region's data-handling rules; the region cannot be changed after a tenant is created (a Qlik Support case is required to discuss alternatives). Deleting a tenant purges Qlik-side data, but any usage data exported to external storage, to other Qlik Cloud tenants, or to your own systems must be tracked and handled per your contractual obligations.

Tasks

Task TA AA DA AuA SAO
Maintain a tenant inventory (hostname, region, subscription, owner, status, customer reference) ✓ ✓
Before tenant deletion, audit any usage / monitoring data that has been exported and apply the relevant retention or deletion policy ✓ ✓
Plan tenant region selection up front—region moves are a Qlik Support engagement, not self-service ✓ ✓
Review the cross-region AI inference setting per tenant (tenant settings; programmatic toggle toggle-cross-region-data-inference). When enabled, AI requests transiently flow to another AWS region where the model is hosted—this is the platform's main admin-controlled cross-region data flow, so document whether it is enabled per tenant. Per-feature cutover dates are in the Qlik release notes and deprecation notices ✓ ✓

References

Tags: #monthly #yearly #multi_tenant #data_residency #region #pii #retirement

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!