Skip to main content

Compliance Engine updates

The Global Compliance Engine (GCE) is the rules engine that powers k-ID's jurisdiction-specific compliance behavior. As regulations evolve worldwide, k-ID periodically updates the engine to reflect new legal requirements, updated guidance, and best practices. When an update is available for your product, you're notified and guided through the review and acceptance process.

What are Compliance Engine updates​

The GCE contains the rules that determine how your product behaves in each supported jurisdiction -- covering age requirements, consent rules, and verification requirements. These rules are what make your product automatically compliant across markets without you needing to track every regulatory change yourself.

Updates to the engine happen when:

  • New laws or regulations take effect in a jurisdiction
  • Existing requirements are amended or clarified
  • Enforcement guidance is updated by regulatory authorities
  • Best practices evolve based on industry developments

An engine update can affect your product's access settings, permission configurations, and verification requirements. Each update carries a version number and includes release notes describing exactly what changed, so you always know what's being updated and why.

Notification and review​

When a Compliance Engine update affects your product, a banner is displayed on the product detail page indicating that a new GCE version is available and your product needs updating.

If your product has a Product Policy attached, the update might need to be accepted at the policy level first before it flows through to individual products.

Updates are never applied automatically. You always review and explicitly accept them, giving you full control over when compliance rule changes take effect.

Reviewing an update​

Click through the update banner to reach the engine update review page. The review page provides a detailed breakdown of what changed in this version:

  • A changelog describing the update at a high level
  • Jurisdiction-level changes showing how rules change for each affected market
  • Configuration changes covering adjustments to age requirements and compliance rules
  • Permission-related changes if the update affects how permissions are handled in certain jurisdictions

Take time to understand how the update affects your product before accepting. If you operate in multiple markets, pay particular attention to the jurisdictions where your product has the most users.

Accepting an update​

After reviewing the changes, accept the update to apply the new engine rules to your product configuration. Once accepted:

  • The updated rules become part of your product configuration immediately in the editor
  • You still need to push to test or push to live (or both) to deploy the changes to your environments
  • The acceptance is tracked in your product's activity log for audit purposes

Accepting an update doesn't change your live product until you explicitly publish. This gives you the opportunity to test the new rules in your test environment before rolling them out to production.