FAQ / Objections
ACC is built for sceptical rooms: rights organizations, distributors, DSPs, legal teams and investors. The standard becomes credible when its limits are explicit.
No. ACC is deliberately not an AI detector. ACC verifies a submitted creator declaration, timestamp, audio hash, declaration hash, certificate status and public verification URL. It gives the market a readable declaration layer instead of a black-box accusation.
A declaration is not blind trust. It creates accountability: an identified declarant, category, timestamp, hashes, public proof, status history and future revocation or dispute handling. Markets already rely on declarations; ACC makes them structured, visible and machine-readable.
C2PA can carry technical provenance and content credentials. ACC is the music-specific declaration and certification layer: HUMAN, SEMI-MIX or AI GEN, bound to an audio work, public mark, verification boundary, ledger event and ACC API response. The two can be complementary.
ACC does not make lying impossible. It makes false declarations traceable, attributable and operationally actionable. A false claim can move into disputed or revoked status, and partners can stop routing the mark as trusted proof.
If you are evaluating music provenance, AI disclosure, catalog certification or partner API integration, ACC is ready for pilot conversations.
Request pilot / brief