Guide
AI training opt-out applies by default when you register your face, voice and persona on Rightis. Anyone who has not separately consented to training use goes on the public Do Not Train list; developers that honour the signal exclude you, and for the rest it is a record that notice was given.
There is nothing separate to file. Register your face, voice and persona on Rightis and training exclusion is the default. Training use turns on only with separate consent, and only consented data is supplied, through Rightis dataset contracts.
Registration is free and takes one frontal photo. It issues a rights ID, and with a public listing that ID appears on the do-not-train list.
rightis.org/.well-known/do-not-train.json lists registered holders who have not consented to training use. Each entry carries the rights ID, display name, profile URL and lookup URL so developers that honour opt-outs can filter by name and ID. Consent can change at any time, so the list changes too and is regenerated hourly.
Alongside it sit the W3C TDM reservation file (tdmrep.json) and the registry file (rightis-registry.json), with ai.txt and llms.txt at the root. The human-readable policy is on the AI use policy page.
To be plain, an opt-out signal is notice, not a command. Developers that honour it exclude you. Those that do not cannot be blocked technically; what remains is a record that you asked in advance, which becomes evidence if a problem arises later.
It also cannot recall photos already online. What registration does is leave your wishes about future use in a form machines can read.
Removing your face from a model that has already been trained is not practical. That is why Rightis treats training and generation as two stages. Training gets the opt-out signal and the notice record; generation gets the permission check.
AI services that integrate Rightis check permission before generating your face, voice or persona. Unregistered people are not treated as cleared, and registered people are generated only within the scope they set. Even if a model already knows you, inside those services nothing is generated without permission.
With consent, your data is supplied only through Rightis dataset contracts, with a record of where it went and settlement under the contract. Consent can be withdrawn at any time, and withdrawal puts you back on the do-not-train list.
Consent is set separately for face, voice and persona, and agencies manage it per artist for those they registered.
Steps
Create your rights wallet. Registration is free.
One frontal photo registers the face.
The default is no. Without consent you are on the do-not-train list.
With a public listing your rights ID appears in do-not-train.json.
Try it now
One frontal photo is enough. Training consent is separate and can change any time.
Questions
No. The list points to people by rights ID, so registration is required. It is free and takes one frontal photo.
Only holders with a public listing appear, and only display name, rights ID and profile URL. Original photos and recordings are never published.
No. Developers that honour it exclude you; for others it is a record of notice. At generation time, permission is checked only inside integrated services.
Yes, at any time. Withdrawal puts you back on the list, which is regenerated hourly.