ICOM

Interpreters Center for care and mediation talks in POUNDS.

Interpreter Center for service and intermediation of conversations in LIBRAS.

- Use of VPN services

The ICOM app is responsible for providing interactivity, engagement and ensuring full communication for our deaf users and we are offering Sponsored Browsing access to the app for certain partners, that is, the user does not have data deducted from their data plan, only during consumption within the sponsoring brand’s service. To do this, we use Datami's Sponsored Browsing service, which requires a VPN connection.

- Why do we use VPN?

To enable this service, it is necessary to use Datami's VPN SDK, which has the function of providing reverse billing to operators. The operator is unable to provide this service because it requires a limited and known range of IPs. When the operator receives the request with the Datami domain, it recognizes it and sends it to the Datami gateway to carry out reverse billing. If the request comes from a third-party service, Datami is unable to encapsulate your domain and guarantee that all requests go through this flow, limiting part of the resources to data sponsorship. In this case, it is necessary to use the VPN to force this request to be counted as reverse billing in GW Datami and even users without data can consume any possible content that the application in question tries to access.

From the operators' point of view, Datami additionally provides the ability to offer Sponsored Browsing by charging only for what is used, while IP or domain release models do not have this type of control, nor do they guarantee that different services are sponsored in the same context . In this case, the only point in common between these requests for different endpoints is the fact that they come from the same App – the application is the context to be sponsored, not the requested domains. With Datami's VPN SDK, sponsoring absolutely all of the app's content becomes possible, since this private connection will guarantee that no requests will be lost and the authentication/authorization services recognize the App and consolidate all its use into a single campaign.