Privacy Notice

Our app is a communication service that requires access to your microphone and camera for you to engage with your contacts. This access is solely for capturing audio and video during calls or when recording an audio message and can only be initiated by you.

Mobile operating systems like iOS/iPadOS and Android limit app activity to conserve battery life. When a message or call arrives, the backend system sends a notification prompting your device to activate the app. Only after the app activates does it connect to the backend to ascertain the reason for the notification and to perform the necessary action (such as displaying an incoming call or alerting you to new messages).

The third-party cloud services provided by Apple for iOS/iPadOS devices and by Google for Android devices, which send these push notifications, do not receive any details about the cause of the app's activation (such as the content of the incoming call or message).

When inviting other users or when making a phone call through your organization’s fixed telephone infrastructure (PBX), you may import contacts from your device's address book into the application. Our app does not automatically import or scan your private contacts, nor does it share the contacts from within the app with your device's address book.

If you use the app to place an external phone call via your organization's PBX, the recipient's phone number and the call content may be recorded in accordance with your organization's privacy and compliance policies.

When exporting files from or importing files to the app, the app needs permission to read and write to the filesystem. File imports can only be initiated by you. Within the app, files are visible only on your device, and remote access to these files is not possible.

The app enables you to share your current position or your live location for a selected duration. To facilitate this, the app requires access to your device's location data. This information is shared solely with the individual or group you select, and cannot be accessed remotely.

For displaying location data, we utilize Google Maps on Android & Desktop and Apple Maps on iOS/iPadOS, ensuring that no identifying personal or device information is shared.

During a video call or conference on the app, you have the ability to share your screen with other participants. Recipients will see all content that you present on your screen during the sharing session. Recall that screen sharing is initiated at your discretion, and you retain full control of your device throughout.

To use the app, a user profile is automatically created by the system. If your organization’s directory does not already provide user profile information to the backend, you have the option to enhance your username with additional details that facilitate identification and communication with other users.

Your display name is how you will appear in other users' contact lists and conversations. It also enables the system and its administrators to identify you. Usernames are not disclosed to third parties and are not directly accessible by other users within the system.

This optional information remains hidden from other users. It enables the system and the helpdesk to send messages to your inbox, such as download links or activation codes. Within the app, under Controls-Profile, you may alter your email address, opting for a fictitious one if you prefer not to disclose your actual information. Be aware that changing this detail could affect the recovery of a blocked device or the addition of new devices.

This optional information is concealed from other users. It permits the system and helpdesk to dispatch messages to your mobile device, including download links or activation codes. To alter this information, reach out to the helpdesk via the email displayed under "Info" in the "Controls" section. If you prefer to keep your real information private, you may opt for a fictitious mobile phone number. However, this action could affect the recovery of a blocked device or the registration of additional devices.

Note: When utilizing the Secure SMS feature, which relies on a mobile operator's SMS gateway to send encrypted messages, your mobile device's phone number must be registered in the system for full functionality. In such instances, senders of a secure SMS will see your mobile phone number.

This optional information is visible only to you and your contacts. You may change or remove your profile picture under the "Controls" section. While visible on backend servers, your profile picture is accessible solely to system administrators. It is not accessible in the management console to the community managers.

Optional details such as department and title, modifiable solely by your community manager or as allocated from an enterprise directory, are displayed exclusively to you and your contacts.

The profile information of a circle member is visible to all other members within that circle. The community managers have access to the list of your circles and their respective members. Private contacts remain invisible to the community managers.

The circle name is visible to all members of the circle. Your community managers can view the names of circles. Any member of the circle can change the circle name, depending on the permissions given by the community managers from the management console.

The circle picture is visible to all members of the circle. Any member of the circle can change the circle picture depending on the permissions given to that particular user.

The posts can be published (depending on the rights defined by the community managers) and received by any of the circle members.

Messages between the sender and one or multiple recipients are end-to-end encrypted, ensuring that only the receiving devices can decrypt and display the message. If you have multiple devices, a copy of any message you send is also sent to your other devices.

During transit, network elements in the internet and the backend servers may temporarily retain a copy of the information until confirmation of reception by the receiving element. This transient information is encrypted, and the transporting element does not have access to the key material, which is solely present on the sender’s and recipient’s devices.

The system guarantees the integrity and privacy of the conversation, with no copies of the conversation stored except on the sender’s and recipient’s devices.

Additionally, mobile devices can send secure SMS in addition to messages. Secure SMS is encrypted so that only the application on the recipient’s device with the correct SIM card can decrypt the message. The mobile network responsible for transporting and delivering the message only sees the encrypted content and does not have access to the decryption key, which is solely present on the recipient’s device.

Both the sender’s and recipient’s mobile phone numbers are shared with the mobile operator and among the participants of the conversation.

The chat room picture is visible solely to members of the chat room. Admins of the chat room have the authority to change the chat room picture.

Phone and video calls are conducted using encrypted transport protocols, ensuring security during transmission. Only the intended participants of the conversation can join the call. The system guarantees the integrity and privacy of the call, with no electronic records or recordings of the call being retained.

External phone calls utilize secure transport to the backend servers, from where the call is routed to your organization's PBX. This allows you to make secure calls worldwide to any of your organization’s extensions or to the public telephone network.

While the phone number you call is visible to the organization’s PBX, your identity may be masked. The call may also be recorded and archived in accordance with your organization’s PBX data retention policies.

If the call is to a public network endpoint outside of your organization, the recipient’s phone number and either your organization’s central phone number or your public line phone number will be visible to the public telecom operators. Your call may also be subject to legal interception.

When sending media and files to peers, you can retain control by revoking the recipient’s ability to export the content outside of the secured container or forward it to other recipients. Within the secure container, you can recall the message, effectively removing the related content from the recipient’s devices.

Files and media are transmitted using end-to-end encryption, ensuring that only the recipient’s devices can successfully access the content.

During transit, network elements in the internet and the backend may temporarily store a copy of the information until confirmation of reception by the receiving element. This transient information is encrypted, and the transporting element does not have access to the key material, which is solely present on the senders' and recipients' devices.

The system maintains the integrity and privacy of the content, with no copies being made other than on the senders' and recipients' devices.

The backend requires knowledge of the platform on which you have installed your app(s). This information is utilized to send push notifications to the device if necessary or to determine the available functions on the device.

The backend receives an incoming connection from your device, utilizing various pieces of information:

• IP Address: Used by the system to reply to the connection request and stored temporarily in a log file accessible only to system administrators for a short duration (8 days). The IP address may indicate the region from which the connection is made.
• Bandwidth: Utilized during audio or video calls to determine the available bandwidth between your device and the backend, ensuring optimal audio and video experience. This information is not stored and is only used within the system.

Your device collects logs of its activities and stores this information locally. The logfile contains only relevant data for resolving issues when using the app. It does not include device hardware identifying information, personal information, or files/messages shared with other members. While it does reveal app usage details like making calls or sending/receiving messages, the logfile is anonymized and does not disclose the real identities of your peers.

Only you can upload the device logs to the backend system, where they will be accessible to the supplier’s Helpdesk. Within the supplier’s support cycle, this information is retained for the duration of the support ticket.

The system requires information on the connection status of your devices to determine whether to send push notifications. The online status is represented by a green dot on the profile picture and is visible to your contacts. Additionally, your contacts can see the last time any of your devices was online. This information is also accessible to your community managers.

The security code serves to unlock the application on your device. It is never saved in its original form; instead, only a hash—a mathematical representation that prevents retrieval of the original code—is stored. This hash resides solely on the device, ensuring that only individuals with device access and knowledge of the unlock secret can successfully access the app.

If you opt to use biometrics for app unlocking, the app does not access the biometric data used by your device for authentication.

Your device-specific private key is utilized to identify and authenticate the device to the backend. Each device possesses its own private key, stored solely on that specific device. If you create a backup set (currently available only on mobile devices), the private key is also included in the encrypted backup set, allowing restoration on a new device.

All this information is solely stored on your devices within local encrypted databases. End-to-End encryption technology replicates this data between devices without a central backend archive. Neither the system nor its administrators have access to any of this data.

Your data is stored locally on your device within an encrypted database. The encryption key is securely stored in the device keychain, accessible only to the application to ensure exclusive access to its database.

On iOS/iPadOS, automatic application backups are stored in your iCloud storage linked to your Apple Account, unless backup to iCloud is disallowed by you or your organization. On Android, you can create an encrypted copy of your encrypted database and store it on accessible locations like local filesystem or cloud storage providers (recommended). The application backup is encrypted and safeguarded with the Backup Key.

Your backup key, created for application backup, is stored in an encrypted archive in the backend. Access to this key is granted only upon authentication with a password set during backup creation. By separating the backup key from the application backup data, and ensuring neither storage space knows the whereabouts of the other, we ensure that only you, as a valid system user, can restore a backup from a created backup set. System administrators do not have access to the unencrypted backup key or knowledge of the backup data's storage location.

Your profile information is stored in the backend servers, accessible to the community managers.