Recent social-media posts have accused Critical Blast Publishing of leaking a former client's unpublished book after the client ended a production engagement with us. That accusation is false. Critical Blast did not publish, distribute, upload, disclose or authorize the public release of the client's book or production files.

Protecting creators' intellectual property is not merely a courtesy. It is fundamental to our business.

What Happened

Critical Blast was engaged to prepare a client's book for publication. During the production process, we identified multiple apparent unauthorized uses of protected characters, names, costume designs and trademarked insignia belonging to other publishers.

We informed the client of those concerns and prepared a separate PDF containing visual examples of possible revisions intended to make the material more legally defensible as parody. The PDF was an advisory document; it did not replace, overwrite or permanently modify the client's original artwork.

The examples were not presented as changes the client was required to accept. The client remained free to follow them, use them as a starting point, develop entirely different revisions or decline to revise the material. The creative decisions remained with the client. Our responsibility was to identify the risks and explain what kinds of changes might address them.

The client declined to pursue revisions and chose to end the engagement. Critical Blast respected that decision. We did not publish the book, distribute the book or continue the project after the engagement ended. The client subsequently arranged to have the uncorrected material published through another provider.

The disagreement over our recommendations is separate from the allegation now being made. Whatever opinion anyone may hold about those recommendations, Critical Blast did not leak the client's book.

How the Project Files Were Handled

Throughout the engagement, the project files were maintained in a secured Google Drive folder. Access was restricted to two members of the Critical Blast production staff and three authorized members of the client's own team.

The folder was used solely to transmit working materials among those five authorized participants. It was not a public download page, promotional preview, open staging area or publicly shared archive. No outside printer, distributor, retailer or unrelated third party was given access through Critical Blast.

When the client terminated the engagement, Critical Blast removed the Google Drive folder. We did not retain it as a public or shared resource, transfer it to another location for distribution or make its contents available after the relationship ended.

Those facts are directly inconsistent with the claim that Critical Blast placed the book on the Internet for public access.

What Critical Blast Did Not Do

Critical Blast did not release the manuscript or completed book to the public. We did not post it to a file-sharing service, piracy site, public archive, social-media account or downloadable webpage. We did not distribute advance copies, transmit the project to an unauthorized third party or give anyone permission to do so.

We have preserved the relevant project records and communications. Those records document the work performed, the concerns communicated to the client, the limited access to the project files, the termination of the engagement and the removal of the shared production folder.

Because client confidentiality matters, we will not publish the client's manuscript, private communications or project files merely to conduct a social-media argument. Our refusal to expose confidential material as part of our defense should not be mistaken for an inability to document what occurred. If the allegation is submitted through an appropriate formal process, we will provide the relevant evidence through that process.

How We Protect Client Property

Critical Blast Publishing and Critical Blast Logistics routinely receive unreleased manuscripts, comic-book pages, cover artwork, mailing lists and campaign materials. Creators must be able to entrust those materials to us before their projects are announced, published or shipped.

We do not claim ownership of a client's intellectual property merely because files were supplied for production. We do not use that material for unrelated purposes, and we do not knowingly disclose or distribute it without authorization.

That obligation does not disappear when a business relationship ends. A client's decision to discontinue a project does not give us the right to release that project, retaliate against the client or expose the client's unpublished work. Critical Blast has never treated the termination of an engagement as permission to disclose a creator's property.

Why the Editorial Concerns Were Raised

Parody can be a legitimate protected form of expression, but labeling a work 'parody' does not automatically make every use of a copyrighted character or trademark legally defensible. Context, transformation, commentary and potential consumer confusion all matter.

When Critical Blast identifies material that may expose a creator, publisher, printer or distributor to an infringement claim, we raise that concern. The creator may accept our recommendations, propose another solution or take the project elsewhere. Critical Blast is not obligated to disregard identified risks and assume responsibility for producing material we believe may violate another party's rights.

That disagreement explains why the production relationship ended. It does not support the separate and false claim that Critical Blast subsequently leaked the book.

Our Position

Creators retain their intellectual property when working with Critical Blast. We take seriously both sides of that principle: we protect the property entrusted to us, and we avoid knowingly reproducing property belonging to others without permission or a legally defensible basis.

Management will not litigate private client matters through an endless exchange of social-media accusations. We will, however, respond clearly when a false claim attacks the trust on which our publishing and fulfillment businesses depend.

The project files were confined to a secured folder shared among authorized Critical Blast staff and members of the client's own team. That folder was removed when the engagement ended.

Critical Blast did not leak this client's book. We stand behind that statement and the records supporting it.