End-to-end encryption and full GDPR compliance keeps your communication secure and private. Only banks and their customers can have access to messages.

End-to-end encryption support for maximum security

If privacy and confidentiality is critical for your communication eg. payment OTP, medical report,.. Catapush solution supports end-to-end encryption.

End-to-end encryption is when not even us as a solution provider can view the messages you send on through our servers, i.e., only the end users you are communicating with can access the message. Nobody in between, neither the government nor us or any other third party can access it.

Here is how end-to-end encryption works:

the communication between Catapush AWS cloud servers and the enterprise end user mobile device / app regarding the message content delivery, is encrypted using XMPP with TLS 256 bits
since the banks control the two end points i.e. the CRM upstream where the content message is created and the mobile app downstream where the content message is delivered and rendered to the end user, you can encrypt the content of the communication upstream and decipher it downstream.

So your message content would be transmitted encrypted over our encrypted channel.

Also consider that Catapush keeps the encrypt messages stored on in its back end queues only during the delivery process. Afterward all messages are deleted from Catapush servers.

In so doing you can benefit of greater security even compared with SMS communication where content cannot be transmitted encrypted.

Full GDPR compliance for maximum privacy

Full compliance with GDPR confirmed by legal opinion from a leading independent law firm (Push Native does not guarantee same level of compliance and expose enterprises to risks)

End-to-end encryption keeps your communication secure. Only you can have access to your messages.