Indonesian-ASR-11-Class-Dataset / docs /ETHICS_AND_CONSENT_SCOPE.md
Atika88's picture
fix: sanitize public paths [ab6fd16c4a0f] (#2)
c65fe8b
|
Raw History Blame Contribute Delete
1.97 kB
# Ethics and consent-scope documentation
The retained NSS-ID study approval is from LPPM Universitas Sriwijaya, no. 0306/UN9.LPPM/SB3ADM/2025, with approval dated 30 June 2025. The private documentation includes twenty recording-consent forms and twenty participant addenda addressing open Hugging Face distribution, CC BY 4.0 reuse, AI/model training, derivative products, potential commercial use, residual voice-identification risks, and limitations on withdrawing distributed copies. Each supplied addendum shows the agreement option selected and visible signatures.
The supplied package also contains a signed principal-investigator request identifying NSS-ID and the original approval, together with an LPPM decision dated 7 September 2026 selecting that the existing approval is sufficient for the publication activities described in the request. The document owner identifies these as parts of the same package and reports that the participant addenda were prepared before initial Hugging Face publication, with the institutional determination obtained later. Local document review is not independent authentication of signatures or historical consent dates.
Signed forms, identity links, scans, and personal contact information are retained privately and are not deposited with the public dataset. Speaker labels are pseudonyms; voices may remain identifying and are not anonymous.
Participant consent and an ethics determination do not independently establish third-party licensing rights for every component. Rights and applicable service terms for synthetic gap-fill audio require a separate assessment; this path-sanitization maintenance update does not certify that assessment or change the dataset license. Sanitizing the current tree also does not erase earlier repository revisions, distributed copies, or model derivatives. Any necessary historical-privacy remediation requires a separate documented decision and appropriate repository support.