ACC

ACC privacy and data processing

Which information ACC processes, which certificate details are public and how to ask about your personal data.

acc-privacy-v0.3 / Updated: 2026-10-13

Reading guide

These explanations help you read the document. They do not replace its full wording or the recorded version of the acknowledgements you accepted.

Before submitting, check the public-data summary. The public certificate can include the declarant's name, credited creators, IPI identifiers and file metadata. An IPI identifier may connect a pseudonym to registry records. Your contact email, account credentials and audio file are not published through the public Creator form.
The public Creator form does not perform government identity, external-signature or bank checks. A separately available service must explain the data it processes before you use it.

Terms explained

ISRC, ISWC and IPI: ISRC identifies a recording; ISWC identifies a musical work; IPI identifies a creator or another party in rights-management records. These identifiers alone do not prove ownership of rights.
Hash / SHA-256: A cryptographic fingerprint used to compare the exact data in a file or record. It does not recognise the same song in a different file or establish that a declaration is true.
Email, KYC and attached documents: Email confirmation shows control of an email address. KYC means identity checks. Recording the hash of an attached document does not, by itself, validate its signature or the person's authority.

Full document wording

What data ACC processes, what becomes public and how to exercise your privacy rights.

Controller

The data controller is ART CLEARANCE CERTIFICATION Sp. z o.o., KRS 0001193252, NIP 9662211120, REGON 542695867, ul. Zlota 2/19, 15-016 Bialystok, Poland. Contact: info@artclearancecertification.org.

Data we may process

Declarant data: name, email, role or organization.
Work metadata: title, artist, creator, phonogram producer, ISRC, optional ISWC and author/IPI details.
Technical file data: name, size, MIME type and SHA-256 hash.
Declaration data: category, answers, version, timestamp and declaration hash.
Historical external-evidence metadata: file name, type, size and hash, without implying signature validation.
Certificate data: ACC ID, status, public verification URL and timestamp-proof state.
Usage and verification data: lookups, API calls, verification events, partner identifiers, timestamps and status results.
Technical logs: IP address, endpoint, time, user agent and API response status.

Audio files

ACC is designed so that a browser or partner system can calculate the audio hash without ACC needing to permanently store the audio file. If a future production workflow accepts audio files, this policy will be updated before that processing becomes standard.

Purposes

Issuing and operating ACC certificates.
Binding declarations to work metadata and hashes.
Providing public verification and partner API responses.
Running partner pilots and business communications.
Securing the system, auditing activity and preventing abuse.
Handling corrections, disputes, revocations and support requests.
Creating aggregate analytics, market intelligence and work/provenance data products connected with ACC certification.

Legal bases

Depending on the context, processing may be based on performance of a service or pre-contractual steps, ACC's legitimate interests in operating a trustworthy certification system, consent where required, or legal obligations. The exact basis may depend on the specific workflow.

Public certificate data

In the public Creator workflow, public verification, downloads and API may show declarant name, artist, credited creator, producer, author names and IPI, ISRC/ISWC, file name, size and type, category, certificate ID, issue time, declaration version and hash, recorded identity-evidence level, certificate status and timestamp evidence. The submission summary identifies the fields before acceptance. Contact emails, account credentials and raw audio are not published. An IPI may link a pseudonym to registry records. Account-connected workflows must show their own specific public-data scope.

Commercial work-data use

ACC may use certified work metadata, category, hashes, timestamps, status, ledger/anchor state, partner API events and verification activity to create reports, analytics, API products and market intelligence. This is part of ACC's business model. ACC does not sell private account, contact or identity data as a standalone product.

Consent and acceptance records

ACC may store the version, timestamp, source, accepted statements and document references connected with a certification request or partner contact form so that ACC can demonstrate what information was presented and accepted.

Service providers

ACC uses infrastructure and service providers such as Vercel, Cloudflare, home.pl and SMTP/email providers where needed for the service. An identity, signature, Open Banking or additional analytics workflow requires its own confirmed processing scope before activation; mentioning it does not announce an active check.

Retention

Certificate records, hashes and status history may be retained as long as needed to preserve verification integrity, handle disputes and protect the credibility of the standard. Contact data, correspondence and logs are retained for the period needed for the relevant relationship, security purpose or legal claim.

Your rights

Depending on the legal basis and context, you may have rights of access, rectification, erasure, restriction, portability, objection and withdrawal of consent. You also have the right to lodge a complaint with a supervisory authority.

Contact

Privacy requests should be sent to info@artclearancecertification.org.

Historical HUMAN LEGACY records

HUMAN LEGACY is issued on ACC's initiative from referenced historical metadata and chronology. It is not a creator or rights-holder declaration, endorsement or a fourth declaration class. It does not inspect or bind a specific audio file. The public record identifies the source and limitations. Its timestamp dates ACC's statement, not the historical recording. Use only the distinct HUMAN LEGACY mark, not a HUMAN declaration mark.