Question: AI / TextGenerator usage + Context Handling + Age-Gating for Kids/Select Experiences

Help and Feedback Game Design Support
, , , ,
1

Hi Roblox team,

This is a follow-up question regarding AI features and Roblox Kids / Roblox Select.

I’ve read the Kids/Select announcement, the new publishing requirements, and the Restricted Content Policy (AI Interaction + Content Maturity Labels), and I want to make sure our use of generative AI is compatible with Roblox Kids and Roblox Select selection. Specifically, I’ve reviewed:

We’re developing Curia OS, a student productivity “3D desktop” built natively in Roblox. It uses TextGenerator for things like adaptive planning, context-aware suggestions, single-session “memory,” and real‑time activity summarization.

We want to be 100% compliant with Roblox Kids / Roblox Select and the Restricted Content Policy, especially the AI Interaction rules that say experiences become Restricted if either:

  • “The experience’s main purpose is to interact with a generative AI bot or character. Users can interact with the AI continuously with no time limit.”
  • “The experience features cross-session memory where the experience saves the context of a user’s prior interactions with AI and loads it on subsequent sessions.”
    (from the AI Interaction section of the Restricted Content Policy)

My questions:

1. Generative AI in Kids / Select experiences

For a productivity OS where the main purpose is studying (not “chatting with a bot”), is it allowed to use TextGenerator in an experience that supports Roblox Kids and Roblox Select accounts, as long as:

  • AI is used in short, task-scoped ways (e.g. “help me break this assignment into steps”, “summarize this session’s activity log”, “suggest 3 study tasks for this session”),
  • AI is not the primary purpose of the experience, and
  • There is no cross-session AI memory (see next section)?

Is it correct to interpret the AI Interaction rules as allowing this pattern for Kids/Select (since it is not extended AI interaction and does not use cross-session memory)? If not, which part of this interpretation is wrong? If there are specific AI usage patterns that are not allowed for Kids/Select (even if content is safe and filtered), could you share a few concrete examples?

2. Single-session context vs. cross-session AI memory

The Restricted Content Policy and Content Maturity Labels docs distinguish:

  • “Extended AI interaction” and
  • “Cross-session memory” for AI as triggers for Restricted/18+.

Our intended Curia pattern is:

  • Use short‑term, single‑session context only with TextGenerator, like:
    • “In this current play session, you did X, Y, Z tasks”
    • “Today’s activity log: N minutes of Physics, M minutes of Math”
  • No AI cross‑session memory at all:
    • We do not load prior AI chat/context into future sessions.
    • No “remember what I told you last week” behavior.
  • All data stays inside the experience, is non‑PII, and is never shared with other players.

Is it correct to interpret this as allowed for experiences that want to be available to Roblox Kids and Roblox Select accounts, and that this pattern does not by itself require a Restricted rating, as long as:

  • AI is not the main purpose of the experience, and
  • There is no cross‑session AI memory or unlimited open‑ended chatbot interaction?

If that interpretation is off, how would you recommend structuring AI‑driven planning/summarization tools so they stay compatible with Kids/Select selection and content maturity rules?

3. Age‑gating 13+ / 18+ features while staying Kids/Select‑compatible

Curia has some AI‑adjacent features that we’d like to limit to older users (13+ and especially 18+), for example:

  • Deeper AI transparency / log inspection tools.
  • Possible future Restricted‑style AI patterns (e.g. more extended AI interactions or experimenting with cross‑session memory), if we ever go there.

Given that:

  • Creators do not have direct access to raw age values, and
  • Kids/Select access is controlled by Roblox via content maturity + the Kids/Select selection process,

our current assumption is:

  • Any truly 18+ / Restricted‑style AI patterns (like extended chatbot experiences with cross‑session memory) should live in a separate Restricted experience/place, and
  • The core Curia OS place should stay Kids/Select‑eligible (Minimal/Mild/Moderate, no social‑hangout classification, no extended AI interaction).

Is that the correct approach? Or is there a Roblox‑supported way, within a single experience, to safely hide certain features from under‑13 / under‑18 users based on the platform’s age checks / account type, while keeping the main experience eligible for Roblox Kids / Roblox Select?

We’re designing Curia OS around Private By Design principles (no PII, clear player‑visible data use, Roblox‑only storage) and want to align precisely with how you interpret:

  • “extended interaction with generative AI”
  • “cross‑session AI memory”
  • and safe age‑based feature separation for experiences that want to remain eligible for Roblox Kids and Roblox Select catalogs.

Any concrete guidance or examples for these three points would be hugely appreciated before we lock in the architecture.

Thank you!

1 Like