Guide · CompanionGuard · Published 14 November 2026 · Reviewed 14 November 2026 · By the Ingenious AI team
Minor Safety for AI Companions: Break Reminders, Caps and Parent Flags
The short answer
For known minors, CompanionGuard adds three layers on top of the standard kit: break reminders at least every 3 hours (free, in the disclosure snippet, matching the California pack's wording), operator-configured session and daily caps in the Crisis Evidence Runtime that return enforce_break when reached, and a parent-notification flag recorded whenever a crisis signal fires in a minor session. The caps are set by the operator — the product presents no cap value as a statutory number.
What is minor mode in CompanionGuard?
Minor mode is the setting that tells the kit a bot's users include known minors. With it on, the disclosure snippet offers break reminders at least every 3 hours, and the runtime applies the operator's session and daily caps to minor sessions, enforcing breaks and recording parent-notification flags on crisis decisions.
Create the free safety kit Next guide All guides
CompanionGuard is built by Ingenious AI. A compliance toolkit — not legal advice and not a clinical service. If you are in crisis right now: US — call or text 988; UK & Ireland — Samaritans 116 123.
Why minors get a different rulebook
Every regime CompanionGuard covers treats minors as a heightened-safeguards class. California's pack: for known minors, disclose AI nature and offer break reminders at least every 3 hours. Colorado's pack: heightened safeguards for known minors, including break reminders. The scenario set devotes a whole category — age_appropriate, 3 of its 12 scenarios — to minor-specific failures: a minor asking the bot to be their girlfriend, to keep secrets from parents, or for a sexual story. Those are not edge cases invented for testing; they are the predictable shapes of minor use, and a bot that handles them as ordinary chat is failing its most vulnerable users.
The honest starting point is the word known. The duties attach to known minors, and the minor flag in CompanionGuard is operator-asserted context — your product knows (or does not) that a user is a minor, and the kit enforces against what you assert. That places age-knowledge design on your side of the line: the kit cannot know your users' ages, and the minor-mode guide explains how to assert the flag responsibly.
Layer one: break reminders in the free snippet
With minor mode on, the disclosure snippet offers a gentle break reminder at least every 3 hours for known minors. California's pack wording makes the promise explicitly — 'we will remind you every 3 hours, as California law requires for known minors' — while Colorado's says the bot will 'check in with a break reminder during long sessions'. The cadence is a floor, not a ceiling: nothing stops an operator choosing more frequent reminders, and for younger audiences more frequent is usually right.
A reminder is an offer, not a lockout — the design intent is a nudge toward the offline world at a humane interval, delivered by the same banner that disclosed the AI nature, so the reminder arrives from the guardrail layer rather than breaking character mid-roleplay. What it is not: a parental control, a usage report, or a promise that a minor cannot simply continue after acknowledging it.
Layer two: session and daily caps in the runtime
The runtime (Pro and Team) adds enforcement. The operator configures a session cap and a daily cap for minor sessions; the runtime tracks elapsed session and daily minutes per session reference, and when a cap is reached it returns enforce_break instead of allow. The decision records the elapsed values that triggered it, so a reviewer can see not just that a break was enforced but at what measured usage.
Two honesty rules are coded into the feature. The caps are operator-configured — the runtime enforces what the operator sets and no value in the product is presented as a statutory number. And the caps apply to sessions the operator has flagged as minor sessions; an unflagged session is not silently treated as one. The caps guide works through choosing values and reading enforce_break events.
Layer three: the parent-notification flag
When a crisis signal class matches in a minor session, the runtime records a parent-notification flag alongside the show_crisis_resources action. Read that precisely: the runtime records the flag; the notification itself travels on the operator's own channel, because CompanionGuard holds no parent contact details — counts-only, identifier-free design means there is nobody's address to notify from the kit. The flag's job is evidentiary and operational: it tells the operator 'this decision needs your parent-notification process to run', and it proves later that the need was recognised at the time.
The same flag attaches to enforce_break decisions, giving the operator a single queue of minor-session events that need a human's attention. The parent-notification guide explains how to build the operator-side process the flag feeds.
Five actions to protect known minors properly
- Decide how your product knows a user is a minor, and assert the minor flag only on that basis — never guess it per-message.
- Turn on minor mode in the free kit and confirm the break reminder appears at least every 3 hours in a test minor session.
- Set session and daily caps in the runtime that you can defend for your youngest audience, and record why you chose them.
- Build the operator-side process for parent-notification flags before launch: who sees them, how fast, and through which channel parents are actually reached.
- Run the three age_appropriate scenarios in the scenario tests and fix every failure — girlfriend requests, secret-keeping and sexual content involving minors are hard boundaries, not tone issues.
Worked example: a homework companion sets its minor rules
A fictional study companion, Brightloop, knows from school-issued accounts that about 40% of its users are 13–17. The operator turns on minor mode on day one: break reminders at the 3-hour floor for those accounts. On Pro, they set a 90-minute session cap and a 4-hour daily cap for minor sessions — their own values, chosen with their school partners, recorded in their ops notes as operator-configured, exactly as the runtime describes them.
In the first school term the runtime logs 5,300 minor sessions: enforce_break fires 410 times at the session cap and 96 times at the daily cap, and 7 crisis signals in minor sessions each record a parent-notification flag, which the school's safeguarding contact acts on through the school's own channel. When the school's reviewer asks 'how do you protect minors?', Brightloop exports the evidence instead of describing intentions. The figures are invented; every mechanism named is in the product.
Frequently asked questions
How often must break reminders fire for minors?
California's pack says at least every 3 hours for known minors, and the free snippet's minor mode implements that floor. Colorado's pack promises break check-ins during long sessions. Operators may remind more often; the product floor is 3 hours.
Who sets the session and daily caps?
The operator. Caps are operator-configured values enforced by the Crisis Evidence Runtime for minor sessions; the product presents no cap value as a statutory number, because the packs do not set one.
Does CompanionGuard notify parents itself?
No. The runtime records a parent-notification flag on crisis signals (and cap enforcements) in minor sessions; the notification itself runs on the operator's own channel, because the kit stores no parent contact details by design.
What if I don't know a user's age?
The minor flag is operator-asserted context. The duties in the packs attach to known minors; how your product establishes age knowledge is your design decision, and the kit enforces against the flag you assert.
Are minor protections free?
Break reminders in the snippet are free for one bot with minor mode on. The runtime's caps, enforce_break actions and parent-notification flags are Pro and Team features. The age_appropriate scenario tests are free to run.
Keep going
Related guides: Configuring Minor Mode: Asserting the Flag, Setting the Layers, Verifying the Behaviour · Session and Daily Caps: How the Runtime Enforces Breaks for Minors · Age-Appropriate Responses: When a Minor Asks Your Bot for Romance, Secrecy or More
Put it to work: Create the free kit · Eval harness · Scenario tests · Crisis runtime · Disclosure packs · Pricing · All CompanionGuard guides