A programmer friend recently told us what happened to him:
“Recently, I was contacted by a software development company to apply for a programmer vacancy. They asked me to take a technical test, which I took because it is usual.
The technical test requirements were very specific and very detailed. They looked like product requirements. And that made me suspicious.
So I made it clear in the interview that the code I provided them could only be used as a demonstration of the knowledge required of me and that they were not allowed to use it in production. I attached several licensing documents in which I made it clear that the copyright was mine and that I was not assigning the rights to exploit the software. I published the source code of the application in my GIT repository, to which I gave them access to analyze the code.
After a few days I check that they have accessed the repository, have deployed the service and have been using it (I entered code to inform me of such activity). So far so normal for them to evaluate me as a candidate?
After a few days, I was informed that I was not valid for the position and that the technical test was not what they expected. However, I notice that the code I did is still being used and that it is also in production!
After more than a month of this company having my code in production uninterruptedly, I contact them and let them know the situation. I let them know that I have proof that the code is being used in production and that this was in breach of the agreed terms. They completely deny it. I nevertheless threatened to sue them, but my lawyer told me there was a problem: no matter how much proof I had that they were using it, I had no proof of ownership on which to base the copyright infringement claim…”
This REAL case happens many more times than we think: we share with companies or people products resulting from our work (sketches, designs, code tests, book drafts, mockups of audiovisual content,…) for them to evaluate. And then we find that they have taken ownership of it, even monetizing it shamelessly. This is illegal, but if we do not have evidence of what happened we have very few options to file a lawsuit or claim for plagiarism or theft of intellectual property.
So how can we protect ourselves in these situations?
From iCommunity we have developed 3 evidence-generation platforms in blockchain that provide you with proof of ownership:
iCommunity’s online digital notary solution, with which you can register all kinds of documents, from contracts, agreements and confidential documents to formulas, algorithms and software code, thus protecting your intellectual property.
The online platform that allows you to register and protect your music, offering you a digitized and decentralized certification through blockchain technology, which serves as a reliable and secure proof of ownership. Through Musicdibs all the files related to the music you create will be protected.
An online copyright registration service for any digital work (books, scripts, videos, photography, audiovisual pieces…), through which you can avoid plagiarism of this type of creations.
If you want to avoid intellectual property theft or have more information about our products, contact us!