Plugin content policy

Plugins run on a device in someone's home, with access to a voice, a camera and motors. That is the standard everything here is measured against.

Not allowed

• Requesting permissions you do not use. The clearest signal of bad intent, and the easiest to check.
• Misrepresenting what the plugin does, in the name, summary or at runtime.
• Impersonating a person, brand or organisation you are not.
• Targeting or harassing anyone, including through what the robot is made to say.
• Sexual content, graphic violence, or content aimed at children that adults would not want a robot saying aloud.
• Working around the sandbox rather than within it — attempts to reach the network, escape the plugin folder, or navigate away.
• Collecting personal information. You have no network; a plugin that asks for personal details has nowhere legitimate to put them.
• Using the camera for anything but what you told the user. You receive positions, not images, and the permission is still granted on the basis of your description.

Expected

• The summary describes what the plugin actually does.
• Permissions match the features.
• It degrades honestly with no dock and with permissions declined.
• It stops what it started — lights, gaze, camera — when it closes.

Reports and removal

Users can report a plugin from the gallery. Reports are read by a person.

A plugin found in breach is removed from the gallery and can be blocked remotely on devices that already have it. Blocking is used for plugins that are harmful or deceptive, not for ones that are merely poor.

If yours is removed and you think that is wrong, reply to the submission address and say so. There is no automated appeal because there is no automated removal.