Circle of Trust™ Implementation Model

SecureSMS Circle of Trust is used for mobile to mobile communication with others within a trusted group. CellTrust SecureSMS Gateway, exclusively hosted at your location, manages and routes the traffic over your organisation’s dedicated short code hosted with any aggregator or carrier.

Application Programming Interface (API) or web tools are used to send SecureSMS or standard SMS from your network to the Circle of Trust or any other phone. CellTrust SecureSMS gateway provides reporting and compliancy for all secure and standard SMS traffic and can be set to allow or prevent handset communication with phones outside the Circle of Trust.

This model is often used by governments, military and businesses wishing to exchange highly sensitive and confidential information.

Mobile to Mobile Implementation Model

Mobile users with SecureSMS on their phone can securely communicate with any other phone with SecureSMS throughout the world. The SecureSMS cross platform Micro Client supports most industry standard installation methods which generally take only a few minutes. Messages are composed using the SecureSMS full feature editor and the destination is identified via phone number, short code number, keyword or recipient name as defined in a secure phone book. Users can set a default behaviour when sending messages to phones that are not capable of receiving SecureSMS messages or set the behaviour for each message individually.

This model is typically used by mobile users who wish to take advantage of secure communication without the need for gateway services.

Application to Mobile Implementation Model

A set of Application Programming Interface (API) and web tools are used for communicating SecureSMS messages between your application and handsets. Typically used to send personal and confidential information from your network to your customers or employees, both dedicated short code and shared short code models are supported. A hosted CellTrust SecureSMS Gateway provides reporting and compliancy for all messages. You may determine a phone’s capability of receiving SecureSMS messages prior to sending the message. You may also define the gateway’s default behaviour when sending messages to phones not capable of receiving SecureSMS messages or set the behaviour for each message individually.

This model is often used by organisations providing personal and confidential information to their customers and other stakeholders.