DIG-DIS-2024
Public-redacted record concerning unresolved distribution-control, takedown-response, metadata-authority, platform-wide removal authority, and royalty-accounting questions involving Dig Dis!. No legal conclusion is made.
This page is a public-redacted evidence record concerning Dig Dis! distribution-control, takedown-response, metadata-authority, platform-wide removal authority, and royalty-accounting questions.
The reporting-side individual, affected catalogue owner, reporting-side organization identity, private emails, account identifiers, release identifiers, payment identifiers, country details tied to the affected side, and raw private correspondence are withheld from this public version.
The record focuses on whether catalogue control, takedown handling, metadata-control workflow, platform-wide removal authority, and royalty-accounting processes were verifiable after a reported termination / disengagement request.
No finding is made regarding intent, legal liability, copyright infringement, discrimination, abuse, or personal wrongdoing.
No legal conclusion is made on this page.
It is a public-redacted evidence record concerning unresolved distribution-control, takedown-response, metadata-authority, platform-wide removal authority, and royalty-accounting questions involving Dig Dis!. It does not make legal conclusions.
The core issue is an unresolved distribution-control, takedown-response, metadata-authority, and royalty-accounting gap: whether releases remained visible or distributed after a reported termination / disengagement request, whether takedown and accounting questions were handled with verifiable logs, and whether the release workflow created metadata-control burdens.
A distributor with catalogue control may be able to request or trigger broad removal across a DSP network. The public-safe issue is whether authority boundaries, takedown logs, catalogue-return confirmations, and written explanations are verifiable.
Dig Dis!'s public materials emphasize full control, transparent monthly invoices, immediate invoicing, personal service, label-management tools, and release metadata workflows. The reviewed record raises the operational question of whether catalogue control, metadata authority, takedown response, platform-wide removal authority, and royalty accounting matched those public claims after disengagement.
Because distribution metadata should remain verifiable at the delivery-record level. If downstream DSP metadata becomes the practical source for upstream delivery, capitalization, remix-version names, title formatting, and correction timing may become difficult to control before wider propagation.
No. The record preserves a reported metadata-control and workflow-verification issue, including Spotify-derived metadata dependency and limited pre-delivery editing control. It does not make a technical-defect finding.
It does not determine legal liability, intent, copyright infringement, deceptive conduct, discrimination, abuse, personal wrongdoing, technical defect, final payment liability, or an exact unpaid amount.
Relevant documents would include dated takedown confirmations, catalogue-return logs, DSP removal records, royalty statements, payment records, app metadata edit logs, DSP delivery logs, payout-threshold records, and written responses from Dig Dis! explaining post-termination distribution, metadata, and accounting status.
Contract excerpts, account notices, takedown requests, royalty statements, payment records, catalogue-control messages, and preserved correspondence where available.
DSP, distributor, store, payment processor, service-provider, regulator, authority, or other third-party responses where available.
Public page availability, store visibility, metadata visibility, archive status, DNS / HTTP signals, and public route checks.
Identifiable statements summarized with private identifiers removed.
Reasonable interpretation based on A-D material, always labeled as inference and not presented as a primary source.
The reviewed record preserves a reported upload-first, correct-later workflow risk. In distribution workflows, incorrect capitalization, remix-title text, version names, artist joins, or release metadata may propagate across DSPs before correction is completed.
The record preserves the reporting-side position that certain releases remained visible or distributed after a reported termination / disengagement request.
The record preserves repeated takedown / removal requests and an unresolved response gap. This is treated as an operational verification issue, not as a legal finding.
The record separately preserves the risk that a distributor with catalogue control may be able to request or trigger broad removal across a DSP network. The public issue is whether authority boundaries, takedown logs, catalogue-return confirmations, and written explanations are verifiable.
The record preserves a reported unpaid-revenue / royalty-accounting issue for the relevant period. Factualist does not state that funds were diverted, misappropriated, or finally adjudicated as payable.
The amount and payout threshold remain source-level accounting questions. Factualist preserves the reported unpaid-revenue issue and invites Dig Dis! to provide royalty statements, payment confirmations, payout-threshold wording, or account-level explanations.
The record concerns whether catalogue control, return, and removal processes were handled in a verifiable and timely manner after the relationship deteriorated.
The record includes complaints that Dig Dis! system handling created metadata-control friction and release-management difficulties, including reported difficulty correcting capitalization, remix-version naming, and detailed metadata before wider delivery. This is treated as platform-operation and metadata-authority context.
Public-redacted source index
DIG-DIS-2024 public-redacted source index listing reviewed source categories, evidence grades, redaction status, public URLs, and source summaries for this record.
Internal publication review for public-facing scope, reporting-side anonymity, no-legal-conclusion framing, and correction-ready wording.
Private evidence inventory includes reported termination / disengagement context, takedown-request summaries, distribution-visibility checks, royalty-accounting questions, catalogue-control correspondence, and metadata-control concerns. Raw files, private names, reporting-side organization identity, affected catalogue identity, release identifiers, account identifiers, payment identifiers, country details tied to the affected side, and private correspondence are withheld.
Official English public materials market "Full control over your music!", transparent monthly invoices, immediate invoicing, and personal service. This source is used only as public-claims context for comparison with the reviewed operational record.
Official public tools materials state that digdis.app gives label management in one place, describe full control, and describe rokket! as a release-creation workflow where all relevant metadata can be added before worldwide delivery. This source is used only as public metadata-positioning context.
Official German public materials state "Aber kein Künstler hat etwas zu verschenken" and describe quick email response, transparent and fast work, and monthly accounting. This source is used only as public-claims context.
Official Royalty Statements public materials position correct, transparent, and timely royalty statements as important in the music business. This source is used only as public accounting-positioning context.
Reviewed summary preserves the reporting-side position that takedown / removal requests remained unresolved or inadequately documented after a reported termination / disengagement request. The public record treats this as an operational verification issue, not as a legal finding.
Reviewed summary records the risk that a distributor with catalogue control can initiate broad DSP-network removal or withholding actions across multiple platforms. This record does not state that any removal was unlawful; it records why authority boundaries, logs, and written explanations matter.
Reviewed summary preserves a reported unresolved royalty-accounting issue for the relevant period. Factualist does not state that funds were diverted, misappropriated, or legally owed by final determination.
Reviewed summary preserves a reported metadata-control issue: the release workflow appeared to rely on Spotify-derived metadata, with limited pre-delivery control over capitalization, remix-version naming, title formatting, and post-import correction handling. This is preserved as a metadata-authority and workflow-verification issue, not as a technical-defect finding.
Reviewed summary preserves a reported small-balance payout / unpaid-revenue question. The exact wording, threshold, amount, and applicability remain subject to screenshot-level or account-record verification and are not presented as confirmed public claims.