Genesys Tempo for Android security

No, Tempo does not store any PII information on the agent’s personal mobile phone.

Are there any protocols used to control user authentication?

Yes, Tempo uses the following protocols to control user authentication:

• HTTP basic authentication, which is a form-based login authentication.
• RACF, which is a client certificate authentication.
• Federated authentication, which is an Active Directory authentication.

Does Tempo for Android use a user authorization process?

Yes, Tempo for Android uses platform-specific APIs to securely store the user’s authorization and refresh tokens. Tempo’s login credentials or the SSO is shared with the user along with the Genesys Cloud platform’s settings.

Which are the authentication providers that Tempo for Android supports?

Tempo supports the basic authentication and OAuth integration. Any SSO support for Tempo has to come from the platform and authorization libraries. Tempo uses a web-based login screen, which the agents can use to access Tempo.

Does Genesys Cloud use a different authentication path for Tempo compared with the web or desktop apps?

No. Genesys Cloud uses a single authentication infrastructure across all clients, which includes the web app, desktop app, and mobile applications like Tempo. All of them authenticate against the same platform using OAuth tokens, and all access the same backend APIs.

This means that features like IP allowlisting, SSO, and MFA policies are applied consistently, regardless of how the user logs in. If IP restrictions are in place and a mobile device’s IP is not allowlisted, the user will not be able to access Genesys Cloud through Tempo either.

Does Tempo for Android send data to a third-party site for processing?

No, Tempo for Android does not send any data to third-party sites.

How does Genesys Tempo use Firebase crashlytics?

Genesys Tempo uses the automated crash reporting feature to collect generic data and a stacktrace. It uses non-fatal logging to log certain internal errors that are not expected. When we use non-fatal logging, we only include a stacktrace, which is an message. PII is not included in the report.

Does Tempo mark its session cookies with the secure attribute so they can only be passed when secured with transport layer security (TLS)?

Yes, Tempo uses TLS 1.2.

What specific data elements does Tempo access, process, transmit, or store, if any?

Tempo stores authentication data in the appropriately secure OS mechanism, while user preferences are stored using the appropriate OS preference API.

Does Tempo for Android access an internet site to provide functionality?

No, Tempo does not access any internet sites to provide functionality.

Does Tempo for Android prevent an unmanaged application from accessing the data?

Yes, Tempo prevents any unmanaged applications from accessing the data.

Does Tempo for Android has the capacity of providing containerization of data stored, processed, or transmitted by it?

No, the data in the mobile application is based on the web APIs.

Does Tempo for Android cache the data on the phone?

No, personal information is stored locally; only app-related settings are stored using the operating system’s secure preference APIs, such as preferences like enabling notifications. Authentication and refresh tokens are stored securely using platform-specific APIs, including the user ID.