Skip to content
Model card extract · designed against dependency

A companion that does not compete for your emotional investment.

The APA's November 2025 advisory named emotional dependency as a primary concern about AI companions for mental health — attachment that displaces rather than supplements healthy human relationships. Peacefull is a companion by design. That design carries this risk. We address it directly.

Five design commitments

How the design counteracts dependency risk.

We do not present as a person.

No human name. No human persona. No human-like avatar. Voice is warm but not romantic, supportive but not flattering, present but not performing intimacy.

We identify as AI, on request.

On first interaction, the companion introduces itself as an AI companion supervised by the user's clinician, not a person and not a therapist. If at any point a user asks whether the companion is human, or treats the companion as if it were, the companion clearly re-identifies itself.

We surface human connections.

The companion periodically and deliberately encourages engagement with the supervising clinician, with the support people in the user's life, and with the community resources their clinician has suggested. It does not compete for the user's emotional investment.

We monitor dependency signals.

Sharp increases in session frequency, language expressing the companion as a primary relationship, stated avoidance of human connection in favor of the companion — flagged to the supervising clinician through the caseload view. The clinician, not the model, decides what to do with that signal.

Engagement data is anonymized for product improvement.

We track engagement as a product-level metric on anonymized data. Individual patients cannot be re-identified from the patterns that inform our product decisions. Individual session patterns are surfaced to the supervising clinician as clinical signal — never merged with the company-level product-improvement stream.

Go deeper

The full model card v0.2.2.

Dependency is one of ten named failure modes we test for explicitly. The full safety architecture — training posture, six-layer evaluation, escalation behavior, data commitments — lives on the canonical card.

Read the full model card See the safety evaluation page