diff --git a/2026/08/2026-08-19-backdrop.md b/2026/08/2026-08-19-backdrop.md new file mode 100644 index 0000000000..b52aed73fa --- /dev/null +++ b/2026/08/2026-08-19-backdrop.md @@ -0,0 +1,133 @@ +While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s). + +--- + +One or more repositories in this DMCA takedown notice has been processed in accordance with GitHub's prohibition on sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, and/or software for bypassing checks for product licensing keys. + +You can learn more in [GitHub's Acceptable Use Policies](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies). + +--- + +Before disabling any content in relation to this takedown notice, GitHub +- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work). +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). + +To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice). + +--- + +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** + +Yes, I am the copyright holder. + +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** + +No + +**Does your claim involve content on GitHub or npm.js?** + +GitHub + +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** + +I am [private], the [private] of Backdrop and an authorized representative of Cindori AB. Cindori AB owns the copyright in the proprietary Backdrop macOS application, and I am authorized to submit this notice on the company’s behalf. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +The copyrighted work is Backdrop for macOS, version 2.6.15 build 119, a proprietary commercial computer program developed and published by Cindori AB. The protected work includes Cindori AB’s original compiled application code, the BackdropWallpaper helper application, BackdropDaemon, compiled interface assets, application icons, data models, and other original application resources. + +The application is distributed under Cindori AB’s name and signed with the Apple Developer ID “Developer ID Application: Cindori AB (ZQK6SX26CE).” Cindori AB has not authorized the reported GitHub user to reproduce or redistribute these materials. + +Backdrop includes separately licensed third-party frameworks. This claim is limited to the original software and assets owned by Cindori AB and does not assert ownership of those third-party components. + +**If the original work referenced above is available online, please provide a URL.** + +https://cindori.com/backdrop + +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** + +**Based on the above, I confirm that:** + +Specific files within the repository are infringing + +**Identify only the specific file URLs within the repository that is infringing:** + +The following files are direct, byte-for-byte copies of Cindori AB’s proprietary Backdrop 2.6.15 build 119 executables and original compiled assets: + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/MacOS/Backdrop + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/BackdropWallpaper.app/Contents/MacOS/BackdropWallpaper + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/BackdropWallpaper.app/Contents/Resources/BackdropDaemon + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/AppIcon.icns + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/Assets.car + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/Backdrop.momd/BD.mom + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/BackdropWallpaper.app/Contents/Resources/AppIcon.icns + +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/Backdrop.app/Contents/Resources/BackdropWallpaper.app/Contents/Resources/Assets.car + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +Yes + +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** + +Backdrop uses a license-validation system to control access to its paid functionality. Under normal operation, a user must activate the application using a valid license key issued following an authorized purchase. + +Backdrop records the validated license, associated plan, and validation timestamp. It periodically determines whether the licence must be revalidated with Cindori’s licensing service. Without a recognized paid plan, the application remains in its limited trial state, including usage restrictions and watermarking. A valid monthly, yearly, or lifetime licence unlocks the corresponding paid functionality. + +These measures control access in the application’s ordinary operation by requiring authorized licence information and validation before paid functionality is enabled + +**How is the accused project designed to circumvent your technological protection measures?** + +The accused project contains an installer created and distributed specifically to bypass Backdrop’s licence-validation system: +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/install.sh + +The installer does not obtain or validate an authorized licence. Instead, it creates a fabricated Backdrop licence record containing a fake licence code and sets its lastValidatedAt value to December 31, 2099. This causes the application’s revalidation logic to treat server validation as not yet required and skip contacting the licensing service. + +The installer also writes Backdrop’s locally stored active-plan value as lifetime, causing an unlicensed installation to be treated as having a lifetime licence. + +The repository’s README explicitly instructs users to run this installer and describes the result as making any copy of Backdrop operate as lifetime-licensed: +https://github.com/User319183/Backdrop-NoLicense/blob/bd2a7a338b79d09bdae4242a95779041dcc4fe6a/README.md + +The project is therefore designed and marketed specifically to avoid authorized licence activation and enable access to Backdrop’s paid functionality without purchasing or validating a licence. + +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and must be identified separately. Please read more about forks. As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** + +**Is the work licensed under an open source license?** + +No + +**What would be the best solution for the alleged infringement?** + +Reported content must be removed + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +GitHub username: User319183 +GitHub profile: [private] +Name used in the repositories: [private] +Public website: [private] +Public contact email: [private] + +The repository owner also acknowledged receipt of [private] direct removal request by email on August 16, 2026, but declined to take it down. + +**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** + +**I have taken fair use into consideration.** + +**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** + +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +[private] + +**Please type your full name for your signature.** + +[private]