Silent Authentication Registration Requirements by Country

In most available countries, all registration requirements are collected by the Network Registry. Certain countries have additional legal and privacy requirements, including particular consent or disclosure wording, that must be fulfilled before using Silent Authentication. This guide outlines the specifics for:

• Germany
• France
• United States

After submitting a request for access to Silent Authentication, through the Network Registry, additional information required should be sent to your Vonage Account Manager or nw_api_reg@vonage.com.

Using Silent Authentication in Germany

Before approving an access request, German networks require:

• Screenshots of the end-user journey in the mobile application wherever Silent Authentication is used. For example, if using Silent Authentication for user registration and login, provide screenshots for both flows.
  Additionally, when using Silent Authentication in Germany, you must use specific wording in your application to gain the user's consent before any IP matching/processing:

For a visual reference, see Mobile Application Screenshot Examples.

• Data processing language: The Privacy Policy contained in the URL already provided must explain how and why you process phone numbers, and that they may be verified with the user's mobile network.

Using Silent Authentication in France

Before approving an access request, French networks require:

• Screenshots of the end-user journey in the mobile application wherever Silent Authentication is used. For example, if using Silent Authentication for user registration and login, provide screenshots for both flows.
• Data processing language: The Privacy Policy contained in the URL already provided must explain how and why you process phone numbers, and that they may be verified with the user's mobile network.

For a visual reference, see Mobile Application Screenshot Examples.

Using Silent Authentication in the United States

Before approving an access request, US networks require:

• End user consent language: Specific pre-approved consent language to be included in customers' Privacy Policy, Terms & Conditions, or in the application itself. If using Privacy Policy or Terms & Conditions, end-users should also be shown a link to them in the application, ideally at the beginning of the journey where Silent Authentication is used:

Mobile Application Screenshot Examples

To help you interpret these requirements, the following examples show a “zero‑click” Silent Authentication experience and how consent and disclosures can be presented in the user journey.