Terms of Service

Last updated: April 2026

1. Acceptance

By using Lyrics D.N.A™ (operated by SwaLay Digital / TalantonCore LLP) you agree to these Terms. If you disagree, do not use the service.

2. Service description

Lyrics D.N.A™ issues cryptographic certificates of authorship for musical compositions and sound recordings. A certificate consists of: SHA-256 content hash, 11 RFC 3161 timestamps, multi-chain blockchain anchoring, and a PAdES B-LTA digitally signed PDF.

3. User warranties

By submitting content, you represent and warrant that (a) you are the original author or lawfully authorised rights-holder, (b) the content does not infringe third-party rights, and (c) information you provide is accurate. Fraudulent submissions expose you to liability under Section 63 of the Copyright Act, 1957 and Sections 318/336 of the Bharatiya Nyaya Sanhita, 2023.

4. Platform role

SwaLay Digital acts as an intermediary under Section 79 of the Information Technology Act, 2000. We issue certificates based on the information you supply; we do not adjudicate authorship disputes. Our certificates are tamper-proof evidence of what was submitted and when.

5. Fees

Lyrics D.N.A™ certificate issuance is currently free for eligible accounts. Certain enterprise features may be paid.

6. Limitation of liability

The service is provided on an "as is" basis. TalantonCore LLP's aggregate liability is limited to fees paid (if any) in the 12 months preceding the claim.

7. Certificate immutability

A Lyrics D.N.A™ certificate, once issued, is permanent and immutable. The following are explicitly NOT possible, no matter who asks:

• Deletion. We will never delete an issued certificate from our primary record, from the Arweave permanent archive, from the blockchain anchors, or from the audit log. Not at the certificate-holder's request. Not at a support agent's discretion.
• Reissuance. An existing certificate ID (SWL/DNA/YYYY/NNNNN) is never reassigned to a different song, artist, or account. If an account is compromised, the path forward is always: issue a new certificate for the same song under the recovered account; the original cert stands as a historical record.
• Transfer. Ownership attribution on a certificate cannot be changed from one party to another. If rights are legally transferred (e.g. publisher acquisition), the original certificate remains attributed to the original creator; a new certificate may be issued under the acquirer's identity, and the historical chain is preserved.
• Post-issuance signature addition. Once a certificate is issued with its Tier 1a (eMudhra Class 2 Document Signer) + Tier 1b (SwaLay Platform Authority) + PAdES B-LTA archive timestamp, no further signatures are appended to the document. If a holder subsequently requests a higher-assurance signature (e.g. CCA-licensed Class 3 hardware DSC counter-signature), a new certificate is issued with the upgraded signing stack under a new certificate ID; the original certificate stands unmodified as a historical record. This preserves the cryptographic integrity of the archive timestamp — any post-archive modification would produce a visible “document modified after certification” warning in compliant PDF verifiers, which is itself a security property the Act is designed to surface rather than suppress.
• Court / regulator intervention. A court can only be provided evidence of a certificate's existence, cryptographic hashes, and blockchain anchors. A court order cannot retroactively modify an already-anchored certificate — the Polygon transaction, Arweave archive, and OpenTimestamps Bitcoin proof are beyond our ability to alter. A certificate may be marked "revoked" (with the original record retained in full) by a valid court order; revocation does not erase the record.

This permanence is deliberate and forms the core evidentiary value of the service. If you would not want a permanent, verifiable public record of your authorship claim, do not request a certificate.

8. Governing law

Indian law. Exclusive jurisdiction: courts of Gautam Buddha Nagar, Uttar Pradesh.

9. Changes

We may revise these Terms; material changes are announced on this page and in-app 30 days before taking effect.