Profile data and consent

Keep profile handling separate from chat access. Embed tokens accept an authenticated user ID and an approved origin; they do not accept birth-profile claims.

Derive the stable user ID from your application session. Collect permission before sharing birth or family details. Do not put private profile data in keys, tickets, URLs or diagnostics.

Use the profile API

After chat access is established, use the profile schema and user-scoped routes supplied with your harness version. Native profile calls are separate from the token mint; a console session or another user's thread cannot stand in for your user. Verify the current create, version and thread-binding contract before adding profile writes.

Account changes

Keep each family profile owned by the authenticated user, and explicitly select the subject for a chat. Unmount chat on logout or account change. Hiding a saved item is not a promise to erase retained chat or memory data; disclose your data policy accurately.

First get backend access and the embedded chat working, then add profiles against the delivered API reference.