The three kinds of twin

One engine, three audiences. They share the same grounding, the same citations and the same honest "I don't know" — what differs is who they answer and who is allowed to reach them.

Your public twin

You, answering your audience, at hiy.ai/yourname. Built from what you've actually made — writing, talks, notes, a CV. It's the one you share, embed, and put on a business card.

Before it goes live it passes an identity check, because a public twin claims to be a specific person. A cleared twin carries a Verified badge beside its AI label.

The badge is tied to the name that was checked. Rename your twin away from that name and the badge comes off — a check made for one name isn't carried over to another. Your twin stays live and keeps answering throughout; renaming back restores the badge on its own, with no second review.

Support twins

A twin for a product you own. It answers your users from your product's material, in a neutral voice — it represents the product, not a person.

It's reachable only through a token your own site mints. Anything it can't answer goes to your inbox with the visitor's email attached, so a stuck user never dead-ends.

Team twins

You, answering colleagues from internal material. Invites are just email addresses, and access begins at first sign-in. Everyone else — search engines included — gets a 404 rather than a login wall, so the twin's existence isn't advertised.

A team twin reports what you wrote. It never decides on anyone's behalf, and there's deliberately no per-person trail.

Switching between them

Twins live behind the twin switcher in your dashboard. Each keeps its own knowledge, its own audience and its own rules — adding material to one never affects another.

You may only twin yourself, or something you own. What enforces that isn't your address being unique — it's the identity check every public twin passes before going live, a person reviewing anything the automated check can't clear, and a report link on every public page that no plan can remove.

Was this page helpful?

View Markdown