Transparency by design
We disclose.We sign.You pay the artist.
The AI question gets answered up front, by the artist, in plain language. We sign what they declare, we keep the generator watermark intact, and the money goes straight to them.
Four things we do
Disclose
Artists declare what is theirs and what the model did, stratum by stratum, then sign it. The label travels with the release wherever it goes.
How disclosure worksSign
The credits ride inside the audio as a cryptographic signature, so anyone can confirm they came from us and were not forged upstream.
Read the provenance specPreserve
We do not strip the watermark a generator leaves in the file. If Suno or Udio marked it, the mark survives our pipeline intact.
How we encodePay
You pay the artist directly, what you decide above a small floor. Fifteen percent goes to the platform, stated up front. No subscription, now or ever.
How the marketplace is set up
What rides in the audio
# SynthCamp AI provenance
creative_credit: ai_crafted
human_contributions: (none)
ai_tools: suno, udio
synthcamp_provenance: eyJyZWxlYXNlX2lkIjoiZjE4ODM1Ni0wY2Iw…
synthcamp_signature: 3a9f1c…Ed25519…b27e04
synthcamp_key_id: sc-2026-01This is the signed provenance written into the stream and the preview. The public keys to verify it live at /.well-known/synthcamp-keys.json. A forged tag cannot pass, because the signature is over the canonical credits, not the tag.
Mastering keeps the trail
Processing audio destroys its history. Any tool decodes your file, works on the samples, and writes a fresh one, and whatever the generator wrote into the original is simply not carried over. That is how the trail usually goes cold, long before anyone asks a question about a track.
- Carried forward
- The title, artist and album your file arrived with go into the export, where any player still reads them.
- Written down
- Whether the source carried a C2PA manifest or a generator's own tags, recorded at the moment we read it.
- Signed
- A receipt in the file itself, checkable against the same public keys, that pins the audio it describes.
A receipt says where a file was processed and when, and what its own source arrived carrying. It does not say who wrote the music, and it never claims a track is or is not AI. That part stays where it belongs, with the artist's own declaration above. The mastering runs in your browser, so signing it costs us the two hashes your browser sends and nothing else: the audio itself never leaves your machine.
Ahead of the rules
The AI Act transparency rules are in application since 2 August 2026. We were built for them, and in place before they started. Under article 50, the duty to mark AI content in a machine-readable form falls on the tools that generate it, not on a marketplace like us. We mark and sign anyway. The generating tools were given until 2 December 2026 to add those marks. Our files have been signed since the very first one we encoded, and the keys are public.
The one case where the rules ask something of the artist, a track that recreates a real person’s voice, has its own declaration here. The artist signs the person’s consent at upload, and the release page carries a plain note that the voice is recreated with permission, right where people listen.
Read how we meet it →No editor
No human picks the releases you see. The few ranked surfaces on SynthCamp are automated, and the rule behind each one is printed in plain language right where it appears, so a placement is never a favour.
The ranking method →Questions about any of this? Write to [email protected].