ACC / music origin

Creator workflow: issue proof

0Issued
0SEMI-MIX
0API checks

Creator

Music work intake

Put a serious origin mark on your music. ACC hashes the audio in your browser, records your creator declaration and returns a public certificate, mark, QR, PDF and partner-readable API object.

1. AudioHash locally. ACC does not store the audio.
2. IdentityChoose Level 1 email or Level 2 signed evidence.
3. DeclareSelect HUMAN, SEMI-MIX or AI GEN.
4. ProofIssue the certificate and open public verification.
No audio upload to ACCThe browser calculates SHA-256 locally. ACC stores the hash and declaration data.
Public certificate registerOpen your certificate's public proof and download pack after issuance. The register is not a private account.
Musical work identifiers

ISWC and IPI are optional and public when supplied. Format checks do not verify registry assignment, identity or rights. An IPI may link a pseudonym to registry records.

Existing ISRC
No file selectedUpload audio or generate a reference WAV
Audio hash pending
HUMAN

I declare that the material creative expression of the work was created by human author(s), and that generative AI did not produce material creative output claimed as part of the work.

HUMAN declaration ritualThis work is mine. Human-made.

I am placing a public origin mark on this music and I understand that the declaration is recorded.

Typed signature and acceptance are recorded in the declaration payload.
ACC Use, Certification & Work Data TermsOne recorded acceptance package for issuing a certificate, publishing proof, enabling partner API verification and using work/provenance data.
0/12
Registered statements

contractI accept the ACC Terms of Use, Certificate Policy, Creator Declaration and Certification Mark Rules.

privacyI have read the ACC Privacy Policy and understand who controls the submitted personal and work-related data.

declarationI confirm that I am authorized to submit this work, metadata, hash and declaration for ACC certification.

declarationI confirm that the declaration and metadata are accurate to the best of my knowledge.

public-proofI understand that ACC certificates are designed for public verification and partner-readable API access.

work-dataI allow ACC to collect, store, analyze and use work metadata, category, hashes, timestamps, status, ledger/anchor data and verification events to operate and improve ACC.

work-dataI grant ACC a worldwide, non-exclusive and royalty-free license to create, offer and sell work-data products, analytics, API outputs and market intelligence based on ACC certificate and provenance data.

work-dataI understand that ACC may use aggregated or statistical data about certified works, categories, statuses, markets and verification activity for research, reporting and commercial analytics.

privacyI understand that ACC's data business concerns work and provenance data; ACC does not sell private account, contact or identity data as a standalone product.

technical-boundaryI understand that ACC normally stores hashes and certificate data, not the raw audio file, unless a separate workflow explicitly says otherwise.

technical-boundaryI understand that ACC records declarations and proof data, and does not claim to independently detect AI.

trust-safetyI understand that ACC may correct metadata, limit use, mark a certificate as disputed or revoke status to protect the credibility of the ACC standard.

Level 1

Certificate

No certificate selected