Absolutely! Pelican uses AES 128-bit encryption standards.
Pelican uses end-to-end encryption from the cloud server to the end Pelican device.
Pelican uses a combination of Private/Public Key exchanges.
Although Pelican has no access to nor stores any critical data, by using a combination of Public/Private key exchanges, the only devices that can communicate with Pelican devices and Pelican cloud serves are Pelican products.
What does this mean?
The encrypted data sent over the Internet is secured through multi-level Digital Signature Algorithms (DSA), which means at no time during the data communication process is any information at risk of being compromised.
Pelican only allows HTTPS connections only.
The Outbound connection between the Pelican gateway and its associated cloud server is always an HTTPS connection. This stands for Hypertext Transfer Protocol Secure. The important part is “Secure” because the HTTPS connection uses the Secure Socket Layer (SSL)/Transport Layer Security (TLS) protocol, which is basically a private point-to-point connection between two devices over the Internet.
Simply, an HTTPS connection makes it so no external devices are able to track the end-to-end connection points across the Internet, because they are secured using Public Key transfer.