Welcome to BeatcanProtect! Heres how it works:
The basic premise of copyright is simple: if you create something for yourself, you own the intellectual property rights. So that's not the problem. The problem is that it's often hard to prove that something was really created by YOU. Digital copies are identical, so if someone makes a copy of something it's impossible to say which is the original and which is the copy. To make matters worse, file dates and other metadata are easy to manipulate. If you share something you've created, someone could "backdate" it so that it looks like they had it a week before you created it. That way they can make it look like YOU copied THEIR content, and that the content actually belongs to them. Beatcan Protect helps solving this problem for you by letting you register content you create, in a way that makes it indisputable who registered it and when. We live in a sharing world, but that does not mean that creators should not have the right to decide how the things they create are used and shared. Beatcan Protect registration helps you protect that right.
BEATCANPROTECT© HAS YOUR BACK
Prove that you are serious about your rights.
Armed with Beatcan Protect registration you can finally prove that you are the creator and thus the owner of any type of digital information. Because you have this proof, would-be infringers better think twice before using your content without your permission. And if someone does use your content without permission, you have stronger proof to get them to pay for it, either in a law suit or in a negotiation.
BEATCANPROTECT© IS SECURE
We don't even have to see your content.
We realize that things that you work on might be sensitive. So why would you want us snooping around in your content? You wouldn't, of course. And you don't have to: to register your ownership of a certain file it doesn't even have to leave your computer. Everything is done locally, within your web browser. That's the same web browser that you use for online banking and for contacts with your healthcare provider. We even use the same kind of transmission security as those guys. What this all means for you is that your content stays safely inside your computer; we only transmit a calculated ID of your file plus – optionally – some encrypted metadata about your content. And we're happy to show you exactly what we transmit so that you can verify it yourself.
BEATCANPROTECT© IS FAST
Small transfers make for great performance.
Since we don't have to transfer your files anywhere to register them in our systems, registering content is blazingly fast. An image is registered in less than a second, a video clip in just a few. Each registration only transfers a couple of kilobytes of metadata over the Internet, so Beatcan Protect is kind to your data plan too.
BEATCANPROTECT© WORKS WHERE YOU WORK
Laptops, cellphones, tablets. Beatcan Protect works everywhere.
Sometimes things just can't wait. That's why we've made sure that Beatcan Protect can follow you wherever you go, and that it's always ready to register and protect the rights of whatever digital content you create, whenever and wherever you create it. All that's needed is an Internet connection and a web browser. Armed with an BeatcanProtect© registration you can secure your files wherever you are!
BeatcanProtect is built with Iperial Technology
WHAT + WHEN + WHO = PROOF
Imagine that you take a picture of a sunset. You proudly upload it to your favorite social media website for all to see. Later you spot your image for sale as a poster by a company that has not asked for your permission to use your image. What do you do?
HERE'S HOW WE HELP YOU PROVE THAT YOU CREATED SOMETHING
The reason for the problem outlined above is that digital copies are identical to the original. There is no degradation, like when you photocopy something or scan and print a copy. A digital copy is indistinguishable from the original, because every byte is an exact copy of the original.
This is usually a good thing, but in the example above it makes it very hard to prove who has the original and who has a copy. How would you prove your case if the poster company claimed that THEIR file was the original, and that yours is a copy? This is where Beatcan Protect comes in! Beatcan Protect lets you register your content before it's published anywhere, and it provides you with a tamper-evident proof of that registration. In short, it lets you prove that YOU had the original file, because once you've registered it with us, no one else can register the same content and get an earlier registration date.
HOW IT WORKS: FIRST WE CREATE A CONTENT ID.
Beatcan Protect uses so called cryptographic hash digests to register a unique identification string that can only ever be generated by one specific piece of content. In the example above, any other picture of any other sunset would result in a completely different identification string.
That means that you can use this identification string to prove exactly which content you have registered. This is the "what" part of your registration. We're off to a good start, but so far we only have a partial proof.
...THEN WE CREATE A WHAT-WHEN-WHO ID...
Your unique Content ID (just the ID, not the content itself) is sent to our system together with a personal signature that you create. The signature can be anything that identifies you as the creator of the content. Your name and the name of the city and country where you live, your company name or your website or blog address are examples of usable signatures. The signature will be the "who" part of the registration, so you'll want to use something that is clearly more likely to be used by you than by anyone else. Using your name is good, using the text "qwerty" is not, because you would have a hard time proving to anyone that no one else would be likely to use that text as their signature. The signature is not validated because there is no need for that. It exists to let you prove that whoever signed the registration used that exact signature, and the value of a good signature lies in the fact that it would be implausible for someone else to use that signature. Our system then adds a third piece of data, the "when" part of the registration, that is set to the date and time when your registration was received by our servers. A second cryptographic hash digest is then calculated for the combination of the "what", "when" and "who" parts. The is the Registration ID, and it can only be calculated using the combination of the exact Content ID that we just calculated, the exact signature that you selected and the exact timestamp that was assigned to your registration by our system.
...AND FINALLY WE PUBLISH THE HASHES
Your Content ID is then published by our system, together with the new Registration ID, your signature and the timestamp. And here's the clever part: All you need to calculate the Content ID is your file, and all you need to calculate the Registration ID is the Content ID, the signature and the timestamp. That means that the Registration ID can be used to prove that a certain file (with your unique Content ID) was registered at the specific point in time that the timestamp indicates, and that it was signed using your signature. Publishing these IDs is safe, because it's impossible to reverse them to get back to your content. Hashes are not encrypted versions of the content, so it's simply not possible to learn anything about the content by analyzing its cryptographic hash.
The publication serves two purposes: first it lets others "test" a file or a document that you've sent to them, so that they can see that it is indeed registered, and to see when that happened. Secondly, it proves that the timestamp used to calculate the Registration ID is correct. As soon as a hash is published it is "known", and it will be picked up by search engines and other content aggregators. If you register a file on June 1 it will be published on June 1. No one else will be able to register that content at an earlier time. Now we have proved that 1: a certain file was registered, 2: it was signed with a specific signature, and 3: the registration happened at a certain point in time. We're almost done. Now we just have to make sure that nobody can change a registration once it has been created, or rather make sure that if someone DOES change a registration it won't go un-noticed.
To achieve that we regularly publish lists of every ID that has been registered. We can, for example, every hour publish a list of all IDs that were registered during the previous hour. The list is sorted on registration time, so each registration has a known position in the list. The list is saved in a place where anyone who is interested can download it, and we also create yet another cryptographic hash digest of the content of the list itself. This digest is also published.
Creating and publishing these lists and their hash digests creates a "logical lock", ensuring that nothing can be changed in a way that would be undetectable. If a registration in the database is changed, the hash digest of that registration would also change. And if the hash digest is changed it would no longer be found where it ought to be in the published list for that period. If someone tries to hide this by also changing the published list, the hash digest of that list would also change and no longer match the previously published hash.
This "looping back" of calculated and verifiable cryptographic hash digests make each registration lock itself, and through the published lists all registrations help lock each other. Since everything that is needed to validate a registration hash digest is built into the registration itself, you don't have to trust anyone for the system to work. The security is in the principles rather than in the system, so we don't even have to remain in business for your registrations to keep being verifiable. Anything that you register in Beatcan Protect will remain registered to the end of time, as long as you make sure to keep a copy of the content that you registered and as long as any copies of the published lists and their hashes exist. For an in-depth discussion of cryptographic hashes and how they work, please see this wikipedia article.