Chirp acts as a transport layer and is capable of carrying any type of data, including encrypted payloads. This is comparable to Wi-Fi, which is not encrypted natively, but can straightforwardly be used to carry secure HTTP web connections.
For secure interactions, we recommend using Chirp to transmit information encrypted with industry-standard AES-256 or RSA cryptography. Please get in touch to arrange a demo.
When using Chirp for access control or authentication, we recommend using one-time or time-limited keys which are discarded after use (or after an expiry period). This protects against "replay" attacks, in which an attacker records a Chirp to play back later.
An example of a Chirp with TOTP (Time-based One Time Passwords) can be seen here.