Features

Sign, protect, and declare your original work – verifiably

With Liccium, you digitally sign your content, bind your rights and metadata to it, and publish a declaration that third parties – platforms, AI systems, anyone – can discover and verify. Your files stay with you; only the declaration is public.

Capabilities

What Liccium does

Sign your content

Digitally sign your work with your own certificate or verifiable credential, binding it to your identity and the rights you declare. The signature is timestamped and can be verified by anyone.

Rights and metadata binding

Your rights and metadata are inseparably bound to the content’s fingerprint and travel with it in the declaration, so third parties – platforms, AI systems, registries – can discover and access them.

Content fingerprint (ISO 24138)

Liccium generates a content fingerprint for images, text, audio, and video. It is derived from the content itself, so the work can still be matched after copies, edits, and re-encodes.

Machine-readable AI preferences

State whether your content may or may not be used for AI training and text-and-data-mining – opt out, attach a licence, or flag AI involvement with FAIA – in a form crawlers and AI systems read directly.

Verified identity

Attach a verifiable identity to your declarations, or declare pseudonymously – using certificates or verifiable creator credentials.

Deduplication and content matching

Find exact copies and near-duplicates across your library or the web.

Declare web content

Timestamp and declare web pages and images. Provide a URL and Liccium fingerprints the content directly.

Automatic declarations

Link your Bluesky account and Liccium declares each tagged post automatically, running on Liccium’s servers so it works when your computer is off.

Update or withdraw over time

Update rights and metadata after publication, or withdraw a declaration. Your signed history stays valid.

Plugins

You choose what to declare

You decide which rights and metadata to declare publicly, per file.

Rights and reservations

TDMRep

State whether your content may be used for text-and-data-mining and AI training, in machine-readable form (W3C TDM Reservation Protocol).

Creative Commons

Attach a Creative Commons licence stating what others may and may not do with the work.

Sector metadata

IPTC

The photo-industry fields agencies and publishers expect: creator, credit, copyright, keywords, licence.

Text

Bibliographic metadata for written works: authors, title, publisher, ISBN, DOI.

Audio

Release metadata for audio: artist, album, and industry IDs (ISRC, ISWC, ISNI).

Trust and provenance

FAIA

Flag whether and how AI was involved: Human-Created, AI-Assisted, or AI-Generated.

C2PA

Attach a tamper-evident Content Credential that C2PA-aware tools (Photoshop, Firefly) can read, bound to the content by its fingerprint and stored in a sidecar, so the original file is unchanged.

How it works

Fingerprint content, bind metadata, declare

Step 1

Fingerprint

Liccium generates the content fingerprint for your work.

Step 2

Bind

Attach your rights and metadata, inseparably, to that fingerprint.

Step 3

Declare

Sign and publish a verifiable declaration to the public registries.

Join the waiting list

Be one of the first to use Liccium Desktop.

Join the waiting list