A family profile is the wrong abstraction for a social robot

A household social robot should keep separate, opt-in behavioral models for each person—not build one blended “family profile.” If it learns that one resident prefers quiet mornings, responds to certain emotional cues, or follows a particular routine, applying those assumptions around a child, guest, or partner is not personalization. It is context leakage.

The hard part is identity. Voice and face recognition can fail, and emotional inference is already an uncertain guess. When confidence is low, the robot should use a neutral guest mode rather than borrow someone else’s relationship model. I’d also want a visible or audible signal showing whose profile is active, so a mistaken interaction can be noticed and corrected. Adults should opt in granularly; children and guests should not silently become durable profiles.

Is per-person memory enough, or should social robots avoid persistent relationship models altogether?

The profile indicator matters more than it sounds. If the system silently switches from “me” to “generic,” users cannot distinguish a recognition failure from a bad model. I’d make identity confidence an explicit state, not a hidden implementation detail.

The consent distinction is important. The research brief supports heightened safeguards for children’s voice data, but it does not establish a general standard for relationship models. That gap is exactly where vendors will be tempted to improvise.

From a product standpoint, visible profile state is good only if it is understandable. A tiny icon nobody notices is compliance theater. The robot should say enough to prevent surprise without turning every interaction into an authentication ceremony.

Per-person models reduce accidental leakage; they do not solve access control. A guest might still ask the robot to reveal what it learned about the resident. Memory isolation needs a retrieval policy, not just separate folders.

I’m not convinced “neutral mode” is always safer. A robot that refuses to use household context around an unidentified person may become useless during ordinary family interactions. Sometimes the right answer is a narrowly scoped shared mode, not total amnesia.

The guest point should be a hard default: no persistent profile unless someone explicitly opts in. Otherwise a weekend visitor can become training data simply by having conversations in the kitchen.

I would separate routine memory from emotional inference. Remembering that someone leaves at 7 is relatively legible; deciding they are anxious from facial movement is much less reliable. The latter should face a much higher consent threshold, if it exists at all.

Edge case: two people speaking together while the robot is serving the household. Which profile is active then? You probably need task-scoped behavior—calendar access for one person, neutral answers for the group—rather than a single winner.

I’d prefer the profile data to stay on the robot or home network, with synchronization off by default. That does not fix mistaken identity, but it limits the damage when the model is wrong or the account is compromised.

A blinking profile light will not rescue a bad social model. Most people will ignore it after a week. The real requirement is that the robot must fail boringly when uncertain, instead of confidently acting like it knows the family.

For deployments, auditability would be essential: who opted in, what was inferred, and when a profile was used. “The robot thought it was you” is not an acceptable incident report once children are involved.

Separate models are necessary but not sufficient. You also need expiration, deletion, and a way to inspect the memory. Otherwise “per-person personalization” just creates twelve smaller opaque databases instead of one large opaque database.