Database policy

1. What the registry is

The Human Behind maintains a public database of self-declared records about AI identities (avatars, voice clones, agents). It is a private initiative operated by AIGiner S.L. — not an official or government registry — and each record is a declaration made by the person who registers it, under their own responsibility, as set out in the terms of use.

2. What gets published

Each public record shows exactly these fields:

• Registration number (THB-year-number) and its public page address.
• Avatar name and type (avatar, voice clone, agent, image…).
• 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.

Never published: the responsible person's email address, identity documents (which we never store in the first place) and payment data. See the privacy policy.

3. Immutability of date and hash

When a record is created, the registry takes a snapshot of its data and computes a SHA-256 hash over it. The registration date and that hash can never be altered afterwards — not even by our administrators: the database itself rejects changes to them. This is what makes a record usable as evidence of priority. The exact recipe of the hash is public and documented in the record documentation, so anyone can recompute and verify it through the public API.

4. Updates and corrections

Some descriptive fields of a record can be corrected by its owner. Corrections never modify the original registered snapshot or its hash: the original evidence stays intact. If you need to rectify personal data, the privacy 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 a soft 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 the privacy 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 in claiming 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 contain only public textual data — a name and a public address — and never images, facial data or any biometric information.

8. Using the registry's data

The registry is public and free to consult, and the public API exists 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.