Product purpose and principles

About Dream Companion

Dream Companion is being developed as an adults-only AI character and conversation experience. The public site now separates product intent from verified availability and avoids presenting fictional characters, review scores, or security claims as established facts.

What the experience is intended to do

Help adults explore fictional AI characters for conversation, romantic or platonic roleplay, creativity, and low-pressure entertainment. A character profile may guide personality, interests, tone, scenario, and boundaries.

Dream Companion is not intended to present AI as human, conscious, therapeutic, or capable of professional judgment.

How product access works

Dream Companion provides educational content and uses a short, non-indexed loading page before sending visitors to an external companion service. Account creation, features, payments, privacy practices, and service terms are controlled by that destination.

Continue to the companion experience

Design principles

What Should Guide the Product

Clear disclosure

Characters should be consistently identified as generated software, not real people.

User control

Personality, boundaries, saved details, and deletion should be understandable and revisable.

Claim accuracy

Features, ratings, privacy, security, and pricing should be tied to evidence and review dates.

Responsible use

The product should enforce its adult audience and explain wellbeing and professional-care boundaries.

Accountability information still required

A launch-ready About page needs facts only the operator can provide: legal entity, jurisdiction, founding story, named team or responsible owner, relevant product and safety experience, support route, editorial review process, and a way to report product concerns. These details have not been invented for SEO.

Contact

For website questions, email hello@dream-companion.net. Product, privacy, and legal contact routes should be confirmed by the operator before launch.

For current boundaries, see Safety, Privacy, and FAQ.