Does a watermark match prove authorship or ownership?
A match means the detector found a CRC-valid codeword under your key. If that ID is in your manifest, it points to a distribution record. It does not establish authorship, ownership, creation time, intent or who leaked the copy; anyone with the tool and the key can embed the same ID, and an ID can be reused.
How Aureal handles it
The match is a signal-level result: the key derives a spreading sequence, the sequence carries a 32-bit payload and a CRC, and the detector found that codeword with enough confidence. The manifest then maps the ID to a record you created. Neither step asserts who created the audio, who owns the rights, or when any of it happened. The ID is a pointer, not a signed statement, and the key is shared with everyone who embeds or detects. A copy can be passed on, stolen, re-tagged by someone with the key, or averaged with other copies until recovery fails. Treat the match as a lead that connects a file to a distribution record you control.
Common failure mode
“A matching ID proves the recipient leaked the file.”
Why it fails: The ID identifies a copy and a record, not a person or an act. The recipient's copy can be shared or stolen, the ID can be reused, and anyone with the key can embed it in another file. The audit tool's own verdict says a match is not proof of who leaked it.
Verified example
Write the finding at the level the evidence supports:
1. Report the CRC-valid ID, key and confidence.
2. Report the manifest record (name, filename, SHA-256, date).
3. Compare the leaked file hash with the recorded hash.
4. Preserve the original, the copy and the detection report.
Say "the file carries ID X, which maps to record Y", not "Y leaked it".Example only. Validate against your own audio, codec and processing chain.
Scope and limits
- A match is not authorship, ownership, creation time or chain of custody.
- It does not prove who leaked a copy or that a leak occurred.
- Anyone with the key can embed or reuse an ID.
- Averaging independently tagged copies can defeat recovery.
Frequently asked questions
Can I name the recipient in a report?
You can name the record the ID maps to and the file hash you matched. You cannot conclude from the watermark alone that the recipient leaked the file; state the limit explicitly and keep the other evidence separate.
Can someone forge my watermark?
Anyone who has the key and the tool can embed the same ID. The ID is not signed, and the 32-bit space is a pointer rather than an identity. Keep the key private and use contracts and independent records for attribution.
Related topics
Test the actual delivery chain. A fixture result is a starting point, not a guarantee for your material.
Open the Studio →