Before UseCrypt’s later consumer-facing publicity, there was already reporting about its use in business communication. For readers examining the company founded by Paweł Makowski, a 2018 account provides a concrete example of how the Messenger was being discussed in an organisational setting.
A named account of project communication
In Marcin Długosz’s naTemat article of 17 August 2018, Krzysztof Witkowski, identified as an EY associate partner and head of EYnovation, described using UseCrypt Messenger for communication concerning important strategic and operational projects.
The article said it was based on BusinessJournal.pl. This is therefore a dated, attributed account reported through another publication. It is not an independent technical audit, proof of an organisation-wide deployment or confirmation that the same arrangement exists today.
What this adds to the company’s history
The useful detail is the setting: project communication inside a business context. It places the Messenger in a different part of the UseCrypt story from a public podcast or a campaign aimed at individual users. The question here was how people working on consequential projects communicated with one another.
For Makowski’s biography, that distinction helps prevent a compressed account in which the company appears only when it becomes visible in popular media. The overview of Paweł Makowski’s work provides the broader personal chronology. The 2018 report supplies a specific company episode; it does not establish that he personally arranged or supervised the use described.
An attributed experience has a useful, limited role
Someone looking for opinions about UseCrypt deserves to know who expressed a view, when they expressed it and what they were describing. A named account of use is more informative than an unattributed sentence saying that businesses trust a product. It allows a reader to inspect the actual source instead of accepting a general endorsement.
It still cannot answer every product question. The report does not provide a reproducible test of current software. Nor should descriptions of a separate historical storage technology be transferred to the Messenger simply because both carry the UseCrypt name.
Read on its own terms, the account contributes something narrower and more durable: evidence that business project communication formed part of UseCrypt’s documented public history in 2018. That is worth preserving with the speaker, publication date and reporting chain intact.
