Skip to content

Claims

A claim links an existing record to the person it actually belongs to. If there is a record about you, or about your avatar, that you do not control, a claim is how you take it over or flag it for review.

  • The record is marked unclaimed. Some records exist in the registry before their owner arrives; claiming is how you take control of one.
  • Someone registered an avatar that uses your identity (your name, your voice, your likeness) without your permission. A claim opens a review by the team.
  1. Open the record’s page. Only verified records have a public page: you will find them in the public directory or through their direct link. If the record that concerns you is not public (registered but not verified), it has no page to claim from. In that case write to the team at legal@thehumanbehind.com and the review follows the same path.
  2. Use the “Claim this record” button.
  3. Provide your email address and a short explanation of your relationship to the avatar. No account is required to submit a claim.

Two practical limits keep the system clean:

  • Submissions are bot-protected, so automated spam does not get through.
  • A given email address can have at most one pending claim per record at a time.

Your email stays private. The address you provide with a claim is visible only to the review team. It is never published, never added to the record and never exposed through the API.

  1. The team receives and reviews the claim.
  2. You are contacted by email with the next steps. The review may ask you to demonstrate control of the profile or channel where the avatar operates (for example, posting a one-time code, or replying from an official address).
  3. If the claim is approved, the record is linked to your account (you will be asked to create one if you have none) and you gain normal owner control over it: you can edit the descriptive fields or unpublish it. The THB number, the date and the slug stay immutable.
  4. If it is rejected, you are told why. You can provide further evidence and try again.

Claiming never changes the sealed parts of a record. It changes who controls the record, not what it attested and when.

We mark the record under dispute from the first moment, and it stays that way for as long as the dispute lasts. A record under dispute still exists, with its date and its hash intact, but it stops serving as proof of priority against anyone.

We ask both sides for the same thing: to show that they control the channel where the avatar appears. If one shows it and the other does not, the record passes to whoever showed it. If neither does, the record stays under dispute: we are not the ones who decide that.

We are not a court. We do not decide who owns an avatar. We put on record who declared it, when, and that somebody contested it.

The mark is visible on the record’s page and in the public API, in the disputed_at field, so that a machine reading the registry sees the same as a person. Marking or lifting it never touches the registry number, the registration date or the content hash: not on a complaint, not on an internal order, not even if both parties ask for it together.

If your issue is not ownership but the content of a record, for example a record you believe is fraudulent or unlawful, you can also reach the team directly at legal@thehumanbehind.com. The removal and complaint procedures are described in the database policy.

No. You submit a claim from the record’s page with just an email and a short explanation. If the claim is approved you will be asked to create an account so the record can be linked to you.

No. The email you provide is visible only to the review team. It is never published, never added to the record and never exposed by the API.

Claims are reviewed by a person, so timing varies with volume. You are always contacted by email with the outcome or with a request for more evidence.

The record is not about ownership, it is harmful content. What now?

Section titled “The record is not about ownership, it is harmful content. What now?”

That is a different track. Write to the team directly and follow the removal and complaint procedure in the database policy, linked below.