Technology info

Are you interested in what Raketu/RakEm inventor has to say? Please read.

RakEM: What is secure private and encrypted?

Secure and Private

In order to have a secure and private service, Raketu believes the service must be:
1) Secured: RakEM uses secure login, access, data
2) Encrypted: RakEM is using the highest levels of industry encryption available, and utilizes our self-mutating encryption keys
3) Device-to-device direct: the communications and data must flow directly from device to device (no servers, no relays). RakEM uses device-to-device direct communications.
4) No data mining: the data belongs to the user, and it should not be mined for monetary gain. By using our device-to-device direct technology, our servers do not even have the data to mine - the data is not on our servers- the data mining is impossible.
5) Users choose when to remove content: RakEM allows our users to delete history files that also delete the history on the associated users device. RakEM has the features users asked for:
In order to have a complete solution for users, they requested and we provide:
1) Easy to use: like an SMS-text program
2) Messaging
3) Picture/File sharing
4) Voice Calls and voice messages
5) Video Calls and video messages
6) User controlled location sharing
7) User controlled content and when it is deleted


In RakEM, What is encrypted?
1) Messaging
2) Picture/File sharing
3) Voice and Video calling
4) Location sharing

Encryption level:

Depending on devices and network conditions, RakEM uses an encryption key length of up to 4096 bit, using the maximum possible for a given task and conditions. For example, an encrypted voice call from an Android to an iPhone will use a 2048 bit encryption key. RakEM’s device-to-device direct communications use our patent pending self-mutating encryption algorithm. RakEM has developed a separate key generation and key exchange system. The primary key, which changes seldom, is mathematically coupled to a session key, which is generated at a user based event (for example logging in), to create a third, exchange key. Prior to each content being encrypted, a transaction key is created, and it is the mathematical coupling of these keys that creates a resulting key that is used to encrypt the content. This encrypted content is then sent, directly from device to device, where the content can be decrypted with the appropriate keys. Why do this? By doing this, each transaction will contain different encrypted data. For example: user A sends user B the following text message 3 times: Hi

encrypted1 = 7d087efcceff332k3diosuehe5422343 encrypted2 = 7d087efcceff332k3diosuehe5422343 encrypted3 = 7d087efcceff332k3diosuehe5422343

encrypted1 = 5d2eae5dab3308892f1e368820d4b56f63e922b66c8b6adbf7ac9d4928d98a92edf10d1cdf73cb24ca263a880976f89904b81e12b7d7368bb12dae04d688890d encrypted2 = 06aa33422e275b4e50effbf0a0d00e310f1cd5911e1d0634ecf7b9d3bd782aed8875f37919cff7d5dd523b9914bd1bdfde3109cd91ccba9d6ca0701219267200 encrypted3 = 60978ca62d2edfc41374ece87ad1122f1546ca47ca6d1eeebfad67fc81a04e59f25b15c6f33644f0b49314f2bc86e76694579ad5705b87ce5748d6c208dcf81a In the example, with RakEM, each time the text “Hi” is sent, it is encrypted differently – which makes it that much more difficult to attempt to decipher by unwanted parties.


Device-to-Device Direct

While encryption is critical, it is not the whole story – how the content is transported also plays a significant role. RakEM uses device to device DIRECT communications. What this means is that content goes from one device to another device directly, without the use of intermediate or central servers. This is important and unlike most other messengers that have the device send the content to their servers, where it is stored and at some later time sent to the recipients device. When the content is stored on their servers it is vulnerable to be data mined by the messaging company themselves, or a partner of theirs or to be accessed from a central point by a hacker or third party. In addition, since all communications in their model go to their central server, it is far easier for a hacker or unwanted third party to “spy” for traffic at or near this origin. In contrast, since RakEM uses direct device to device transmission, it is incredibly difficult for any hacker or unwanted third party to find the traffic in the first place in order to “spy” on it – and even if they did “spy” on it, our encryption level and algorithms make it next to impossible to decipher the content.

Encrypted local files

RakEM also encrypts local files – so even your text history is encrypted locally on your device.

Reciprocal Deletion of Text History

RakEM also provides users the ability to reciprocally delete all or selected messages from their chat history that also deletes those messages from the recipients device. In other words, you can “take back” your texts.

Location Sharing

While many people don’t like the idea of location sharing, many do. RakEM is working on some new features around the concept of what we call “who’s near” – more to come on that later. Regardless of whether you like the idea of location sharing or not, RakEM comes with location sharing turned OFF by default. Each user must manually turn on periodic location sharing in the settings. Once it is turned on, only your approved friends can see your location. You can send your location update to a specific approved friend directly without turning on periodic location sharing – either from the contact list more, or when you are in a text chat with them. You are in total control of location sharing.

Open Source?

RakEM is not currently open source. We at Raketu are believers and advocates of open source, and we regularly contribute to several. We are considering open sourcing RakEM at a future date when we feel it is appropriate to do so.

Why RakEM is more secure than WhatsApp and Snapchat?

RakEM does not use servers for delivery of messages between users.
RakEM messages go directly device-to-device, no server touchdowns. Even though Snapchat and WhatsApp say they do not read messages off their servers, the shear fact that they are on their servers leads to a potential for 'hackers' or 'snoopers' to get the messages. In addition, some apps say they use encryption and store it on their servers. Problem is, with the type of encryption they are using, it must be able to be decrypted so if the messages are obtained by those other than the intended recipients (internal, external back doors or hackers), they can also be decrypted. RakEM uses direct device-to-device which eliminates this issue.

RakEM uses end-to-end encryption over device-to-device direct transmission.
This means that before a message leaves the device, it is encrypted, then sent directly to the recipients device, received, decrypted and displayed. When other apps say encrypted and stored on servers, it is unclear as to whether the messages are encrypted on the device or not, or encapsulated within encryption in transmission from device to server, whether the content is encrypted itself, and if it is stored in their database encrypted or not. Regardless, RakEM encrypts the messages at source, uses no servers, and decrypts at destination.

RakEM does not allow third party add-ins.
According to Snapchat, this was the main cause of the collection of the images that were stored out on non-Snapchat servers. RakEM does not allow third party add-ins at all.

Snapchat content 'disappears' within a set timeframe (10 seconds or so).
With RakEM, the rich media disappears when the chat session is terminated (ie. when the user navigates off the chat session). Note that with RakEM, once the rich media is displayed, it is in memory only, not even stored locally. With RakEM the textual content is stored locally, and users can choose to delete their chat session when they want to and it will automatically delete that chat session from their friends device also.

Many people report that you can just take a screen capture of the Snapchat screen before the pictures disappear, and you have circumvented the entire Snapchat disappearing picture feature.
For RakEM, we are developing a new feature that either prevents screen capture all together, or when a screen capture is taken of RakEM, the capture is a black screen, no image of RakEM is taken. We have this working in our labs and will be releasing this feature in an upcoming release.

We believe RakEM is the most secure messaging app available, and we have many unique features, like the who is near visually showing your friends on a grid based on their location - NOTE that you can only use this feature if your friends turn on location sharing which is turned OFF by default.


Download Your RakEM now!

Download on Google Play! Download on Appstore!