Jurisdictional variants respect the ?jurisdiction query parameter

If you publish a policy in multiple jurisdictional variants — say a GDPR version and a CCPA version of the same Privacy Policy — there has always been a question of how to route a visitor to the right variant. The Legal Center now supports a ?jurisdiction query parameter that the variant resolver honours.

Examples that all "just work" now:

• https://hub.termerly.com/your-project/privacy-policy?jurisdiction=eu — serves the GDPR variant.
• https://hub.termerly.com/your-project/privacy-policy?jurisdiction=us — serves the CCPA variant.
• https://hub.termerly.com/your-project/privacy-policy — serves the default variant.

This unlocks routing patterns where you can detect a visitor's region in your own application (e.g. with their IP or their account settings) and deep-link them to the right variant. Useful for SaaS products that need to surface different policies to different markets without spawning more URLs than search engines can sensibly index.