STEP 01
Create or import
Generate with a verified MEGGA clone, or import your own content.
MEGGA Shield
One public certificate per generation.
Identity, provenance and compliance, sealed into the file at generation and readable by anyone. Built for the EU AI Act.
Standards
Two open standards and one fingerprint.
Anyone can read a certificate against public specifications, with no account.
C2PA Content Credentials
A signed manifest that binds the creator, the model and the timestamp to the file.
Adobe TrustMark
An invisible watermark in the pixels. It survives re-encoding and cropping.
Perceptual fingerprint
A hash of the pixels themselves, to recognize the asset once the manifest is stripped.
Robustness
Two ways to protect. One survives a re-upload.
A social re-upload strips metadata and re-encodes the pixels. Toggle the file state to see which layers survive.
Fingerprint
- C2PA manifest
- Perceptual hash
- Public anchor
Watermark embedded
- C2PA manifest
- Invisible watermark
- Perceptual hash
- Public anchor
Illustrative: the watermark lives in the pixels and survives the re-encoding that strips metadata.
Why it holds up
Built differently from likeness crawlers.
Monitoring tools guess from the outside. Shield plants the proof at the source.
| Approach | Probabilistic monitoring tools | MEGGA Shield |
|---|---|---|
| Detection | Probabilistic face match, false positives included | Deterministic signal planted at creation |
| Reference | Scraped or user-uploaded photos | KYC-verified, consented identity |
| Survives re-encoding | Re-detection, best effort | Invisible watermark survives crop, JPEG and re-uploads |
| Verifiable by third parties | No | Certificate, watermark and fingerprint, readable without an account |
Web-scale monitoring comes later. Shield already adds what a crawler cannot: provenance, identity and robustness.
How it works
Build the proof. One click at a time.
Seal each layer yourself. This is the chain Shield runs on every asset.
- 1Create
- 2Certify
- 3Notarize
- 4Verify
- 5Monitor
STEP 02
Certify against a verified identity
Bound to a verified creator: KYC for individuals, KYB for brands, consent before training. Then the Shield stack is sealed into the file.
STEP 03
Notarize independently
With version 1, the fingerprint will go to a public, append-only record, so origin and ownership stay verifiable without us.
STEP 04
Verify anywhere
A platform, a regulator, a journalist or a buyer reads the certificate against open standards, with no login.
STEP 05
Monitor and enforce
On the roadmap: Shield will track where certified content travels and turn confirmed misuse into takedown claims, with a tamper-evident evidence trail.
Click to seal each layer.
Where it stands
Shield is in private beta.
Certificates carry C2PA Content Credentials, an invisible watermark and a perceptual fingerprint today. Public anchoring arrives with version 1.
Get in touch
Put Shield on your content.
Ask for a technical walkthrough, or for help integrating Shield into your pipeline.