Database policy
The rules of the registry itself: what is published, what can never change, and what happens when a record is unpublished.
Last updated: 20 July 2026
1. What the registry is
TheHumanBehind maintains a registry of self-declared records about AI identities (avatars, voice clones, agents, images, video and music). A free record is a private record of standing for its owner; only a verified record becomes public. It is a private initiative operated by AIGiner, S.L., and it is not an official or government registry. Each record is a declaration made by the person who registers it, under their own responsibility, as set out in theterms of use.
2. What gets published
Registering does not publish anything: a free record is private to its owner. Only once a record is verified does it become public, and its public page then shows exactly these fields:
- Registration number (
THB-year-number) and its public page address. - Avatar name and type (avatar, voice clone, agent, image, video or music).
- Declared scope (general, or sensitive: health, finance, legal…).
- Where it operates (the declared profile, website or channel).
- Name of the responsible person.
- Registration date and time (ISO-8601 UTC).
- The record's cryptographic hash (SHA-256), so anyone can verify its integrity.
- Its seal level: green Registered or gold Verified.
- The description written by the owner, and the image, video or voice sample attached to the record.
- Whether the record is under dispute, and the date the dispute was opened. The owner cannot remove this mark.
- If the owner offers their work professionally, that fact and the title they chose for it.
Never published: the responsible person's email address, identity documents (which we never store in the first place) and payment data. See theprivacy policy.
3. Immutability of the number and the date
When a record is created, the registry takes a snapshot of its data and computes a SHA-256 hash over it. The registry number and the registration date are protected by a database rule that rejects any change, including from our own administrators. This is what makes a record usable as evidence of priority. The exact recipe of the hash is public and documented inthe record documentation, so anyone can recompute and verify it through thepublic API.
4. Updates and corrections
Some descriptive fields of a record can be corrected by its owner. When that happens the hash is recomputed, so it always matches the record as it stands today, and the previous version is archived permanently in an append-only ledger that nobody, ourselves included, can rewrite or delete. Nothing is erased by a correction: the earlier evidence stays, alongside the new one. If you need to rectify personal data, theprivacy policy explains your rights.
5. Unpublishing a record
You can unpublish a record at any time. Because the registry's credibility depends on its history not silently disappearing, unpublishing is asoft removal:
- The record's data stops being published on the website and through the API.
- The record's page returns an HTTP 410 (Gone) response with a minimal notice: a record existed at this address and was unpublished. No personal data is shown.
- The registration number is never reused by another record.
This minimal trace protects everyone: it prevents a registry where records can vanish without a mark, which would undermine the value of every remaining record. Data protection erasure requests are honoured as described in theprivacy policy.
6. Claims and disputes
If a record impersonates you, uses your name without authorisation or infringes your rights, you can dispute it. The process is described inclaiming a record; you can also write directly to legal@thehumanbehind.com. We review every claim, may ask both parties for evidence, and can suspend a record while a dispute is examined.
7. Third-party and unclaimed records
Today, every record is created by the person who declares responsibility for it. If the registry ever includes unclaimed records created from public information (so their owners can claim them), those records would stay private (not listed in the public directory or served by the public API) until claimed and verified, and would containonly textual data (a name and a public address) andnever images, facial data or any biometric information. Claims for records that are not public are handled by email, as described in section 6.
8. Using the registry's data
The public directory and thepublic API (which expose only verified records) are free to consult and exist precisely so third parties can verify records. What is not allowed:
- Wholesale extraction or re-publication of the database to build a competing registry (see the intellectual property policy on database rights).
- Using registry data to harass or profile the people behind records.
- Feeding registry data into facial recognition systems or any biometric identification database.
9. Changes
We may update this policy. We will publish the current version on this page with its update date; changes never affect the immutability guarantees of records that are already registered.
See also how a record and its hash work, the security page and theterms of use.