We've archived these tweets where Copperhead's CEO admits to them tracking devices via unique identifiers and using them as part of the update system.
He admits that their phone sellers with Copperhead emails, etc. have databases mapping unique identifiers to the customers too.
Conversation
Replying to
His excuse is that tracking devices via unique identifiers available to update server doesn't count as tracking users. They've designed it in a way that they can ship an update targeting a device. The excuse is they don't know which user has which device, but their seller does.
1
3
25
In that same thread, he also peddles the usual lie that Copperhead is source available. Meanwhile, the sources are not published and are not available for review. Multiple researchers including a Whonix developer have attempted to get access to the sources and could not get it.
1
2
21
It's not even source available to the extent that Windows is source available. No reasonable definition of that term would apply to what they're doing. They stopped publishing their sources in December 2019. They want to hide that they just copy GrapheneOS code and do tracking.
1
3
19
Here's a fork of a few GrapheneOS repositories from 2016:
github.com/CopperheadOS-T
I created CopperheadOS in 2014 on my own time. That project is now called GrapheneOS. The company didn't exist until late 2015. I used permissively licensing for the sources until January 2017.
1
2
17
From January 2017 to mid-2018, I made a unilateral choice to license my own code (not code from others) under a non-commercial usage license. This was an attempt to prop up the company sponsoring the work. I permanently switched back to the permissive licensing after mid-2018.
1
1
14
Look back at the available archives of the code and past statements from the company and CEO. He still admitted that it was open source project with my ownership over the code even after pushing me out. His story has drastically changed over time and continues changing. It's BS.
1
1
21
Copperhead CEO deleted all his tweets prior to June 2020 along with other information despite the ongoing lawsuit. They're supposed to preserve anything relevant to the case.
June 2020 is when they maliciously registered grapheneos.ca and grapheneos.net too...
1
22