Skip to main content

6 posts tagged with "compliance-studio"

View All Tags

Legal document options on widget URL endpoints

The hosted widget URL endpoints now accept per-call legal document variants, matching the options object already available on /age-gate/check. Use these to show platform-specific Terms of Service, Privacy Policy, and additional legal links (for example, Xbox, PlayStation, or Steam) in the widget consent flow instead of the product defaults.

What's new​

API reference (OpenAPI)​

CDK: Sessions and permissions​

  • Presenting legal documents and data notices: Documents that termsOfServiceDocument, privacyPolicyDocument, and additionalLegalLinks are the canonical field names for legal-document variants across the k-ID API, and where they live for each endpoint (options on the age gate check and the widget URL endpoints, materialChange on /session/upgrade).

Compliance Studio​

  • Additional legal links: The Variant ID guidance now points at the widget URL endpoints, not just /age-gate/check.

Documentation​

Guides for transactions and payment-as-verification

Transactions and payment-as-verification now have full documentation on the developer hub.

What's new​

  • Transactions. Your product reports a child's purchases to k-ID, which surfaces them to the linked parent as a per-child Purchases view in Family Connect and in the recurring activity digest. Where you want a parent in the loop before a charge, a purchase-approval request asks them to approve it first, and the outcome arrives as the Transaction.PurchaseApprovalResult webhook. Both parts are configured per product in Compliance Studio.
  • Payment-as-verification. A completed card payment can stand in for the parental-consent step, mirroring the credit-card verification method one-to-one: it's honored exactly where that method is enabled for the session, credit-card funding only, and everywhere else the parent completes the standard verified parental consent flow unchanged.

Documentation​

Guides for verified parent linking, screentime, and activity ingestion

Three parent-controls capabilities now have full documentation on the developer hub: verified parent linking, screentime, and activity ingestion.

What's new​

  • Verified parent linking (VPL). A player can invite their own parent into your product; once the parent verifies their identity, they can see and set that player's controls, for example, screentime. VPL is a link, not a gate: nothing is blocked, and your product keeps working whether or not the parent accepts. The Session.Unlink webhook tells you when either side ends a link. VPL is enabled per developer organization.
  • Screentime. A parent sets daily limits, quiet hours, and break reminders for their child in Family Connect. Your product reports usage and honors the verdict k-ID returns; k-ID holds the rules, counts usage per child per day, and evaluates the schedule. Each limit is preceded by a warning event so a player can reach a save point, and a child can ask for more time through a screentime override.
  • Activity ingestion. Your product reports what a child did by pushing records against activity types you declare per product in Compliance Studio. k-ID stores and aggregates those records into the surfaces a trusted adult reads in Family Connect, including a recurring digest email. Activity is inbound only.

Documentation​

Version history and rollback in Compliance Studio

Every configuration a product has published is now kept and listed, and an administrator can point Live back at a configuration it served before without waiting on k-ID.

What's new​

  • The History tab. A product now has a History tab holding two sections. Activity lists everything that has happened to the product, and any entry that changed the configuration carries a View changes link showing exactly what that one entry changed. Versions lists every configuration published to Live and to Test, newest first, with the one being served marked Current.
  • Rollback. The version Live is serving offers Rollback, which repoints Live at the configuration published before it. It doesn't create a new version, so numbering is unaffected and the version you rolled off stays in the list and can be made current again. A rollback takes effect within minutes, with no review step, so the confirmation shows the full diff of what Live would serve.
  • Reset to published. A working copy with unpublished edits can be reset back to whatever Live or Test is serving, previewed the same way. This is separate from a rollback: a rollback changes what players are served and leaves your working copy alone, a reset does the opposite.
  • Naming a version. Versions can be given a name, so Live v7 can also read as "pre-launch tuning" when someone comes looking a month later.

Documentation​

Additional legal links and Check age gate options

We've documented additional legal links in Developer Details and the new options parameter on the Check age gate API so you can show platform-specific legal documents (e.g., Xbox, PlayStation, Steam) in consent flows.

What's New​

In Compliance Studio, on the Developer Details tab for a product, you can now add optional Additional legal links that appear in consent flows:

  • Title and Link: Localized display title and URL (same language options as your main legal documents).
  • Variant ID: Identifier used when calling the Check age gate API (e.g., xbox-tos, playstation-privacy-policy). Required if Always display is off.
  • Always display: When on (default), the link is always shown in consent flows. When off, the link is only shown when your game calls the age-gate API with the matching variant ID in options.

Use these when your game is distributed on multiple platforms and each platform requires different legal document URLs.

Check age gate API — options parameter​

The POST /api/v1/age-gate/check request body now supports an optional options object:

  • termsOfServiceDocument: Variant ID for Terms of Service (must match a configured additional legal link).
  • privacyPolicyDocument: Variant ID for Privacy Policy (must match a configured additional legal link).
  • additionalLegalLinks: Array of variant IDs for extra legal documents to display with ToS and Privacy Policy (each must match a configured additional legal link).

When a challenge is created, the consent screen shows the requested legal links instead of the default product Privacy Policy and Terms of Service.

Documentation​

Developer Role and Product Access Control

We've introduced a new Developer role in Compliance Studio with product-level access control, enabling organizations to maintain clear boundaries between different products and teams.

What's New​

Developer Role​

A new Developer role is now available in Compliance Studio. Users with the Developer role can manage products and product developer settings, but only for products they have been explicitly assigned to.

Key Features:​

  • Product-level access control: Developers can be restricted to access only specific products within your organization
  • Granular permissions: Each Developer role member can be assigned to their respective products, enabling product-level access control and maintaining organizational boundaries
  • Product management: Developers can manage products and product developer settings for their assigned products only

Member Access Management​

A new Member Access menu has been added to the Organization settings, allowing Owners and Admins to assign product access to members with the Developer role.

How it works:​

  • Access assignment: Owners and Admins can use the Member Access menu to assign specific products to Developer role members
  • Multiple product assignment: You can assign multiple products to a single Developer
  • Immediate effect: Product access assignments take effect immediately

Updated Documentation​