EU AI Act · Art. 50 · 2 Aug 2026

The consent seal
for the AI content economy.

Every brand compositing AI with real likenesses needs a provenance and licensing record. The EU AI Act requires it. Courts are already deciding who pays when it’s missing. INKAN seals the record... cryptographically, permanently, independently verifiable.

Biometric record · live preview
EU AI Act · Article 50 · enforcement begins 2 Aug 2026UK Equity: 99.6% of members demand verifiable consentSpotify × UMG (May 2026): consent + compensation confirmed
Courts are deciding now

The liability is already landing.

A signed email won’t hold up... it can be edited, back-dated, or denied. A clicked checkbox can’t prove who clicked, when, or that a real, willing human did.

INKAN turns “trust us, they agreed” into a sealed, timestamped, self-proving record. Change one comma and the seal breaks... so everyone can tell.

UK · DEC 2025

Jorja Smith / FAMM

Likeness used in an AI campaign without consent.

SDNY · JUL 2025

Lehrman v Lovo

Voice-clone claims survived a motion to dismiss.

US · 2024

ScarJo / OpenAI

The Sky voice was pulled after a likeness objection.

EU · 2025

Brad Pitt deepfake

$850K fraud committed using a synthetic likeness.

Cryptographic proof

Every consent, sealed the moment it’s given.

At the instant of agreement, INKAN signs the record with a private key and stamps it with a trusted third-party timestamp. The seal is maths... a verifiable proof bound to the exact terms and the exact moment.

  • Ed25519 signature over the canonical record
  • Trusted timestamp from an external authority
  • Append-only audit chain, verifiable offline

印 (inkan) ... the Japanese personal seal, a person’s legal signature for centuries. We made it cryptographic.

Verify a seal yourself →
The rail
01SCOPE · TERRITORY · EXPIRY

License

Live

Brands and agencies issue a fixed-fee likeness licence... scope, territory, expiry, all sealed. The consent receipt travels with the asset across every render and downstream system.

02LEDGER · SEAL · AUDIT

Prove

Live

Every action lands on an append-only audit ledger. One button re-checks the maths and confirms the whole history is intact... or points at the exact entry someone tried to change.

03CEREMONY · LIVENESS · HASH

Capture

In development

A consent ceremony, not a checkbox. The person signs once with a live face-scan; we bind the likeness to a jurisdiction-aware template, hash it, and write the seal. In active development.

Where this goes

The dashboard is the on-ramp. The API is the destination.

Today: the admin dashboard for agencies and brands. Tomorrow: the API every AI content platform embeds to issue consent at the point of creation.

A creator uploads a likeness. The platform calls INKAN. A sealed consent record exists in milliseconds. The rights are provable forever.

The dashboard is Stripe Dashboard. The API is Stripe.js. INKAN is the consent rail for the AI content economy.

The founders

A rights-infrastructure team, not a software team learning rights.

Roberto Lopez · CTO

Two decades building the mechanical-rights and royalty rails that pay artists when their music plays. He built INKAN’s ledger the same way... append-only, sealed, verifiable. Co-inventor and stack architect.

Sam Shooter · CEO

Commercial, buyer discovery, and the raise. Co-inventor. Took INKAN from a buyer conversation to a live, sealed, verifiable product. First hire this round: a senior infrastructure engineer.

The standard before the standard

Consent becomes infrastructure.

A working MVP today... sealed records, append-only audit, jurisdiction logic, regulator-ready packs, and a live likeness-licensing ledger. Open it and verify the maths yourself.