Cloud4Wi FAQs

Cloud4Wi MyApps is a tool that allows you to create personalized and branded access journeys for your customers. Each one of our clients is unique, has different strategies, goals, and tactics, so we build a tool to create easily any type of experience in a short time and make it personal.

With MyApps you can adapt and deploy your existing services and experience (for example a loyalty program onboarding, or a train ticket verification) into the WiFi Access Journey. Or, you can develop new ideas from scratch, designed and optimized for the WiFi digital touchpoint.

When a customer connects to WiFi, at the right time, Cloud4Wi redirects the user to your web application including all the context info that you might need to create a personal experience. The web SDK, also allows you to adapt your application to let the user go online once he has consumed your content.

Using MyApps you can:

Create content applications that can show custom personalized web content to your guest during the onboarding process to the Guest WiFi (called the Access Journey).

Link your custom and personalized content from a menu of the Splash Page (for example the menu of a restaurant)

Create a setting page published in the Cloud4wi Dashboard, that can be used either to configure a content application (for example updating the menu from the example above) or to publish back-end oriented content (for example a custom reporting page).

Here some examples of what our customers have built using MyApps:

Hyper localized and personalized advertising page

Promote the subscription to your loyalty program

Integrate an AdServer

Show promotions that are different for each location

Verify user credentials or membership before granting him access

Create a custom gamified experience to gather customer interests

Invite the user to chat with your support team on a bot or chat

This article includes the following contents:

Apps for the Splash Page

Apps for the Cloud4Wi Dashboard

Getting Started

Creating a MyApp Account

Creating an Application

Publishing the Application

Installing the Application

Apps for the Splash Page

The main purpose of MyApps is to allow you to bring your own content into the experience of a user connecting to the Guest WiFi, and make it highly relevant.

There are two main methods to publish the content in this experience, via the Access Journey and via the App Bar.

TheAccess Journeyis a tool that allows the orchestration of the steps that a user takes to go online. The most important page of the Journey is the Welcome Portal Home Page, which usually contains some content as well as the login options (for example registration form or social login options). This page is managed from the Cloud4Wi Dashboard. The Access Journey tool allows you to publish one or more dedicated web pages before or after the Welcome Portal, forcing the user to go through a series of pages before getting online.

The Access Journey, as managed from the Cloud4Wi Dashboard, includes the following steps:

Connect: this step is the first one in the journey and shows a page before the Home Page of the Welcome Portal. In this step, the user is still anonymous, so MyApps offers only location information (where the user is connecting from).

This is a video that shows a journey that prompts a video advertising page as soon as the user connect, using the Connect step of the access Journey.

Sign-Up: this step happens when a new user registers for the first time. It can be seen as the first login. Technically in this step the user is already online and MyApps knows everything about the user.

Login: this step happens every time the user logs in. In this stage the user is already online.

This is a short video that shows an example of a Survey App published in the Login Attempt.

Login attempt: this step has been introduced between the user login attempt that the actual authorization to go online. Technically the user has been authenticated (creadial are ok) but has not been authorized on the network yet.

This step will force the user to interact with this page in order to continue online (for example showing an advertisement for 10 seconds), while in the login and sign-up steps the user is technically online and can leave the journey at any time.

This step has been introduced also to face a particular behaviour that happens in the latest Andorid phone. When an Android phone connects to an hostpot, it launches a Sign in webview that open the Welcome Portal. As soon as Andorid recognize that the user can reach internet through hotpsot, it closes automatically the sign in with.. popup, and the user is dropped from the journey, making impossible to show other contents to the users.

This is a short video that shows an example of a standard journey on a phone where we see the "login" popup closing as soon as the user goes online, demonstrating the downfalls of the sign-up and login steps.

Logout: this step happens when the user clicks on the Logout button on the Welcome Portal Success Page. Since most of the times the user leaves the Access Journey to browse the internet, the user will rarely click the logout button, except for specific use cases (for example in the case of paid internet access when the user can stop the session and use the remaining time in another session).

TheApp Baris a collection of links that can be published on the Home of the Splash Page and the Success Page (the one the user lands after a successful login), to let the user exposer contents.

The figure below summarizes all the methods and steps where an app can be launched.

GitHub link

How it works

You can develop and host your app on your own servers, in any programming language.

When your app is invoked, either from the Splash Page, Access Journey, or Admin Panel, Cloud4Wi will make a web call to your app's endpoint, appending a few parameters to the request, including asession key.

Your app can use the session key and use it to retrieve Context data from the Context API about who and where the app was launched from.

Your app can use this information to craft personalized and localized content and reply to the initial web request with that content.

The figure below shows the application flow when launching your app from the Access Journey.

The API to retrieve the context information for the application launch is called the Context API. The document explains in detail all the parameters sent in the original request to the Application Server, the context API and the parameters returned by the API call.

Please note that you can also leverage the Cloud4WiAPIsto retrieve further data from a Cloud4Wi Account (for example the logs of the connections of a User or his full profile).

Take care of the Walled Garden

Note that when your app is launched, the content is served directly from the Application Server and the browser is redirected on the domain where the app is hosted.

When the application is launched from the Welcome Portal in a stage when the user is not online yet, you need to make sure that your domain/hostname can be reached by the user by whitelisting your domain/hostname in the walled garden of the Access Point.

Each access point vendor has different capabilities, some of them can whitelist an entire domain with a wildcard, other supports only hostnames, and others support only a list of IP addresses (this last case, in particular, makes things much more difficult to handle if your hosting is in the cloud).

Handle the Journey navigation

When the App is published in the Welcome Portal, either via Access Journey or with a link in the App Bar, we need to control the way the user interacts with the content pages and, more importantly, with the journey.

For example, if the user opens an App by clicking a link in the App Bar, once he reaches the App content, he needs a method to return to the previous page.

When publishing the App in the interactive Journey, we need to embed in the app a method to let the user move forward to the next step.

MyApps offers two methods to handle this problem.

The first one is the possibility to publish a Navigation Bar on top of the page, which includes some icons to move forward or go back (depending on how the app is launched).

The second one is a javascript SDK that provides some methods that can be used by the app, to move forward to the next step or go back to the previous one or to the home. This allows the developer to create his own custom experience in the app.

MyApps Web SDK details

Apps for Cloud4Wi Dashboard

The Apps created with MyApps are published in the Cloud4Wi Dashboard and they offer the option to show in the Admin Panel configuration page when they are opened.

This can be used, for example, to create a configuration page of an App but also to create pure back-end applications meant to be displayed on the Admin Panel, such as a reporting dashboard.

The apps shows up in the Apps page under the category configured when initializing the app and also under the Dev Suite group.

The diagram below shows the flow of launching the app from the Cloud4Wi Dashboard.

Here, an example of an app (Video Advertising) built with MyApps, that offers a configuration page that can be opened directly from the Cloud4Wi Dashboard.

Since Cloud4Wi is a cloud based multi-tenant platform, an App can be installed in different Cloud4Wi Accounts (Tenants). It is up to the developer to create the logic that allows an app to have different settings on different accounts.

When an Admin opens the app from the Admin Panel, Cloud4Wi calls the application Server with a session key that allows the retrieval of the Account data (Company ID, Venue ID) so that the app can save different settings per each Account.

Note that all the settings and saved data are the responsibility of the app developer and hosted in the developer's Application Server.

Getting Started

In order to develop and deploy an App on Cloud4Wi using MyApps, you will need to:

Get access to the Developer Portal and initialize your App

Publish the App in the Cloud4Wi Account via the Cloud4Wi Dashboard

Publish the App to the Access Journey or the App Bar

Creating a MyApp Account

If "MyApps" is active for your Organization instance, then you can create a Developer account through the Cloud4Wi Dashboard.

To do this, click on the quick access toolbar on the left Manage Settings Dev Portal. From here you can create, edit or make other actions on developer accounts.

To create a new Developer account, click on the Add button at the top right-hand corner of the page.

To add a new Developer account, you have to provide the following information:

First name

Last name

Email

Then click on Save.

Finally, your Developer account for MyApps is ready. Username and password will be sent to the email address provided. Now you can make further actions by clicking on the username.

The available actions are:

Lock / Unlock: you can disable on enable the account

Edit: you can edit First name, Last name, and Email fields

Reset password: you can set a new password and send it to the provided email address

Creating an Application

The developer portal is published at myapps.cloud4wi.com

Your Cloud4Wi Account Administrator can activate an account for you directly from the Admin Panel. This Help Article explains how to add a Developer Account.

Once logged in, you can create a new application by clicking onCREATE NEW APP.

You will then have to provide information for your app:

General Information

App name: The name of the application. This field is what the App will be called in Cloud4Wi.

Category: The category displayed in the Marketplace of the Cloud4Wi Dashboard. Can beMarketing,Analysis,Guest Wi-Fi,Integrations, orOther. The application will be displayed under the category you choose as well as the unselectableDev Suitecategory.

Short description and Full description: These descriptions will be displayed in the Marketplace.

Icon: The icon displayed in the Marketplace and (if publishing to the App Bar) in the Welcome Portal.

App Management

App Visibility: the application is shown in the Marketplace only at Company level (Company level only), or both at Company and Venue level (Company and Venue levels).

Enable pre-authentication mode: You can decide to show the app for guests that havent performed the authentication on the Welcome Portal. Take Note: Because authentication hasnt happened yet, the guest is still within the walled garden, so you have to take care that all the required resources are actually accessible by your guests (by configuring the walled garden of your access points). Any libraries and resources you use must be served from within the walled garden.

App Endpoints

Base URL: the host where all the pages for the app are located.

Access Journey page: the relative URL where the user is redirected during the Access Journey.

Admin Panel settings page: the relative URL to be opened in the Marketplace. From here, the Company or Venue managers are able to configure the application.

App Bar page: the relative URL where the user is redirected when coming from the App Bar.

Once finished, save your application

Publishing the Application

In order to use it, you need to install it on your Cloud4Wi Account. As a first step you need to click the button Publish in the app dashboard page.

Every time you make a change to the App settings in the Developer Portal and click Save, you need to also click Publish to put them into effect, even in applications that have already been published and deployed. Click on Publish to get your App Id. It will be necessary to install the application on your company instance.

Installing the Application

Login in your Cloud4Wi Account. In the Apps page you can install the application by clicking on the Add button, entering the App Id displayed after clicking Publish on the Developer Portal, and then clicking on Import. After that, your app will be in the Marketplace in the Dev Suite tab and in the tab you defined when selecting the category of the application.

Now the application is installed and ready to be used on your Cloud4Wi account. By clicking Open you are able to access and use the Admin Page you linked to as the Admin Page during the creation process.

Demo Applications

Slack

NodeJS backend application that incorporates MyApps, Webhooks, and Slack APIs to show the possibilities of MyApps and Webhooks with Slack.

GitHub link

Video Advertising

PHP backend showing a simple MyApps to display a video advertisement to users during the Access Journey.

A misspelled email is a missed customerand a fake email is a real problem. Cloud4Wi Email Validation add-on intercepts invalid emails during the registration flow andensures that an email address actually exists.

The component is already integrated into the onboarding process and the experience is designed to reduce the impact on the customer experience. By intercepting invalid email in real-time you get multiple benefits:

intercept misspelled email and maximize the probability to collect valid email

avoid the necessity to post-process in batch the email using external tools

With the email validation add-on, you can improve your data quality, reach more contacts and unlock all benefits from a healthy and solid customers database :

Lowers bounce rate under thresholds required by most ESPs.

Identifies and removes spam trap emails from your list.

Remove known abusive addresses that often mark emails as spam.

Removes emails from domains that don't accept mail.

Identifies commonly misspelled email domains.

Protects your IP reputation and increases deliverability.

Improves inbox placement and email campaign performance.

Clean personal data with a classified record.

How is this different from "email verification"?

The email verification feature allows making sure the email provided actually belongs to the customers by sending them a confirmation link to the provided email address. While this mechanism provides more guarantees, it also impacts the overall customer experience and sometimes a simple validation check may be sufficient.

The customer experience

The email validation add-on allows validating in real-time the email provided by the customers during the registration process. If the email is not valid, the user is prompted to a page that invites him to review the email address before proceeding.

Contact us

How it works

The email validation add-on performs multiple checks on the email address, including:

Domain validation We check the ISPs and detect all emails with invalid, inactive, parked domains.

SMTP validationWe check email existence on the real SMTP server resolving the MTA (Mail-Transfer-Agent) to a correct MX Server (with a valid hostname using the IP address) and then execute an SMTP transaction for checking email existence

Hard and soft bounce checkerWith the SMTP validation, we detect the hard bounces - that means the recipient's email address is invalid or no longer in use - versus soft bounces - for example, mailbox full

Syntax errors validator (RFC validation) Syntax error checker detects emails with invalid syntaxaccording to the RFC 822 standards

Interested in this add-on?

Cloud4Wi product suite offers a collection of tools to:

Integrate the data, such as customer's emails, with your own third-party systems

Create custom experiences for the users during the WiFi onboarding

Create new tools published in the Cloud4Wi Dashboard marketplace

The tools include:

REST APIs: access to data (users, network, logs, analytics)

Webhooks: real-time notifications when users sign-up, log-in or simply walk by a store or enter into a zone

MyApps: develop and inject personalized content pages during the WiFi Access Journey; create new tools that leverage the APIs

The Developer Hub ( https://developers.cloud4wi.com/ ) is the main resource to getting started with the development tools.

https://cloud4wi.zendesk.com/hc/en-us/articles/360015691931-Marketing-opt-out-via-REST-APIs

Related resources:

API introduction https://cloud4wi.zendesk.com/hc/en-us/articles/205207615-An-overview-of-the-Cloud4Wi-REST-APIs

Create a Developer Account https://cloud4wi.zendesk.com/hc/en-us/articles/115001016024-How-to-add-a-Developer-account

Marketing Opt-Out APIs

In case you are exporting the user list to an external marketing tool, such as an email marketing tool, and the users opt-out from that marketing tool, you can sync the opt-out status in the Cloud4Wi customer list so that all the native Cloud4Wi marketing applications won't send communications to those individuals anymore.

API End-point:

https://api.cloud4wi.com/v2/marketing/disable/{{customer_id}}?api_version=v2.0&api_key={{api_key}}&api_secret={{api_secret}}

Where:

{{customer_id}} is the encrypted customer id

{{api_key}} is your account api_key

{{api_secret}} is your account api_secret

When you import the users formCloud4Wi to your marketing tool, we suggest keeping also the customer_id field so that in case that user unsubscribes you can use the API to sync this info in yourCloud4Wi account.

Beta program enrollment

Cloud4Wi started the Beta Program and is onboarding new clients that want to test the power of the Passpoint SDK. Click the button below to get in touch with our team and discover more about the technology and use cases.

Get in touch

Cloud4Wi Passpoint SDK empowers mobile apps with instant and automaticfully-encrypted WiFi connection upon arrival to enabled locations, elevating customer experience andunlocking new location-based experiences.

contact our team

Seamless secure Wi-Fi

57% of shoppers use retailer mobile apps in-store and they need a fast and reliable connection. Dont make them ask, just get them online.

Cloud4Wi Passpoint SDK empowers your app with a seamless, secure connection upon arrival in all the brand location. All your mobile users will be automatically connected and authenticated to the WiFi network as soon as they are in the rage of the network.

Location Events

The automatic connection to WiFi allows Cloud4Wi to detect accurately all the customer interactions and push the relevant events to your application systems.

Using Location events you can create new location-based experiences for your mobile users. For example, you can send timely and localized promotions and messages via push notifications, you can personalize the app experience based on the store location, alert your associates and support team with a VIP customer arrives.

Benefits

Frictionless customer onboarding You can design your own enrollment experience, asking users to activate the service or just making it happen with zero friction

EnhancedWPA2 security compared to open guest WiFi with Captive Portal.

Accurate location events. Cloud4Wi detects mobile customers as soon as they arrive, stay and leave form any location and can notify your application servers to unlock new location-based experiences and services (see webhooks )

Boost app KPIs, usage, engagement and retention. By unlocking new benefits, you are giving your users more reason to download, keep and use the app.

Easy integration into any mobile app. We provide you a native SDK for any platform and development framework to make it faster.

For every business

Passpoint MObile SDK empowers apps of any business and vertical. Here some examples:

Retail mobile apps

Co-working spaces mobile apps

Hotels mobile apps

Banks mobile apps

Fitness and health clubs mobile apps

Loyalty programs mobile apps

Casinos gaming apps

Theme parks mobile apps

Restaurants and food-related mobile apps

Transport mobile apps

Health groups mobile apps

How it works

The SDK allows the mobile app to pre-activate users in the Cloud4Wi platform and generate a local HS2.0 WiFi profile that enables the phone to automatically associate and authenticate to the hotspot 2.0 access points, even if the app is in background.

The SDK provides 3 main methods:

Create the user. In order to authenticate the user on the network, each user has a unique account in the Cloud4Wi core authentication system, identified by a username and password. The credentials can be generated by the mobile app and sent to CLoud4wi or they can be generated automatically by the Cloud4Wi cloud authentication systems.The method also allows passing the user contacts and demographic profile so it gets stored in the Cloud4Wi CRM for using the Cloud4Wi marketing tools.

Get User AgreementsTo create a user account in the system, Cloud4Wi requires to specify also the user agreements that have been accepted by the user. Cloud4Wi allows clients to create their own custom agreements and opt-ins, so this method allows the developer to pull the list of all the possible opt-ins configured in the Cloud4Wi account so that they can be used when invoking the method to create a new user.You can also use this method to gather the list of opt-ins and create an experience in your app to collect your customer's consent.

Generate and activate the profileOnce the user account has been pre-activated, this method allows generating a configuration profile for the user device.Note that this configuration profile can't be found in the profiles managed by the smartphone OS, so they cannot be removed manually by the users.Bu uninstalling the app, also the WiFi is removed automatically.

Get started in 3 steps

Setup the network Add to your Access Point a dedicated SSID configured with hotspot 2.0 settings. We provide a step by step documentation for each certified vendor. Add the Access Point MAC address in the Cloud4Wi Dashboard. At the moment, the following vendors have been certified:Cisco Meraki, Cisco WLC, Ruckus, Cambium Networks, Aerohive.We are working to support other WiFi vendors, if the vendor you are using is not in this list get in touch with us.

Install and integrated the SDK Get the authorization token form Cloud4Wi and install the SDK following the user guide. You can develop any enrollment flow that you like (such as a button, a form or an additional opt-in) or just make it completely transparent to the user.

The SDK is available forIOs,Android,ApacheCordovaandReact Native.The SDK code, technical documentation, and examples are published on a GitHub repository. At this time, the access is restricted to the participants of the Beta Program.

Receive Location Events Form the Cloud4Wi Dashboard, you can enable the webhooks that you are interested in and send the notifications to your application servers. Learn more about the webhooks.

Try the demo mobile app

In order to let you test the possible experience before starting to code, we developed a demo mobile app (for IOs and Android) that allows you to see the experience and even run a real-life proof of concept. Contact us to learn more and get started with Passpoint SDK.

Request Access to the Beta Program

Not only mobile apps..

If you don't have a mobile app but still want to bring the benefits of Passpoint to all your customers, you can use other channels to invite the user to download a configuration profile on their device that will make their deviceautomatically connecting to the network whenever they are in range.

Email or SMS: invite your customers to enroll in the service via email or SMS. You can send the message when they register online, when they book their visit and connect it to any web form using our dedicated APIs.

In-store QR codes: by scanning a QR code, customers reach an onboarding portal where you can collect their profile and consent and immediately download the profile on their device.

Captive Portal: you can also leverage the standard captive portal to invite users to unlock the benefit of the Passpoint connection, inviting them to download the profile during the WiFI onboarding

To learn more about the above use cases and technology, please .

Getting Started

Click here to download a skeleton MyApps app

This is a skeleton project that provides a very barebones backend with limited capability to save the configuration and provides a static page to serve as the App in the Access Journey.

The backend is written in Node.js and depends on npm to handle dependencies. To set up this skeleton application for your own project, you will need to have Node installed on your computer and be able to run npm. To get setup, simply download the zip file, extract, and runnpm install.

npm install

To start the server, use the command

npm start

Testing the App

Hosting with a URL

To properly test the app, you will most likely want to have it be part of an Access Journey or Welcome Portal. To publish an app on the developer portal you will need to have the app hosted with a proper url. An easy way to accomplish this is by using Heroku.

Hosting with SSL

Furthermore, for an Admin Page you build to work within Volare, it will need to be hosted with https enabled. Your Admin Page is called with an embedded iframe and because Volare is secure, most modern browsers will block any attempts to load insecure resources. Any iframe that tries to load an http page as opposed to https will be blocked. Hosting with https can be accomplished by using any number of Certificate Authorities online. A free and reliable one you may use is Let's Encrypt.

The App

These files represent a very basic demonstration app that shows some of the functionality of the MyApps SDK. The only reason for there being a javascript file in this sample is to retrieve a saved configuration that was stored with the Admin Page.

Index.html

<!DOCTYPE html>

<html>

<head>

<title>Sample MyApps application</title>

<script src="https://splashportal.cloud4wi.com/myapps/v1/myapps-sdk.js"></script>

</head>

<body>

// The following lines are purely optional and are for demonstration purposes

This is a sample MyApps application

<div id="app"></div>

<p>The next URL is <script>MYAPPS.getNextUrl();</script></p>

<p>You can go Next in the Access Journey using <button onclick="MYAPPS.goNext()">MYAPPS.goNext()</button></p>

<p>You can go Home to the Welcom Portal if launched by App Bar using <button onclick="MYAPPS.goHome()">MYAPPS.goHome()</button></p>

<p>You can do whichever is contextually relevant using <button onclick="MYAPPS.end()">MYAPPS.end()</button></p>

<p> Finally, you can Render a Navbar using <button onclick="MYAPPS.renderNavbar()">MYAPPS.renderNavbar(navbarOptions)</button></p>

<p> <strong>Note</strong>: the navigation will not work without the proper query strings added by Access Journey and/or Volare Website </p>

<script src="js/app.js"></script>

</body>

</html>

App.js

This file represents the logic that was used in this project to communicate with the backend and retrieve a saved message.

var settings = {};

var app = document.getElementById("app");

var getConfiguration = function() {

var xhr = new XMLHttpRequest();

xhr.onreadystatechange = function() {

if (xhr.readyState === XMLHttpRequest.DONE && xhr.status === 200) {

settings = JSON.parse(xhr.responseText);

app.innerHTML = "Message: " + settings.message;

}

};

xhr.open("GET", "api/config", true);

xhr.send();

}

getConfiguration();

// Example of retrieving Context Information:

var sk = MYAPPS.getSk();

var context = null;

var getContext = function() {

var xhr = new XMLHttpRequest();

xhr.onreadystatechange = function() {

if(xhr.readyState === XMLHttpRequest.DONE && xhr.status === 200) {

context = JSON.parse(xhr.responseText).data;

}

};

xhr.open("GET", 'https://volare.cloud4wi.com/controlpanel/1.0/bridge/sessions/' + sk);

xhr.send();

}

The Settings Page

These files demonstrate a possible Admin Page accessed from the Volare Admin Panel. This page presents a single text input field. When the save button is pressed, the page sends an HTTP POST request the backend server where that message is saved. The saved message in the backend is then later retrieved by the user-facing application in the Access Journey.

Admin.html

<!DOCTYPE html>

<html>

<head>

<title>Sample MyApps application</title>

<script src="https://splashportal.cloud4wi.com/myapps/v1/myapps-sdk.js"></script>

</head>

<body>

This is a sample admin page

<form id="config-form">

<label for="message">Message: </label>

<input type="text" name="message">

<input type="submit" value="Save">

</form>

<script src="js/admin.js"></script>

</body>

</html>

Admin.js

var form = document.getElementById("config-form");

// Make AJAX POST request to save the configuration to server

var saveConfig = function(config) {

var xhr = new XMLHttpRequest();

xhr.onreadystatechange = function() {

if (xhr.readyState === XMLHttpRequest.DONE && xhr.status === 200) {

console.log("settings saved successfully");

}

};

xhr.open("POST", "api/config", true);

xhr.setRequestHeader("Content-type", "application/json");

xhr.send(JSON.stringify(config));

};

// Add listener to submit function of form

form.addEventListener("submit", function(e) {

e.preventDefault();

var message = e.target.elements.message.value;

saveConfig({message: message});

return false;

});

The backend

These files are a very basic Node.js Express Server used to save a message from the Admin Page and provide it to the App in the Access Journey. This could easily be replaced by PHP, Ruby on Rails, or any other language that can handle HTTP requests. Of course, without the need to save and access data, the need for an Admin Page and backend is limited. MyApps can easily be solely a static page with MyApps SDK being the only javascript on the page.

Server

// ============================================================================

// Setup

// ============================================================================

var express = require('express');

var http = require('http');

var app = express();

// Port from script argument, falls back to environment variable

// if neither of the above, defaults to 8080

var port = process.argv[2] || process.env.PORT || 8080;

// BodyParser middleware to enable reading json requests

var bodyParser = require('body-parser');

app.use(bodyParser.json());

// ============================================================================

// Create API routes

// ============================================================================

var router = express.Router();

var configHandler = require('./src/configHandler');

router.route('/config')

.get(configHandler.get)

.post(configHandler.post);

app.use('/api', router);

// ============================================================================

// Start Server

// ============================================================================

// Add static file serving

// serves the folder 'public' on server root

app.use('/', express.static('./public'));

// Create and Start Server

var server = http.createServer(app);

server.listen(port, function() {

console.log('Server listening on port ' + port);

});

configHandler

This is NOT a robust way to save data. If the app crashes at any time, any changes are lost. This is for demonstration purposes.

var settings = {

message: "this is a test message"

};

exports.get = function(req, res) {

res.json(settings);

};

exports.post = function(req, res) {

settings = req.body;

res.json(settings);

};

Including the Web SDK in your Application

The SDK can be included with your application by including the following tag in your HTML document.

<script src="https://splashportal.cloud4wi.com/myapps/v1/myapps-sdk.js"></script>

Including the script in your application gives access to theMYAPPSobject. This object encapsulates a handful of functions that allow your application to integrate itself into the Access Journey provided by Volare.

goNext()

Moves the user away from the page to the next destination on the Access Journey.

Not available when the application is opened from the App Bar as it is not a part of the Access Journey.

MYAPPS.goNext();

getNextUrl()

Returns the URL that points to the next destination on the Access Journey. It is the same URL that would be used by thegoNext()function to continue the Journey.

Not available when the application is opened from the App Bar as it is not a part of the Access Journey.

MYAPPS.getNextUrl();

goHome()

Moves the user away from the page to the Welcome Portal. In many cases, has the effect of going Next, but can also have the effect of going back. Useful for App Bar applications that can use it as a "back" button in lieu of not having access to thegoNext()function.

MYAPPS.goHome();

end()

CombinesgoNext()andgoHome(). If available, will behave asgoNext(), but revert togoHome()otherwise.

MYAPPS.end();

renderNavbar(navbarOptions)

Takes as an argument a JavaScript Object that contains options that are applied to the navigation bar. The options it supports are a delayed timer before the continue button is revealed, foreground and background color, and the text shown in the upper left corner.

let navbarOptions = {

apn: "Welcome", // Label text for upper left

fontColor: "white", // Font Color

backgroundColor: "black", // Background Color for gradient

nextBtn: 10 // Number of seconds for delay timer

}

The options object does not have to be filled, as there are default options that can be relied upon. One simply has to ommit an entry in the object to revert to the default settings.

MYAPPS.renderNavbar(navbarOptions);

The styling is hardcoded into thenavtag that is produced, so apart from JavaScript manipulation, custom styling is fairly limited.

showNextBtn()

This function changes the style of the "next" button produced by therenderNavbarfunction fromhiddentoinline-block.

MYAPPS.showNextBtn();

getSk()

Returns the session key necessary for the context API call.

MYAPPS.getSk();

getParam(param)

Returns the value of the given argumentparamby parsing the URL.

MYAPPS.getParam(param);

Available parameters:

sk: session key, used for the context API call

tgr: step of the Access Journey that called the App

trOpn: Connect

trRgt: Sign up

trPlgn: Log in Attempt

trLgn: Log in

trLgt: Disconnect

false: When not part of the Access Journey

Context APIs

Making a GET request to the API url with the session key appended will return with a json object depending on the context with which the API was called. For example, calling the API from the Admin Panel will return different results than calling it from within the access journey.

The API endpoint is:

https://volare.cloud4wi.com/controlpanel/1.0/bridge/sessions/{SESSION_KEY}

Response when used in the Volare Admin Panel

From Tenant level

{

"status": "success",

"data": {

"lang": "eng",

"auth": {

"level": "tenant",

"tenantId": "1001"

}

}

}

From Venue level

{

"status": "success",

"data": {

"lang": "eng",

"auth": {

"level": "wifiarea",

"tenantId": "1001",

"wifiareaId": "3246b0001"

}

}

}

Response when used in the Welcome Portal

User is Not logged in

{

"status": "success",

"data": {

"customer": {

"is_logged": false,

"lang": "eng"

},

"hotspot": {

"city": "Livorno, Italy",

"id": "9067",

"identifier": "685112345D_illiade",

"latitude": "45.960782503827",

"longitude": "12.091283106750",

"mac_address": "685112345D",

"name": "Odissea",

"state": "Livorno",

"tag": "hotspot",

"zip": "Livorno",

},

"tenant": {

"name": "Taylor's Tenant",

"read_only": false,

"tenant_id": "1001"

},

"wifiarea": {

"name": "Livorno Venue",

"wifiarea_id": "18cde0005"

}

}

}

User Authenticated and logged in

{

"status": "success",

"data": {

"customer":{

"is_logged":true,

"lang":"eng",

"id":"rlC.6yTePhzYg",

"first_name":"John",

"last_name":"Doe",

"username":"706B5C1D",

"gender":"",

"birth_date":"0000-00-00 00:00:00",

"phone":"",

"phone_prefix":"",

"email":"[email protected]",

"mac_address":[]

},

"hotspot": {

"city": "Livorno, Italy",

"id": "9067",

"identifier": "685112345D_illiade",

"latitude": "45.960782503827",

"longitude": "12.091283106750",

"mac_address": "685112345D",

"name": "Odissea",

"state": "Livorno",

"tag": "hotspot",

"zip": "Livorno",

},

"tenant": {

"name": "Taylor's Tenant",

"read_only": false,

"tenant_id": "1001"

},

"wifiarea": {

"name": "Livorno Venue",

"wifiarea_id": "18cde0005"

}

}

}

Beta program

We are working to upgrade al the existing APIs to V3 within January 2020. At this time, V3 includes only a subset of APIs. If you are interested in using the new APIs, please Contact our team !

The V3 of Cloud4Wi API is designed to provide more scalability and improved performances. APIS V3 introduces a new authentication method as described below.

Retrieve API Key and Secret

On your Cloud4Wi Dashboard, go to Cloud4Wi APIs apps form the Settings > Marketplace page.Create a new Service enabling the Read / Write scopes as you need.

Finally, you can see the API Key and Secret clicking on the view icon.

Authentication

Using the clientKey and clientSecret generated in the section of services of control panel do a request to

/v1/sts/login/services

and get the JWT token from the response.

To have access to the resources put the token in the Authorization Header as Bearer.

Authorization: Bearer JWT

The JWT token expires after 1 day; to have a brand new token to do a new request to:

/v1/sts/login/services

AuthN/AuthZ Flow

API Responses

All endpoints will respond with an HTTP status code:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

200: Successful request

201: The request has been accepted

401: Unauthorised, clientkey/clientsecret not valid

403: Forbidden, the service is not authorized to access to the resource or the token is invalid/expired

409: Conflict, the request had semantic errors or invalid parameters

404: The resource does not exist

410: This endpoint has been revoked or removed

429: Too many requests, rate limit exceeded

500: Uncaught application error

Error responses also include an error message where relevant.

Example of error message:

{

"message": "Access Denied",

"path": "/sts/services/xxx"

}

APIs Rate Limits

All the API endpoints v1, v2 and v3 (APIs V3 are under the endpoint explore.cloud4wi.com ) have a rate limit configured:

burst: 60 requests/minute

daily: 15.000 requests/day

Faq

Where can I find the 'iss'

The token used has the JWT format ( https://en.wikipedia.org/wiki/JSON_Web_Token ).

You can find the iss inside the payload of JWT after you have decoded it.

Example of decoded JWT

header:

{

"alg": "HS256"

}

payload:

{

"aud": "service",

"iss": "srv-11111111-zzzz-yyyy-xxxx-2222222",

"exp": 1574173580,

"iat": 1574087186

}

signature:

HMACSHA256(

base64UrlEncode(header) + "." +

base64UrlEncode(payload),

secret

)

How to check the rate limit

In the response are returned some http headers where you can find the rate limits of the apis.

Two kind of limits are configured

Requests Rate Limits

Are the limits configured on the number of requests that arrives to the APIs.

X-Ratelimit-Limit-Minute: What is the limit per minute configured

X-Ratelimit-Remaining-Minute: How many requests left

X-Ratelimit-Limit-Day: What is the limit per day configured

X-Ratelimit-Remaining-Day: How many requests left

Objects Rate Limits

Are the limits configured on the number of objects elaborated (created/returned/edited/delete) through the Apis.

X-Ratelimit-Limit-<OBJECT>-Day: What is the limits configured for the object

X-Ratelimit-Remaining-<OBJECT>-Day: How many object left

Where <OBJECT> is the object interested in the limits.

If any of the limits configured is being reached, the APIwill return a HTTP/1.1 429 status code to the client with the following JSON body:

{ "message": "API rate limit exceeded" }

What is the 'cid'

The cid is the identifier that identifies univocally an object inside the Cloud4Wi APIs V3. It is related to the type of the object of the request, for example in the API

/v1/organizations/{cid}

the cid is the identifier of the organization in the API

/v1/customers/{cid}

the cid is the identifier of the customer

Where can I find the cid of the organization

You can find your organization cid in the control panel in the section /services

How to use the sid (scroll Id) in the search APIs

The sid (scroll id) can be used to retrieve a large number of results from a search request.

An initial search request without the sid must be executed to initialize the scroll session. In the response of the search request the sid parameter is returned inside the response.

As a second step, the received sid must be set along with the following requests where another batch of results is returned with a new sid. This new sid can then be used to retrieve the next batch of results, and so on. This process should be repeated in a loop until no more results are returned.

The time interval between 2 requests is 60 seconds; after that interval, the sid expires and no results are returned.

Examples

first request

Request:

GET customers/organizations/cid?size=100&hasEmail=true&hasPhone=false&ageVerification=true

Response:

{

"generated": "2019-11-20T16:56:06Z",

"totalCount": 216,

"count": 100,

"sId": "c5ecaa82e6b01e6dcb8d059ede66b8fe32ca25cfb376129fda99585a91e41253",

"customers": [

...

]

}

following requests

GET customers/organizations/cid?sId=c5ecaa82e6b01e6dcb8d059ede66b8fe32ca25cfb376129fda99585a91e41253

Response:

{

"generated": "2019-11-20T16:56:30Z",

"totalCount": 216,

"count": 100,

"sId": "36955899909af957fc8a6f8ba7c14ea6c295ce83581a7850ad89b40afff75a7a",

"customers": [

...

]

}

The Cloud4Wi public endpoints are powered by the same underlying technology that powers the core Cloud4Wi application. As a result, Cloud4Wi engineering closely monitors the usage of the public APIs to ensure a quality experience for users of the Cloud4Wi applications.

All integrations must comply with the Cloud4Wi Terms of Use and API Terms of Use. Please see these pages for more details:

https://cloud4wi.zendesk.com/hc/en-us/articles/205422285

https://cloud4wi.zendesk.com/hc/en-us/articles/360037286491

Starting on January 1st, 2020, we will start enforcing new API limits to all the new and existing Accounts, for both APIs V2 and V3.

The following rate limits will be appliedper each Account:

Burst:60/60 seconds

Daily:15,000

Integrations that poll Cloud4Wi for new or updated information are limited to polling a maximum of 15,000records per day, for each type of object. This limit applies to whole endpoints.

On each API response, you'll receive the status of your updated allowance, so you can keep track of the usage over time.

We reserve the right to change or deprecate the APIs over time - we will provide developers ample notification in those cases. These notifications will be provided through our product changelog.

Other terms:

You may create no more than 10 webhook subscriptions per Account

You may create no more than 1 service per Account on APIs V3

The Cloud4Wi REST APIs allow you to query meta-data about your accounts, end-users, Hotspots, Venues, accounting logs, Splash Portal impressions, Analytics data etc. .

Since the API is based on REST principles, it's very easy to write and test applications. You can use your browser to access URLs, and you can use pretty much any HTTP client in any programming language to interact with the API.

This section provides all the basic information you need to use Cloud4Wi REST APIs.If you are getting started, then you have to follow the workflow below:

Download

Get your API Secret.

Open the "Cloud4Wi API" application, ask for the API secret and agree to terms and conditions for the service.

Access the Developer Portal

http://developers.cloud4wi.com You can login with your Cloud4Wi account credentials

Start coding

Cloud4Wi REST APIs are based on REST principles, so you can easily interact with them regardless of the language you use.You can find some examples in the Developer Portal

Getting your API secret

Please note that in order to interact with the Cloud4Wi REST APIs, it is necessary to have an "API key" / "API Secret" pair.

You can get your API credentials by accessing the "Cloud4Wi API" page form the Marketplace section of the Cloud4Wi Dashboard. The API key identifies a Tenant and cannot be changed.You can, however, change your API secret at any time by clicking on the Renew API Secret button in the "Cloud4Wi API" page. The API secret is a secret shared between Cloud4Wi and your application and for this reason, it must not be public in any case.

If you are using your account for the first time, you need to generate your API secret by clicking the"+" button and accepting terms of use for the API service.

Data scrolling and pagination

When you deal with a large number of records, you need to retrieve smaller chunks of data with multiple API calls.

Most of the API endpoints use the pagination method to move across multiple chunks of records, using the limit and offset parameters. The limit parameter determines the maximum number of records returned in a single API call. The offsetparameter indicates the index of the first records to be retrieved.

Some API endpoints are designed to provide access to the data at a faster speed. This method requires you to use the ScrollId parameter, and it is available in the following endpoints:

/visits

/connections

/troubleshooting/

/troubleshooting/

Each ScrollId token value has an expiration set to 2 minutes and each API iteration can retrieve up to 9.999 records.

Some API endpoints (/connections and /troubleshooting) provide both methods while managing the transition from the standard pagination technique to the ScrollId.

If you are already using the APIs with the standard pagination technique, you can keep using it by using limit and offset parameter and omitting the scollId parameter.

Whenever you want to migrate to the ScrollId method, you can simply start using the ScrollId token in the API call (offset and limit values won't be considered in this case).

Examples

Please check out our sample scripts.

Description

Used language

File

Returns a CSV file with all active users on the Organization (API v1)

PHP 5

Download

Returns a CSV file with all active users on the Organization (API v2)

PHP 5

Webhook is a technical name to indicate a web-based notification that sends a messageto an URL when certain actions happen.

Cloud4Wi allows you to setup a webhook the following types of event:

Sign-up: the event is triggered after a user is registered to the database (either registration from the Splash Page, Cloud4Wi Dashboard or Kiosk)

Login: the event is triggered after a guest user signs-in on the guest Wi-Fi

Presence: the event is triggered after a user's device is detected by the access point

https://en.wikipedia.org/wiki/Server_Name_Indication

Webhooks can be created in the Cloud4Wi Dashboard of your Cloud4Wi Company Account, from Manage > Notifications.

The page shows a summary of the existing notifications.

For each webhook, you can check the percentage of notifications that have been delivered successfully and those which originated an error.

You can specify a list of venues where the webhook is enabled

You can enable or disable the webhook

You can test the webhook by clicking on the icon ()

Note: at the moment you can not edit an existing webhook. But you can delete and then re-create it.

Create a webhook

To create a webhook you have to click on the Add button on the top of the page.

On the next page, you can set the followingdata:

Name: name of your webhook, for inventory purposes

Type: type of event, either login or sign-up

URL: end-point of the HTTP POST request (for example https://yourdomain.com/myapps/webhook.com),The end-point of the HTTP POST request of the webhook can be http and https; if https the server must be correctly configured in order to support the Server Name Indication (SNI) ().

Auth Token: validation code that will be included in the header of each HTTP POST request so that the receiver can validate the source of the POST

Venues: the venues where the webhook can be triggered

Limitations:

At the moment you can not edit existing a webhook. But you can delete and then re-create it.

Technical details:

The Auth Token is included in the HTTP header of the POST request with the name "Authorization".

HEADERS

Content-Type: application/json

Accept-Charset: UTF-8

Cf-Ipcountry: IE

Cf-Ray: 3882e1b1980f2969-DUB

Accept: application/json

Authorization: 1234567890

The HTTPS POST data is a JSON file containing the following dataset:

{ "userId":"0ef3d69c170266937600e16b7189c037", "tenantId":"617d17a5639aea2f7728f48d251b9def", "venueId":"2c9f929f59b1881b015a3726ab880b8d", "hotspotId":"344759de5464435d80cf0e2780247975", "event":"login", "timestamp":1562753268, "username":"BDF017C0", "firstName":"Ivan", "lastName":"Muccini", "gender":"", "phone":"+14151234567", "email":"[email protected]", "birthDate":"", "provider":"cloud4wi", "marketing":false, "type":"guest", "online":true, "visitCount":"1", "lockedRegistration":false, "deleted":false, "civilStatus":"Mr", "country":"IT", "customOptin":{ "myCustomOptInClause_1":false "myCustomOptInClause_2":true }}

Notes:

The hotspotId parameter is not available on the Sign-Up webhook when users register from a Kiosk or they are manuallycreated from the Cloud4Wi Dashboard.

The customOptin key contains all the defined custom opt-in clauses. In case no clause is defined on the organization, then the key will not appear.

Listener example in PHP

Here a simple example to catch the webhook message and parse the data:

<?php$headers = getallheaders(); //get headers$jsonPayload = file_get_contents('php://input'); //get the json body$aPayload = json_decode($jsonPayload, true);//headers$auth = $headers['Authorization'];//payload$event = $aPayload['event'];$userId = $aPayload['userId'];$tenantId = $aPayload['tenantId'];echo $auth;echo $event;echo $userId;echo $tenantId;?>

A new data privacy law in California

Protecting customer data and privacy is a fundamental and essential requirement of running a business. Back in May 2018, we saw the introduction of the European data privacy law known as theGeneral Data Protection Regulation(GDPR). In January 2020, a similar privacy law known as theCalifornia Consumer Privacy Act(CCPA) will come into effect. Although the law continues to be amended by the California legislature, there are some things you should be aware of if you conduct business in California. Ifyou'veworked on complying with the GDPR, youre in good shape to meet some of the CCPA requirements. Otherwise, its time to prepare.

On this page, we'll walk you through the basics of the law, and some of the most relevant parts for Cloud4Wi customers. As the January deadline draws nearer, we'll create more product-specific resources to help you meet some of the CCPA's requirements. Although most Cloud4Wi customerswon'tneed to make changes because of the CCPA, its important to find out if you meet the specific requirements.

Disclaimer:This website is neither an exhaustive summary of the California Consumer Protection Act (CCPA) nor legal advice for your company to use in complying with it. Instead, it provides background information to help you better understand the CCPA and how it can apply to your business. This legal information is not the same as legal advice, where an attorney applies the law to your specific circumstances, so you should consult an attorney if youd like advice on your interpretation of this information or its accuracy. You may not rely on this paper as legal advice, nor as an endorsement of any particular legal understanding. You may read more about recent movement toward a federal data privacy law here and here. Cloud4Wi is and will continue monitoring both the development of federal privacy legislation as well as subsequent amendments to the CCPA, and continue to update this page as necessary.

What is the CCPA?

The California Consumer Privacy Act (CCPA) establishes and enhances consumer privacy rights for California residents and imposes rules on businesses that handle their personal information. The CCPA is the most extensive consumer privacy legislation passed in the United States to date. It goes into effect on January 1, 2020, and the California Attorney General is expected to issue regulations clarifying certain provisions of the CCPA before then.

Does the CCPA apply to my business?

The CCPA applies to anyfor-profit entity doing business in Californiathat collects and controls the processing of a consumers personal information (controllers) and also satisfies ANY one of the following thresholds:

Exceeds $25 million gross revenue annually,

Handles the personal information of 50,000 or more California consumers, households, or devices annually, or

Derives more than 50% of annual revenue from selling consumers' personal information.

The CCPA also applies to any business that controls or is controlled by an entity that meets one of the above criteria and shares common branding with that entity. For example, non-profit organizationswon'tneed to comply with the CCPA unless they are owned by, control, or share branding with a for-profit business.

Who and what does the CCPA protect?

The CCPA protects privacy by affording Californians the right to access, delete, and opt-out of the sale of their data. The CCPA protects consumers, which are broadly defined as California residents. Consumers extends to both California residents currently in the state and those traveling outside of the state. They encompass customers of goods and services, employees, and business-to-business transactions.

You might be wondering what type of data is protected. Right now, the data covered can be broadly described as all data collected on consumers. You can think of it as data that directly or indirectly, identifies, describes, or can reasonably be linked to a particular consumer or household. For example, commercial internet activity information and any inferences drawn about a consumer apply. Theres currently a non-exhaustive list of specific categories of personal information defined in section 1798.140 of the law.

Important requirements under the CCPA

Individuals rights

The CCPA grants consumers rights to know what personal information a business sells, discloses, or collects about them as well as the categories of third parties who purchased or received their data. Consumers have the right to obtain a copy of personal information collected about them by making verified consumer requests. Customers then have the right to transmit the information from one entity to another.

Consumers can request that a business delete any of the personal information that the business has collected from them. The CCPA creates certain exceptions to this deletion right, like when personal information is necessary to perform a contract or complete a transaction.

Consumers are given the right to opt-out of the sale of their personal information, and the CCPA prohibits businesses from discriminating against consumers that exercise their opt-out rights. Companies cannot ask consumers to sign contracts that limit their data privacy rights under the CCPA. This includes contract provisions limiting or waiving the right to a specific remedy or means of enforcement for an alleged violation.

Internal expectations for your business

Making required disclosures: Businesses must notify consumers of their rights under the CCPA, including their right to deletion, right to know, and data portability rights as well as how to exercise these rights. These required disclosures can either be made via privacy policies, in CCPA-specific notices, or at the time the personal data is collected. Companies privacy policies must lay out how the collected data will be used. The CCPA imposes obligations for companies that sell a consumers personal information and/or the data of children. However, Cloud4Wi customers are not allowed to use our products to sell data or collect childrens data. See our Privacy Policy and Terms of Use for more information.

Responding to consumer rights requests: Businesses must implement processes to respond to verified consumer requests and opt-out requests. For example, responses to customer requests must cover the 12-month period preceding the request, so companies must have a way to date the data they collect.

Access and portability: Businesses must make at least two methods for submitting requests available to consumers including, at a minimum, a toll-free telephone number and a website address if the business maintains one. Businesses must respond to consumers requests for information within 45 days of receiving a request, which may be delivered by mail or electronically in a portable format. However, for online-only businesses, one proposed amendment to the CCPA allows them to make, at a minimum, only an email address available for submitting requests for information. You may track the status of this amendment here.

Deletion: If requested, businesses must delete the consumers personal information from its records unless maintaining the information is necessary to complete a transaction, for security or fraud-prevention purposes, or another purpose listed in the Act.

Opt-out: Companies that sell data must disclose that they do so to their customers, and include a Do Not Sell My Personal Information link giving consumers the opportunity to opt-out both in a privacy policy and on the companys website homepage. If a consumer opts-out or refuses to opt-in, the business must honor that request and continue to provide equal service and pricing to consumers that opted-out.

What happens if Idon'tcomply with the CCPA?

The Act is enforced by the California Attorney General, and currently provides businesses 30-days to comply if accused of noncompliance. However, a proposed bill removes this time period and allows for enforcement immediately. Civil penalties may be imposed of up to $2,500 per violation or $7,500 for intentional violations. The CCPA extends a private right of action to consumers, giving businesses exposure not only to government fines but also to lawsuits from customers.

How is Cloud4Wi helping you prepare for the CCPA?

Since the CCPA is not finalized and is subject to amendment by the CA legislature, wearen'table to make representations with respect to our compliance with the CCPA. What we know is the following:

There is and will likely continue to be a significant amount of overlap between the CCPA and the GDPR.

Cloud4Wi has extensive resources on GDPR, including this playbook, that explain our product and system features and functionality used by us and by our customers to support compliance with GDPR.

A good portion of the existing product and system features, processes and policies (that are currently used for GDPR compliance) can be used in the same ways for compliance with CCPA (in whatever final form). Example: you may handle Access and Deletion Requests (these are currently requirements under both bodies of law) by using our existing functionality.

We will provide more information on our official CCPA playbook or other resources once the CCPA is finalized and as they become available.

Be on the lookout for new blog posts and updates by subscribing to our blog.

DATA PROCESSING AGREEMENT

Last Updated: May 24th, 2018

This Data Processing Agreement (DPA) is made and entered into as of the date of last signature below (Effective Date) by and between you, our Customer (hereinafter referred to as Client, or Controller), and us Cloud4WI (referred to as Processor). This Data Processing Agreement is a supplement to and made a part of the Customer Terms of Service ( Agreement ).

If you are accepting these Data ProcessingAgreement on behalf of Customer, you warrant that: (a) you have full legal authority to bind Customer to these Data ProcessingAgreement; (b) you have read and understand these Data ProcessingAgreement; and (c) you agree, on behalf of Customer, to this Data Processing Agreement. If you do not have the legal authority to bind Customer, please do not accept these Data Processing Terms.

1. DEFINITIONS

All capitalized terms used in this DPA shall have the meanings given to them below:

1.1 Applicable Data Protection Law: means all applicable international, federal, national and state privacy and data protection laws that apply to the processing of Personal Data that is the subject matter of the DPA (including, where applicable, European Data Protection Law).

1.2 Controller: means the entity that determines the purposes and means of the processing of Personal Data, and for the purposes of this DPA means Client.

1.3 European Data Protection Law: means: (i) prior to 25 May 2018, the EU Data Protection Directive 95/46/EC, and any applicable national implementation of it; and (ii) on and after 25 May 2018, the EU General Data Protection Regulation 2016/679 ("GDPR") and any applicable national laws made under the GDPR.

1.4 Personal Data (Data): means any information relating to an identified or identifiable natural person; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

1.5 Processor: means an entity that processes Personal Data on behalf of the Controller, and for the purposes of this DPA means Cloud4Wi.

1.6 Service (Services): means any product or service provided by the Processor to the Client pursuant to the DPA and the Agreement.

1.7 Data Protection Officer (DPO): Professional figure, provided for in the EU Regulation, acts as a reference with the Guarantor for the protection of personal data. The DPO must guarantee independence and autonomy from the organization in which it operates, during the performance of its functions, and the absence of conflict of interests. It oversees compliance with the EU Regulation and collaborates to conduct a preliminary assessment of the Processing of Data so that there are no negative impacts on fundamental rights and freedoms; it is also a support for keeping the personal data activity register.

The definitions not present have the same meaning as in the General Data Protection Regulation of 2016/679.

2.GENERAL DATA PROTECTION OBLIGATIONS

2.1 Relationship of the Parties: As between the Parties, Client is the Controller and appoints Cloud4WI as a Processor to process the Personal Data described in section 1.4.

2.2 Purpose limitation: Processor shall process the Data as a Processor only for the purposes described in Annex 1 and strictly in accordance with the documented instructions of the Client (the "Permitted Purpose") and processing outside the scope of these instructions (if any) shall require prior written agreement between Client and Cloud4Wi.

Notwithstanding anything to the contrary in the Agreement (including this DPA), Client acknowledges that Cloud4Wi shall have a right to use and disclose data relating to the operation, support and/or use of the Services for its legitimate business purposes, such as billing, account management, technical support, product development and sales and marketing. To the extent any such data is considered Personal Data under Data Protection Laws, Cloud4Wi is the Data Controller of such data and accordingly shall process such data in accordance with the Cloud4Wi Privacy Policy and Data Protection Laws.

2.3 International transfers of Data: Processor shall, at all times provide, an adequate level of protection for the Data, wherever processed, in accordance with the requirements of Applicable Data Protection Law. Processor shall not process or transfer any Data originating from the European Economic Area (EEA) in or to a territory which has not been designated by the European Commission as providing an adequate level of data protection unless it has first obtained Client's prior written consent.

2.4 Confidentiality of processing: The Processor shall keep strictly confidential all Personal Data that it processes on behalf of Client. The Processor shall ensure that any person that it authorises to process the Data (including the Processor's staff, agents and subcontractors) (each an "Authorised Person") shall be subject to a strict duty of confidentiality (whether a contractual duty or a statutory duty), and shall not permit any person to process the Data who is not under such a duty of confidentiality. Processor shall ensure that only Authorised Persons will have access to, and process, the Data, and that such access and processing shall be limited to the extent strictly necessary to achieve the Permitted Purpose. Processor accepts responsibility for any breach of this DPA caused by the act, error or omission of an Authorised Person.

2.5 Security: Processor shall implement appropriate technical and organisational measures to protect the Data from (i) accidental or unlawful destruction, and (ii) loss, unauthorized alteration, unauthorised disclosure of, or unauthorized access to the Data. At a minimum, such measures shall include the security measures identified in Annex 2 to this DPA.

Client acknowledges that the Service is not intended or designed for the Processing of Sensitive Information, and the Client agrees not to provide any Sensitive Information through the Service.

2.6 Subcontracting: Controller consents to Processor engaging third party sub-Processors, including Certified Partners of Processor, to process the Data provided that:

Processor will provide to Client an up-to-date list of its then-current sub-Processors upon request; the list is also published online at https://cloud4wi.zendesk.com/hc/en-us/articles/360003452492

Processor provides at least thirty (30) days' prior written notice of the addition or removal of any sub-Processor (including the categories of Data processed, details of the processing it performs or will perform, and the location of such processing).

In all cases, Processor shall impose the data protection terms on any sub-Processor it appoints that at a minimum meets the requirements provided for by this DPA and Processor shall remain fully liable for any breach of this DPA that is caused by an act, error or omission of its sub-Processor.

2.7 Cooperation and individuals' rights: To the extent permitted by Applicable Law, Processor shall provide reasonable and timely assistance to Client to enable Client to respond to: (i) any request from an individual to exercise any of its rights under Applicable Data Protection Law; and (ii) any other correspondence, enquiry or complaint received from an individual, regulator, court or other third party in connection with the processing of the Data. In the event that any such communication is made directly to Processor, Processor shall instruct such individual to contact Client directly.

2.8 Data Protection Impact Assessment: If Processor believes or becomes aware that its processing of the Data is likely to result in a high risk to the data protection rights and freedoms of individuals, it shall promptly inform Client of the same. Processor shall provide Client with all such reasonable and timely assistance as Client may require in order to conduct a data protection impact assessment and, if necessary, consult with its relevant data protection authority.

2.9 Security incidents: Upon becoming aware of a Security Incident, Processor shall inform Client without undue delay (and, in any event, within 32 hours) and shall provide such timely information and cooperation as Client may require in order for Client to fulfil its data breach reporting obligations under (and in accordance with the timeliness required by) Applicable Data Protection Law and relevant contractual obligations owed by Client to its subscribers. Processor shall cooperate with Client in taking all appropriate measures and actions as are necessary to remedy or mitigate the effects of the Security Incident, shall manage and modify its systems to remedy or mitigate such Security Incident and the likelihood of future similar Security Incidents, and shall keep Client informed of all developments in connection with the Security Incident. Processor shall not notify any third parties of a Security Incident affecting the Data unless and to the extent that: (a) Client has agreed to such notification, and/or (b) notification is required to be made by Processor under Applicable Data Protection Laws.

2.10 Deletion or return of Data: Upon termination or expiry of the DPA, Processor shall (at Client's request) destroy all Data (including all copies of the Data) in its possession or control (including any Data subcontracted to a third party for processing); provided, however, that customer data (including Data) may be retained on backup for a period of up to eighteen (18) months for legal and compliance purposes. Notwithstanding the foregoing, Processor shall not reduce the security measures at any time until such Data is permanently deleted.

2.11 Audit: Processor shall permit Client (or its appointed third-party auditors) to audit Processor's compliance with this DPA, and shall make available to Client all information, systems and staff necessary for Client (or its third-party auditors) to conduct such audit. Processor acknowledges that Client (or its third-party auditors) may enter its premises for the purposes of conducting this audit, provided that Client gives it reasonable prior notice of its intention to audit, conducts its audit during normal business hours, and takes all reasonable measures to prevent unnecessary disruption to Processor's operations. Client will not exercise its audit rights more than once in any twelve (12) calendar month period, except (i) if and when required by instruction of a competent data protection authority; or (ii) Client believes a further audit is necessary due to a Security Incident suffered by Processor. Processor shall also respond to any written audit questions submitted to it by Client.

2.12 Indemnity: Processor (the "Indemnifying Party") shall defend and fully indemnify Client from and against all loss, harm, cost (including reasonable attorney's fees), fines, expense, and liability that Client may suffer or incur arising as a result of Processor's breach or non-compliance with this DPA. The foregoing shall be subject to the indemnification procedures set forth in the Agreement.

2.13 General cooperation to remediate: In the event that Applicable Data Protection Law, or a data protection authority or regulator, provides that the transfer or processing of Personal Data under this DPA is no longer lawful or otherwise permitted, then the Parties shall agree to remediate the processing (by amendment to this DPA or otherwise) to the extent practical in order to meet the necessary standards or requirements. If Processor is unable to remediate the processing, then Client will be entitled to terminate the DPA (and any other agreement between the Parties relating to the provision of services by Processor to Client) without penalty.

3.TERM

3.1 The obligations placed upon the Processor under this DPA shall survive so long as Processor and/or its sub-Processors Process Personal Data on behalf of Client.

ANNEX 1

DETAILS OF PROCESSING OF CONTROLLER PERSONAL DATA

This Annex 1 includes certain details of the Processing of Controller Personal Data as required by Article 28(3) GDPR.

Subject matter and duration of the Processing of Controller Personal Data

The subject matter and duration of the Processing of the Controller Personal Data are set out in the Agreement and this DPA.

The nature and purpose of the Processing of Controller Personal Data

Cloud4Wi will Process Personal Data as necessary to perform the Services pursuant to the Agreement, as further specified in the Service Documentation, and as further instructed by Client in its use of the Services.

The categories of Data Subject to whom the Controller Personal Data relates

The Client may collect Personal Data with the Service, the extent of which is determined and controlled by Client, and which may include, but is not limited to Personal Data relating to the following categories of data subjects:

Any individual accessing and/or using or managing the Services through the Client's Service Account ("Users")

Any individual: (i) whose personal data is included in the Clients Service Account; (ii) whose personal data is stored on or collected via the Services, or (iii) to whom Users send communication or otherwise engage or communicate with via the Services, (ii) whose device identifier is collected via the Services using Tracking Technologies (collectively, "Subscribers")

The types of Personal Data to be Processed

The Client may collect and submit Personal Data of Users and Subscribers to the Processor, the extent of which is determined and controlled by Client on its sole discretion, depending also on services products, licenses, and subscriptions purchased by the client, and which may include, but is not limited to, the following categories of Personal Data:

User's Contacts and Profile data

First name

Last name

Email

Phone number

Company name and address

Subscriber's Contacts and Profile data

Subscriber identifier

First name

Last name

Title

Email

Phone number

Social network identities and publicly available details (including, for example, profile picture and demographic data)

Address or location

Birthdate

Age

Gender

Company

ZIP code

Other identification data (ex. passport number, identifiers of other services)

Details of Subscribers' devices used to connect to WiFi service

Subscriber identifier

Device identifier (WiFi MAC Address)

Device model

Device operative system

Subscriber's WiFi Service Authentication and Connections data

Subscriber identifier

Subscriber's credentials for WiFi service (Username andPassword)

Time, date and location of registration to the WiFi service

Time, date, location and duration of each WiFi connection

Device identifier (WiFi MAC Address) and IP Address of each WiFi connection

Subscriber's Activities data

Subscriber identifier

Type of activity (for example redeem offer, response to a survey, click on a call to action, etc...)

Content and details of the activity (for example survey responses)

Time, date and locationwhere the activity is performed (where applicable)

The following categories of Personal Data may be processed only with Cloud4Wi products, licenses, and subscriptions that include Location Services, on the sole discretion of the Controller:

Subscriber's Location data

Subscriber identifier

Device identifier (WiFi MAC Address)

Approximate time, date and duration of visits to each venue

Approximate location inside the venue whilst at a venue

The client may also upload content to Clients Service Account which may include Personal Data and special categories of data, the extent of which is determined and controlled by the Client in its sole discretion.

Tracking Technologies

Client acknowledges that in connection with the performance of the Services, Cloud4Wi may employ the use of cookies, unique identifiers, web beacons, WiFi location tracking, BLE location tracking and similar tracking technologies ("Tracking Technologies"). Customer shall maintain appropriate notice, consent, opt-in and opt-out mechanisms as are required by Data Protection Laws to enable Cloud4Wi to deploy Tracking Technologies lawfully on, and collect data from, the devices of Subscribers (defined above) in accordance with and as described in the Cloud4Wi Cookie Policy and Privacy Policy.

ANNEX 2

DESCRIPTION OF THE TECHNICAL AND ORGANIZATIONAL SECURITY MEASURES

This Annex 2 includes the description of the technical and organizational security measures implemented by the Data Processor.

Cloud4Wi currently observes the security practices described in this Annex 2. Notwithstanding any provision to the contrary otherwise agreed to by data exporter, Cloud4Wi may modify or update these practices at its discretion provided that such modification and update does not result in a material degradation in the protection offered by these practices. All capitalized terms not otherwise defined herein shall have the meanings as set forth in this DPA.

a) Access Control

i) Preventing Unauthorized Product Access

Outsourced processing: Cloud4Wi hosts its Service with outsourced cloud infrastructure providers. Additionally, Cloud4Wi maintains contractual relationships with vendors in order to provide the Service in accordance with this DPA. Cloud4Wi relies on contractual agreements, privacy policies, and vendor compliance programs in order to protect data processed or stored by these vendors.

Physical and environmental security: Cloud4Wi hosts its product infrastructure with multi-tenant, outsourced infrastructure providers. The physical and environmental security controls are audited for SOC 2 Type II and ISO 27001 compliance, among other certifications.

Authentication: Cloud4Wi implemented a uniform password policy for its customer products. Customers who interact with the products via the user interface must authenticate before accessing non-public customer data.

Authorization: Customer data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of Cloud4Wis products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the users permissions against the attributes associated with each data set.

Application Programming Interface (API) access: Public product APIs may be accessed using an API keyii) Preventing Unauthorized Product Use

Cloud4wi implements industry standard access controls and detection capabilities for the internal networks that support its products.

Access controls: Network access control mechanisms are designed to prevent network traffic using unauthorized protocols from reaching the product infrastructure. The technical measures implemented differ between infrastructure providers and include Virtual Private Cloud (VPC) implementations, security group assignment, and traditional firewall rules.

Intrusion detection and prevention: Cloud4Wi implemented a Web Application Firewall (WAF) solution to protect hosted customer websites and other internet-accessible applications. The WAF is designed to identify and prevent attacks against publicly available network services.

Static code analysis: Security reviews of code stored in Cloud4Wis source code repositories is performed, checking for coding best practices and identifiable software flaws.

Penetration testing: Cloud4wi maintains relationships with industry recognized penetration testing service providers for four annual penetration tests. The intent of the penetration tests is to identify and resolve foreseeable attack vectors and potential abuse scenarios.

iii) Limitations of Privilege & Authorization Requirements

Product access: A subset of Cloud4Wis employees have access to the products and to customer data via controlled interfaces. The intent of providing access to a subset of employees is to provide effective customer support, to troubleshoot potential problems, to detect and respond to security incidents and implement data security. Access is enabled through just in time requests for access; all such requests are logged. Employees are granted access by role, and reviews of high risk privilege grants are performed periodically. Employee roles are reviewed at least once every six months.

Background checks: All Cloud4Wi employees undergo a background check prior to being extended an employment offer, in accordance with the applicable laws. All employees are required to conduct themselves in a manner consistent with company guidelines, non-disclosure requirements, and ethical standards.

b) Transmission Control

In-transit: Cloud4Wi makes HTTPS encryption (also referred to as SSL or TLS) available on every one of its login interfaces and for every Splash Page hosted on the Cloud4Wi products. Cloud4Wi HTTPS implementation uses industry standard algorithms and certificates.

At-rest: Cloud4Wi stores user passwords following policies that follow industry standard practices for security. With effect 25 May 2018, Cloud4Wi has implemented technologies to ensure that stored data is encrypted at rest.

c) Input Control

Detection: Cloud4Wi designed its infrastructure to log extensive information about the system behavior, traffic received, system authentication, and other application requests. Internal systems aggregated log data and alert appropriate employees of malicious, unintended, or anomalous activities.Cloud4Wi personnel, including security, operations, and support personnel, are responsive to known incidents.

Response and tracking: Cloud4Wi maintains a record of known security incidents that includes description, dates and times of relevant activities, and incident disposition. Suspected and confirmed security incidents are investigated by security, operations, or support personnel; and appropriate resolution steps are identified and documented. For any confirmed incidents, Cloud4Wi will take appropriate steps to minimize product and Customer damage or unauthorized disclosure.

Communication: If Cloud4Wi becomes aware of unlawful access to Customer data stored within its products, Cloud4Wi will: 1) notify the affected Customers of the incident; 2) provide a description of the steps Cloud4Wi is taking to resolve the incident; and 3) provide status updates to the Customer contact, as Cloud4Wi deems necessary. Notification(s) of incidents, if any, will be delivered to one or more of the Customers contacts in a form Cloud4Wi selects, which may include via email or telephone.

d) Availability Control

Infrastructure availability: The infrastructure providers use commercially reasonable efforts to ensure a minimum of 99.95% uptime. The providers maintain a minimum of N+1 redundancy to power and network.

Fault tolerance: Backup and replication strategies are designed to ensure redundancy and fail-over protections during a significant processing failure. Customer data is backed up to multiple durable data stores and replicated across multiple availability zones.

Online replicas and backups: Where feasible, production databases are designed to replicate data between no less than 1 primary and 1 secondary database. All databases are backed up and maintained using at least industry standard methods.

Cloud4Wis products are designed to ensure redundancy and seamless failover. The server instances that support the products are also architected with a goal to prevent single points of failure. This design assists Cloud4Wi operations in maintaining and updating the product applications and backend while limiting downtime.

This section is visible to Cloud4Wi team only

This add-on is not published on the public price list.

The risks of providing wireless internet access for your clients can be mitigated by adopting Cloud4Wi Content Filtering Add-on. The solution allows you to control the content that can be accessed, creates a safe environment to access the internet, and provides your organization with reports regarding network usage which gives you the potential to tailor your services to your clients needs.

Cloud4Wi partners with WebTitan and to provide a convenient WiFi content filtering system that blocks inappropriate material and provides access to a certification symbol to show that the WiFi is safe. WebTitan, advanced web content filtering built for businesses, use the Internet Watch Foundation to block inappropriate material based on certain categories and specific web addresses.

Benefits:

Give your business and your customers peace of mind with WiFi content filtering

Automatically block URLs on the Internet Watch Foundation watchlist and promote child-friendly internet access

Optimize bandwidth usage and network management

Reduce liability (ie: if users download copyrighted content)

Access reports on top requested domains, top requested categories, most blocked domains, and most blocked categories

Block or unblock content according to category

Technical capabilities

No hardware or software installationrequired.

Fast: DNS solution provides almost zero additionallatency.

Supports both static and dynamic IPs addresses.

Protection from both HTTP and HTTPS security threats

Filters website URLs into 53 predefined categories such as social media, news, pornography, gambling etc. The system contains over 500 million website addresses in 200 languages, each sorted into the predefined categories

Create whitelists and blacklists of websites you wish to allow or block as exceptions to the general policy, for example, block all social media sites except Twitter

Web dashboardfor administrators to easily access to manage policies per network, group, user or IP address

Generate reports by category and schedule periodic reports received via email

Protect the network from malware and phishing attacks, will block access to compromised websites, malicious websites, spam based websites and spyware

How it works

Contact us

Screenshots

Interested in this add-on?

The Survey application that allows you to create beautiful surely that can be sent via email, text or presented on the Access Journey during the guest WiFi onboarding.

Survey app is available in Volare Splash and Volare Compass for the Organization Managers only. You can open the app form the Marketing panel.

Summary:

Creating a new survey

List of Surveys

Survey Reports

Publishing Surveys during the Access Journey

Creating a new survey

In order to add a new survey, click the Add button on the top of the screen.

The set up your survey you have to configure the data in the following tabs:

Configure

Build

In the Configure tab, you have to enter some text values in your favorite language, such as:

Survey Name (required)

Introduction (optional)

Thanks text (optional)

Button label: Next Step

Button label: Submit survey

Button label: Skip survey

Button label: Already answered

Button label: Start message

In the Build tab, you can create your questions. The following types are available:

Text

Multi Choice

Yes / No

Rating

Form

Please find below all the details for each type.

Text

You can add a Text question if you want to ask an open-ended question.

It is possible to configure the following fields:

Question: the text of your question

Description: a small description or comment for the question

Max Answer Length: how many characters are allowed for answers

Required: whether it is mandatory for the end-user to give an answer

Multi Choice

You can add a Multi Choice question if you want your end-users to select one or more answers from a list.

It is possible to configure the following fields:

Question: the text of your question

Description: a small description or comment for the question

Required: whether it is mandatory for the end-user to give an answer

Answers As Dropdown/As list: if you want your answers to be presented as a drop-down menu or as simple text

By clicking Add Answer you can add your options.

Yes / No

You can add a Yes / No question if you want to ask a close-ended question ("Yes" or "No" are the only possible options).

It is possible to configure the following fields:

Question: the text of your question

Description: a small description or comment for the question

Yes label: write "Yes" in your favorite language or in the form you prefer

No label: write "No" in your favorite language or in the form you prefer

Required: whether it is mandatory for the end-user to give an answer

Rating

You can add a Rating question if you want your end-users to rate an item on a rating scale of 1-5.

It is possible to configure the following fields:

Question: the text of your question

Description: a small description or comment for the question

Required: whether it is mandatory for the end-user to give an answer

Style: you can choose to display Faces, Stars or Numbers

Form

You can add a Form question if you want your end-users to provide their personal data.

It is possible to configure the following fields:

Question: the text of your question

Description: a small description or comment for the question

Required: whether it is mandatory for the end-user to give an answer

Override: whether the information provided by the end-user has to replace previously existing values. Please read more details at the end of this paragraph.

You can ask your end-users to provide the user fields below:

First name

Last name

Email

Document type

Document number

Gender

Birth date

For each field configured you can define the related label in your favorite language.

About the Override option, please consider the cases below:

if the Override option is disabled and the end-user is authenticated, then:

the user data that are already stored in Cloud4Wi will not be displayed

the user data that are not stored will be displayed, but the user's answer will not replace any already existing value

if the Override option is enabled and the end-user is authenticated, then:

all the user data will be displayed, and answers of the end-users will replace already existing values

if the end-user is not logged in, then the Override option has no effect.

List of surveys

On the main page of the application, you can see all available surveys.

For each survey, the available information is:

Title: the survey name. If the survey is not Published, then you can click and change the details

Status: can be Published (enabled on your Splash Page) or Draft (disabled)

Created: the creation date

Code: a unique code automatically assigned to your survey

Public Url: if the "public access" is enabled, then you can publish the survey at the displayed URL without being connected to an access point

# Questions: the number of questions the survey consists of

# Answers: how many end-users gave answers to the survey. By clicking on this value you can see the detailed statistics for the selected survey.

Actions: the possible actions for each survey that are:

Publish survey () or Deactivate survey (): enable or disable the access to the survey from the Splash Page. It is allowed to publish only one survey per organization instance.

Deny public access () or Allow public access (): enable or disable the access to the survey from the Internet (without being connected to an access point)

Edit survey (): make changes to your survey. This action is allowed only if the access from the Splash Page is disabled (you cannot edit an active survey)

Delete survey (): delete your survey. This action is allowed only if the access from the Splash Page is disabled (you cannot delete an active survey)

Survey reports

By clicking the # Answers value for each survey, you can see the related statistics.In the Report tab, you can see a statistics dashboard, where user answers are summarized in some charts.

In the Result tab, you can see all the answers given by the end-users, one by one. It is possible to export this report to a CSV file.

Publishing Surveys during the Access Journey

To publish a survey campaign in the Access Journey, you need to click on the button "Apply to" in the list of surveys.

A window pops up that allows deciding in which locations to publish the Survey.

In order to publish the Survey, you also need to enable the Survey content in the Access Journey. To create an interstitial experience, the best step where to publish the Survey is on the Login Attempt.

Introduction

The Presence and Location integration is available for the following Extreme Wireless Controller devices:

V2110 Controller

Wireless Controllers

Minimum Firmware version:10.41.18.XXXX

Configuration

Log in to your ExtremeCloudAppliance account.

Click on(Settings) in the left toolbar, go to the Third Party Configurationpage and configurethe input fields as below:

Subscriber Push URL: https://presence.cloud4wi.com/cloud4wi-presence/rest/extreme

Events: Presence, Location, RSSI

Cloud4Wi allows you to verify email addresses provided by end-users during the registration process. You can access this feature by opening Guest Wi-Fi Setup Login Profiles, then selecting your login profile. In the Advanced tab, select "Email" as the Account validation mode.

This feature is supported when the following Sign-up options are selected: User Account and Click-through.

If you have set the email verification into the Cloud4Wi Dashboard, then each end-user who registers (except for users who choose Social Login) will be asked to enter their email address, regardless of the other options set in the login profile.

After the registration, the Splash Portal shows a confirmation screen. Here, the end-user can confirm the email address, or change it if he has made some mistakes.

After that, Cloud4Wi sends an email to the end-user asking him to open a verification URL containing a link. The end-user can click on it and get full access to the Internet.

Service limitations for "unverified" accounts

For unverified accounts, it is not possible to surf the Internet for more than 5 minutes per session. Please note the different examples:

If the Internet plan allocated to the end-user allows him to surf for more than 5 minutes, then the user will be disconnected after 5 minutes. Afterward, the end-user is still able to reconnect to the Internet, and the period of the new session depends on the remaining minutes of the Internet plan.

If the Internet plan allows the end-user to surf fewer than 5 minutes, then no restrictions are applied.

If the account is not associated with any Internet plan, then the end-user is not able to connect to the Internet.

Furthermore, the following cases happen for "unverified" accounts:

Every time an "unverified" account user goes online, the Splash Portal shows an alert and Cloud4Wi again sends the email confirmation to the end-user. That happens until the account is verified.

If Click-through is enabled, the Splash Page asks the end-user to provide his email address, until he completes the verification process.

Manual verification by the system user

A system manager (Organization or Location Manager) can manually verify an account from the Cloud4Wi Dashboard, by clicking on the People button in the quick access toolbar on the left, searching for the end-user account, opening it and clicking on the "Confirm" link next to Confirm registration email. If you cannot find this link, it means that the account does not need to be verified.

By configuring the Login profiles section, you can define the login flow for your end-users and set all the available options on the Splash Page. A Login profile is an entity containing all these options.

Once you have a Login profile, you can assign it to a location (through the Locations section, by clicking on the left sidebar at Manage Login Profiles) and enable there all the desired options.Your location will be pre-configured with two login profiles (called "Click-through access" and "Username and password"). You can edit any existing Login profile or create a new one.

For any option you can set the ownership:

If you're going to apply this setting for all your locations, then you have to set the lock option: Sponsor validation

If you want to let your location able to change your value, then you have to set the unlock option:

The Login profile section consists of two tabs: Login options and Advanced.

Login options

This tab contains the most common login options to be used and consists of the following sub-sections:

Primary Sign-Up

Social Login

One Time Password Login (you'll see this option when Kiosk is enabled and installed in your organization instance)

PRIMARY SIGN-UP

The first thing to think about is: how do you want your users to sign up for the service?By configuring the Sign-up option, you can set the decide between the following options:

Username/Password: this option enables the classic user registration form where end-users need to register and receive a username and password.

Click-through: this option enables the click-through mode, where end-user need to provide the information requested by the organization or location manager. In this mode, the registration form, self-care page, and password recovery page are not displayed on the Splash Page.

None: none of the registration methods above are selected.

Note: This option does not include Social Login. You can enable the Social Login flow by the corresponding sub-section called Social Login.

Depending on what you configured in these sections, there may be other options to configure.If you configured Username/Password, then the following options are available:

Username: by selecting this option you can determine how the system builds a username for a registered end-user. Options include:

Mobile number: the username for the end-user is the mobile phone number provided during registration. If the phone number does not belong to any registered end-users, the username will be the phone number. Otherwise, if it already belongs to a registered end-user, and if the Multiple registrations of the same mobile number option is enabled, the username will consist of the provided phone number + a numeric suffix.

Customer name: the username for the end-user is based on the first name and the last name provided. More precisely, the username will consist of: the first 6 letters of the first name (or the whole first name if it is 6 letters or less) + the "." character + the first 6 letters of the last name (or the whole last name if it 6 letters or less) + a progressive number used in order to avoid duplicate usernames(e.g. John Doe john.doe1 ; Alexander Smithee alexan.smithe1)

Generated by the system: the username for the end-user is a random alphanumeric string chosen by the system.

Email: the username is the email address of the end-user.

Allow sign-up from the Splash Page: by selecting this option, it is possible to establish whether an end-user can register through the Splash Page. Possible values for this option are:

Yes: the end-user can register directly through the Splash Page (autonomous registration).

No: the end-user should go to the Location Manager in person and ask for personal access credentials.

Registration fields: by selecting this option, it is possible to specify fields that will be requested from end-users in the registration form. If no fields are specified, the default registration fields will be prompted to end-users. It is possible to enable the following fields:

First name

Last name

Title

Email

Birthday

Gender

Phone number

Personal ID

Personal ID (Brazil)

Passport number

Country

Mandatory registration fields: by selecting this option, you can specify which of the Registration fields specified (in the previous option) are mandatory. If you leave this empty, any field displayed to end-users is intended as optional. You can also decide to make mandatory "Email or phone".

Allow multiple accounts with the same phone number: by selecting this option, it is possible to determine if the system can accept two or more end-users with the same mobile number within the location. Possible values for this option are:

Yes: multiple registrations with the same phone number are allowed. In this case, if Username type is set to Mobile Phone, the username will consist of the provided phone number + a numeric suffix.

No: multiple registrations with the same phone number are not allowed. If the phone number provided is already used in the location, then the end-user receives an error until another mobile number is entered.

Allow multiple accounts with the same email: by selecting this option, you can determine if the system can accept two or more end-users with the same email address within the location. Possible values for this option are:

Yes: multiple registrations with the same email address are allowed. In this case, if Username type is set to Email, the username will consist of the provided email address + a numeric suffix. For example: [email protected]

No: multiple registrations with the email address are not allowed. If the email address provided is already used in the Location, then the end-user receives an error until another email address is entered.

Show sign-up summary screen: by selecting this option, you will enable a summary screen that is shown to any end-user as soon as the sign-up form is submitted without validation errors. Here the end-user is able to check if the data are correct and decide whether to go online or go back to the sign-up form. Possible values for this option are:

Yes: this screen is shown

No: this screen is not shown and the end-user will go directly online after signing up

Enable self-care portal: by selecting this option, you can enable the My profile section for the Splash Page. If enabled, end-users can display and update their personal data, unregister from the service, check for active internet plans, and check the list of traffic sessions in the past. This option is not available if the Sign-up method is set to "Click-through". Possible values are:

Yes: the My profile section is available to end-users.

No: the My profile section is not available to end-users.

Allow password recovery from Splash Page: by selecting this option, it is possible to choose whether the password recovery is allowed for end-users or not. This is not available if the Sign-up method is set to "Click-through". Possible values are:

Yes: end-users are able to recover passwords to access the service by clicking on the appropriate link within the Splash Page.

No: end-users cannot automatically recover passwords and must go to the location manager in person to obtain credentials.

If you configured Click-Through, then the following options are available:

Registration fields: by configuring this option, it is possible to require the end-user to enter some personal data, such as:

First name

Last name

Title

Email

Birthday

Gender

Phone number

Personal ID

Personal ID (Brazil)

Passport number

Country

Mandatory registration fields: by selecting this option, you can specify which of the Registration fields specified (in the previous option) are mandatory. If you leave this empty, any field displayed to end-users is intended as optional.

If you configured None, then no further options are available

SOCIAL LOGIN

This sub-section allows you to enable the Social Login flow on your location. To do that, just set Enable: Yes.Once Social Login is enabled, you can choose to enable the integration with the following social network providers:

Facebook

LinkedIn

Twitter

Google+

Gmail

VKontakte

Instagram

Foursquare

Pinterest

Registration fields: by configuring this option, the user will be asked to enter the following information if it is not returned by the social network provider.

First name

Last name

Title

Email

Birthday

Gender

Phone number

Personal ID

Personal ID (Brazil)

Passport number

Country

Mandatory registration fields: by selecting this option, you can specify which of the Registration fields specified (in the previous option) are mandatory. If you leave this empty, any field displayed to end-users is intended as optional.

ONE TIME PASSWORD LOGIN

If Kiosk is enabled on your organization instance, then you will see this sub-section. From here you can enable your Splash Page to accept-one time passwords designed for Kiosk.To enable the One-time password login, just set Status: Enabled.

Advanced

This section contains more advanced login option and consists of the following sub-sections:

Policies

Access control

Communications

Success page

POLICIES

In this sub-section, you can set every option regarding any policy that the user may/has to accept in order to get Internet access.

Acceptance of Terms of Use and Privacy Policy: By configuring this option, it is possible to set the following modes of policy acceptance:

Explicit: the end-user has to check Terms of Use and Privacy Policy before clicking the button to go online. If it does not happen, then the end-user gets an error

Implicit: when the end-user clicks the button to go online, then it is intended that he accepted Terms of Use and Privacy Policy and no checkboxes for this will be shown to the end-user. A specific statement on the Splash Page describes this behavior without any ambiguity.

Terms of use and Privacy Policies: By configuring this option, it is possible to set the following modes of policy acceptance:

Unified in single clause: the end-user will get a unique acceptance statement for Terms of Use and Privacy Policy.

Implicit: the end-user will get two separate acceptance statements, one for Terms of Use and one for Privacy Policy.

Terms of Use: By configuring this option, it is possible to customize the Terms of Use clauses as described below:

Default text: the Terms of Use of the service are the default one provided by Cloud4Wi

Custom text: the end-user is able to customize in the Terms of Use for the service, in all the provided languages.

In case of Custom text you are required to enter a Version of your clause.You can also check Ask your existing users to accept the new policy version again in order to ask your users to re-accept the Terms of use if the last version accepted is different from the one set in the Login Profile.As this option affects the user experience, please use it only if you are aware of what you're doing. You can find more information here. If in doubt, do not hesitate to contact our Support Team.

Privacy Policy: By configuring this option, it is possible to customize the clauses of the Terms of Use as described below:

Default text: the Terms of Use of the service are the default one provided by Cloud4Wi

Custom text: the end-user is able to customize in the Terms of Use for the service, in all the provided languages.

In case of Custom text you are required to enter a Version of your clause.You can also check Ask your existing users to accept the new policy version again in order to ask your users to re-accept the Privacy Policy if the last version accepted is different from the one set in the Login Profile.As this option affects the user experience, please use this option only if you are aware of what you're doing. You can find more information here. If in doubt, do not hesitate to contact our Support Team.

Pre-check Terms of Use and Privacy Policy: By checking this option, Terms of Use and Privacy Policy will be checked by default on the Splash Page.

Promotional Communication Policy: by selecting this option, you can ask end-users to agree to receive marketing communications from the service provider. You can send communications using the following applications: Emails and Triggered Campaigns. Possible values are:

No: end-users will not be asked to receive any marketing communications. End-userswon'tbe able to accept or decline marketing communications and will not receive them at all.

Opt-in to receive promotional communications: end-users will be asked to click on the checkbox if he or she wants to receive marketing communications.

Opt-out of receiving promotional communications: end-users have a choice not to click on the checkbox if he or she does not want to receive marketing communications.If Opt-in or Opt-out are enabled, then it is also possible to choose between displaying the default text or a custom one for any supported language.

Pre-check Promotional Communication Policy: this is displayed only if Promotional Communication Policy is set to "Opt-in to receive promotional communications". If you check this option, then the marketing clause will appear checked by default on the Splash Page. Otherwise, it will not be checked.

Minimum Age Verification: by enabling this option you can ask your end-users to confirm to be older than a certain age. You can use this option to restrict your service based on the age of your end-users. You are required to enter a Version of your age verification clause.You can also check Ask your existing users to accept the new policy version again in order to ask your users to re-accept the age verification clause if the last version accepted is different from the one set in the Login Profile.As this option affects the user experience, please use this option only if you are aware of what you're doing. You can find more information here. If in doubt, do not hesitate to contact our Support Team.

Custom Opt-in: this option allows you to define custom opt-in clauses that you can submit to your end-users, without any obligation of acceptance for them. When the end-user accepts one or some clauses, this information will be stored in the platform and displayed in the end-users' CSV file that you can export from the People section.You can define up to 5 opt-in clauses simultaneously, and for each clause you have to provide:

Terms name: an alphanumeric value (only [0-9][a-z][A-Z] accepted) that is used for inventory purposes and displayed only in the end-users' CSV file (it won't be shown to your end-users)

Version:

Text: you can define the text that will be displayed next to your checkboxes, for each language you set on the Splash page.

Required: you can choose to make the acceptance mandatory for the end-user.

You can also check Ask your existing users to accept the new policy version again in order to ask your users to re-accept your custom clause if the last version accepted is different from the one set in the Login Profile.As this option affects the user experience, please use this option only if you are aware of what you're doing. You can find more information here. If in doubt, do not hesitate to contact our Support Team.

ACCESS CONTROL

This sub-section allows enabling all the features connected with access control.

Smart Authentication: this is a type of MAC authentication that ties devices to user accounts and on the second login automatically makes the authentication on behalf of users when they open the Splash Page. If the Smart Authentication is enabled and the user previously had signed in by using the same device, then he will be automatically signed in when opening of the Splash Page, without any need of manual authentication.

Primary Sign-Up Validation: by selecting this option, it is possible to add a validation step during the registration of end-users. Possible values are:

None: no validation step required

Password via text message: the password is sent to the phone number provided by the end-user (available only for "Username/Password").

Inbound text/call: the end-user is required to call or send a text message to a specified phone number in order to receive the username and the password (available only for "Username/Password").This option enables: Enable inbound call, Enable inbound text messages (separate options to enable inbound texts, or calls, or both)

Email: a verification email is sent to the email address provided by the end-user. The user is required to check his mailbox and click on a link to unlock his account (available for "Username/Password" and "Click-Through"). Please find here an example of how it works: Set up Click-through with email verification.

Validation code via text message: the end-user receives a text message containing the username and the verification code. The end-user has to enter the verification code to get the access (available for "Username/Password" and "Click-Through")

Social Login Validation: by selecting this option, it is possible to add a validation step when the end-user signs up through Social Login. Possible values are:

Validation code via text message: the end-user receives a text message containing the username and the verification code. The end-user has to enter the verification code to get access.

Send a text or call: the end-user is required to call or send a text message to a specified phone number in order to receive username and password

None: no validation step required

Require access code for foreign users: by selecting this option you can require any end-user providing a foreign mobile country code (different than the default one set in the Preferences) to enter an identification code in order to get the access. Possible values are:

Yes: foreign end-users are asked to enter the code

No: this validation step is not required

Shared password: by selecting this option, it is possible to ask the end-user to enter a shared password after any successful authentication, in order to get the access. Possible values are:

Yes: shared password is required

No: this validation step is not required

Sponsor validation: by selecting this option you enabled the that let an end-user to get the access only after having been enabled by qualified people (called "sponsor"). Possible values are:

None: the Sponsor validation is disabled

Multi Sponsor: Sponsor validation is enabled for some domains that you have to enter in the provided input field, separated by commas

Single Sponsor: Sponsor validation is enabled. Only one email address is allowed to act as the sponsor, and you have to enter it in the provided input field

Please note that enabling Sponsor Validation will disable the following options: Primary Sign-Up Validation, Social Login Validation, Require access code for foreign users, Shared password.

COMMUNICATIONS

This sub-section allows enabling the Splash Page to send e-mails to the end-user on sign-up/sign in.

Send welcome email at sign-up: by selecting this option, the Splash Page sends an e-mail on end-users' sign-up. Possible values are:

Yes: the platform sends a welcome email on the sign-up of the user

No: no welcome email is sent on the sign-up of the user

Send welcome email at sign-in: by selecting this option, the Splash Page sends an e-mail on end-users' sign-in. Possible values are:

Yes: the platform sends a welcome email on user's sign-in

No: no welcome email is sent on user's sign-in

SUCCESS PAGE

This sub-section allows enabling some behaviors after the end-user has successfully got the access.-

Show log out button: by selecting this option, you can enable the "Logout" buttons and links on the Splash Page. Possible values are:

Yes: "Logout" buttons and links are displayed

No: "Logout" buttons and links are not displayed

Please note that in the cases below this option will be hidden and no logout button will be displayed on the Splash Page:

You enabled the Smart Authentication

Your access point does not support "logout" from the web interface.

Display welcome box on landing page: by selecting this option, it is possible to show the welcome box after end-user authentication. The possible values for this option are:

Yes: the welcome box is displayed.

No: the welcome box is not displayed.

Enabling location services

The first step to getting your Cisco Meraki network feeding data to Cloud4Wi is to enable the location services on the Meraki dashboard. With this step, your Cisco Meraki network will start sending presence and location data to Cloud4Wi, and the Overview, Trends, Peak and Virtual Zone dashboard will start working automatically.

1. Accessing the web interface

Login to the Meraki Dashboard with your credentials andselect your organization and the network where you want to enable the service on.

2. Enabling the Meraki CMX and the communication with APIs

Go to the Network-wide >Configure page form the left sidebar.

https://cloud4wi.zendesk.com/hc/en-us/articles/208154933-Adding-and-managing-floors

Scroll down until you find the Location and scanningsection and set Scanning API value to "Scanning API enabled". if you don't see this section, contact the network administrator as you might not have the permission to change these settings

Copy the Validator string and send it to the Cloud4Wi support team opening a Ticket. Cloud4Wi will provide you the data to be entered into the interface:

Post URL

Secret

Once received the data, click "Add a Post URL" and enter the two values above:

Click the "Validate" button. If you receive a confirmation message, everything has been configured correctly. If you don't receive the successmessage, please check if the data is correctly entered. Alternatively, you can open a ticket in our Support Center.

Enabling Heatmap and Polygon Zones

To get your Heatmap dashboard working and to start using the Polygon Zones, you need to take a further step. In order for these features to work, you need to sync the floor plans you have configured in your Meraki dashboard with the floor plans in your Cloud4Wi account.

1. Configuration on Meraki

The initial step is to upload a floor plan (.png or .jpeg files only) onto the Meraki dashboard and then place APs on this floor plan. You need to make sure that all the APs have been placed on the floor plan and there are no APs remaining under unplaced option. See below sample screenshot.

Also, take note of the Network name as this will be needed when configuring on Cloud4Wi. Visit Meraki support for more information in regards to adding floorplan ( https://documentation.meraki.com/MR/Monitoring_and_Reporting/Using_a_Floor_Plan_or_Custom_Map_in_Dashboard ).

2. Configuration on Cloud4Wi

The first step is to upload the same floorplan used on Meraki dashboard under the location where Heatmaps data is to be captured. The important field when creating a new floorplan is Floor hardware manufacture ID: this field should be the same as the floor plan name (its case sensitive) used on Meraki dashboard.

Please read the following article about how to Add and Manage floorplan () on Cloud4Wi.

Once the configuration upload has been completed, the access point will be able to capture location data and feed it to the Cloud4Wi service. At this point, your Heatmap dashboard will start showing the data (it may take a few hours before you see data showing on the map).

You can also start using the Polygon Zones by drawing polygons on the floor plans and analyzing the zone traffic on the related Zone Traffic dashboard.

Purpose

This guide shows how to configure a Huawei device with the following AP models running firmware FitAP_Model_V200R006C10SPC800:

AP6010SN-GN

AP6010DN-AGN

AP6310SN-GN

AP6510DN-AGN

AP6610DN-AGN

AP7110SN-GN

AP7110DN-AGN

AP5010SN-GN

AP5010DN-AGN

AP3010DN-AGN

AP6510DN-AGN-US

AP6610DN-AGN-US

AP5030DN

AP5130DN

AP7030DE

AP2010DN

AP8130DN

AP8030DN

AP9330DN

AP4030DN

AP4130DN

AP3030DN

AP2030DN

AP9131DN

AP9132DN

AP5030DN-S

AP3010DN-V2

Please note that the images contained in this article may have outdated configuration data. Please check the data in the article "Parameters for the Solution" at the bottom of the page, as that information is up to date.

Prerequisites

The configuration procedure has been performed and tested on Huawei Access Controller AC6005-8-PWR running firmware VRP (R) software, Version 5.130 (AC6005 V200R006C10) and Access Point AP5030DN running firmware FitAP5X30XN_V200R006C10SPC800.

Before integrating the Access Controller with Volare, it is necessary that it is connected to the Internet and reachable on the network and has open the UDP port 2000.

This guide will refer to the Access Controller AC6005 and the network architecture in the picture below.In this case:

Network 1 includes the Access Controller

Network 2 includes the Access Points, any switch or any client

https://splashportal.cloud4wi.com For all other network topologies. please contact Huawei support or read through the Huawei documentation available their site: http://support.huawei.com/.

Accessing the device

By default, the Access Controller has the following IP address: 169.254.1.1. You can manage and configure the AC by Telnet or by opening a web browser, visiting the following URL: http://169.254.1.1 and logging in as the admin user with a default password [email protected]. This guide will drive the configuration based on CLI.

Network 1 (AC)

Ethernet interfaces and VLANs

Configure a Service VLAN and the CapWap source IP address (in this example is the IP address configured in Vlan150) on the GigabitEthernet interface attached to your default gateway (GigabitEthernet0/0/1).

Configure a management VLAN. (Management of APs - Vlan30).

Configure the CapWap source to your public IP address of the AC 6005.

Configure a tagged VLAN. (Service for the STAs - Vlan200)

In Telnet session, we start to configure the VLAN interface GigabitEthernet 0/0/1 as following:

<AC-6005>system-view

Enter system view, return user view with Ctrl+Z.

# Change the system name to the public IP address of the AC 6005. This is a mandatory step and the name of the controller needs to be its public IP address. If AC controller uses private IP address, then you need to provide public IP address after NATting.

[AC-6005]sysname 151.0.208.150

# VLAN / Capwap source (public IP address of the AC 6005)

[151.0.208.150]interface vlanif 150

[151.0.208.150-Vlanif150]description public-ip-AC

[151.0.208.150-Vlanif150]ip address 151.0.208.150 29

[151.0.208.150-Vlanif150]quit

# Service VLAN with the address pool of the STAs (Client devices will connect to AP)

[151.0.208.150]interface vlanif 200

[151.0.208.150-Vlanif200]description service-VLAN

[151.0.208.150-Vlanif200]ip address 192.168.50.1 24

[151.0.208.150-Vlanif200]quit

# Management VLAN (IP pool for APs)

[151.0.208.150]interface vlanif 30

[151.0.208.150-Vlanif30]description Management-VLAN

[151.0.208.150-Vlanif30]ip address 192.168.30.1 24

[151.0.208.150-Vlanif30]quit

# Associate the VLAN created to interface GigabitEthernet 0/0/1

[151.0.208.150]interface GigabitEthernet0/0/1

[151.0.208.150-GigabitEthernet0/0/1]port hybrid pvid vlan 150

[151.0.208.150-GigabitEthernet0/0/1]port hybrid tagged vlan 200

[151.0.208.150-GigabitEthernet0/0/1]port hybrid untagged vlan 30 150

[151.0.208.150-GigabitEthernet0/0/1]quit

[151.0.208.150]vlan batch 30, 150, 200

# Capwap source is the public IP address of the AC

[151.0.208.150]capwap source ip-address 151.0.208.150

# Add the default gateway of the AC. In this case 151.0.208.145

[151.0.208.150]ip route-static 0.0.0.0 0.0.0.0 151.0.208.145

[151.0.208.150]quit

<151.0.208.150>save

# Verify the portal version of the AC

[151.0.208.150]undo web-auth-server version

The Portal version on the AC should be set to Ver 1. If the AC is running on different version then you can execute the following command.

Configuring ACL and free-rules (Walled garden)

Security consideration. To permit the connections between the Portal Server and the Access Controller, it's necessary the AC is reachable from the Internet and have open the UDP port 2000 (check your firewall configuration guide).

# Free domains

[151.0.208.150]passthrough-domain name *.cloud4wi.com id 1

# Example to configure free domains for facebook login

[151.0.208.150]passthrough-domain name *.facebook.com id 2

[151.0.208.150]passthrough-domain name *.facebook.net id 3

[151.0.208.150]passthrough-domain name *.akamaihd.net id 4

[151.0.208.150]passthrough-domain name *.fcbn.net id 5

# ACL

[151.0.208.150]acl number 6000

[151.0.208.150]rule 4 permit ip destination 8.8.8.8 0

[151.0.208.150]rule 5 permit udp source 0.0.0.0 0 destination-port eq dns

# RADIUS server

[151.0.208.150]rule 6 permit ip destination 54.247.117.188 0

[151.0.208.150]rule 39 permit tcp destination passthrough-domain *.cloud4wi.com

[151.0.208.150]rule 40 permit tcp destination passthrough-domain *.facebook.com

[151.0.208.150]rule 41 permit tcp destination passthrough-domain *.facebook.net

[151.0.208.150]rule 42 permit tcp destination passthrough-domain *.fbcdn.net

# Create a free rule template

[151.0.208.150]free-rule-template name free1

[151.0.208.150-free-rule-free1]free-rule acl 6000

To configure the walled garden, please check the following articles:

Walled garden for the Social Login (websites/domains to open)

Walled garden for PayPal feature (websites/domains to open)

Configuring RADIUS server template

[151.0.208.150]radius-server template radius

# Cloud4Wi RADIUS server IP: 54.247.117.188 authentication port: 1812, accounting port:1813

[151.0.208.150-radius]radius-server shared-key cipher secret provided by cloud4wi

[151.0.208.150-radius]radius-server authentication 54.247.117.188 1812

[151.0.208.150-radius]radius-server accounting 54.247.117.188 1813

[151.0.208.150-radius]radius-server user-name domain-included

[151.0.208.150-radius]quit

[151.0.208.150]aaa

[151.0.208.150-aaa]authentication-scheme radius

[151.0.208.150-aaa-authen-radius]authentication-mode radius

[151.0.208.150-aaa-authen-radius]quit

[151.0.208.150-aaa]authorization-scheme radius

[151.0.208.150-aaa-author-radius]authorization-mode if-authenticated

[151.0.208.150-aaa-author-radius]quit

[151.0.208.150-aaa]accounting-scheme radius

[151.0.208.150-aaa-accounting-radius]accounting-mode radius

[151.0.208.150-aaa-accounting-radius]accounting realtime 900

[151.0.208.150-aaa-accounting-radius]quit

[151.0.208.150-aaa]domain d1

[151.0.208.150-aaa-domain-d1]authentication-scheme radius

[151.0.208.150-aaa-domain-d1]authorization-scheme radius

[151.0.208.150-aaa-domain-d1]accounting-scheme radius

[151.0.208.150-aaa-domain-d1]radius-server radius

Configuring URL template and authentication profile

[151.0.208.150]url-template name u1

[151.0.208.150-url-template-u1]url https://splashportal.cloud4wi.com

# Uam parameters

[151.0.208.150-url-template-u1]url-parameter user-ipaddress wlanuserip ac-ip wlanacip ac-mac wlanacmac ap-ip wlanapip ap-mac wlanapmac redirect-url wlanuserfirsturl ssid ssid sysname wlanacname user-mac wlanusermac

[151.0.208.150-url-template-u1]quit

[151.0.208.150]web-auth-server web

[151.0.208.150-web-auth-server-web]server-ip 54.247.117.188 (Cloud4wi splash portal ip)

[151.0.208.150-web-auth-server-web]port 50100 (default port communication between AC-Portal)

[151.0.208.150-web-auth-server-web]url-template u1

[151.0.208.150-web-auth-server-web]source-ip 151.0.208.150

[151.0.208.150-web-auth-server-web]quit

[151.0.208.150]portal-access-profile name portal

[151.0.208.150-portal-access-profile-portal]web-auth-server web direct

[151.0.208.150-portal-access-profile-portal]quit

[151.0.208.150]authentication-profile name portal

[151.0.208.150-authentication-profile-portal]portal-access-profile portal

[151.0.208.150-authentication-profile-portal]free-rule-template free1

[151.0.208.150-authentication-profile-portal]access-domain d1

[151.0.208.150-authentication-profile-portal]authentication roam-accounting

[151.0.208.150-authentication-profile-portal]update-session-mode

[151.0.208.150-authentication-profile-portal]authentication-scheme radius

[151.0.208.150-authentication-profile-portal]accounting-scheme radius

[151.0.208.150-authentication-profile-portal]authorization-scheme radius

[151.0.208.150-authentication-profile-portal]radius-server radius

Configuring WLAN, SSID profile, and VAP profile

# Create SSID Profile

[151.0.208.150]wlan

[151.0.208.150-wlan-view]ssid-profile name C4W-huawei

[151.0.208.150-C4W-huawei]ssid name_of_ssid

[151.0.208.150-C4W-huawei]quit

# Create VAP Profile and associate it with authentication profile

[151.0.208.150-wlan-view]vap-profile name C4W-huawei

[151.0.208.150-wlan-vap-prof-C4W-huawei]service-vlan vlan-id 200

[151.0.208.150-wlan-vap-prof-C4W-huawei]ssid-profile C4W-huawei

[151.0.208.150-wlan-vap-prof-C4W-huawei]security-profile C4W-huawei

[151.0.208.150-wlan-vap-prof-C4W-huawei]authentication-profile portal

Configuring AP group and setting the radio profile to vap-profile

The following schema defines the functional priorities of the operations necessary to configure AP groups, radio profile, and vap-profile.

# Create a new ap-group

[151.0.208.150-wlan-view]ap-group name default

[151.0.208.150-wlan-ap-group-default]vap-profile C4W-huawei wlan id_wlan radio all

# Change the AP update mode to ac-mode

[151.0.208.150-wlan-view]ap update mode ac-mode

[151.0.208.150-wlan-view]ap auth-mode no-auth

Creating a QoS profile and associate it to a user-group

For example, we'll configure a QoS profile to limit the bandwidth in Uplink and Downlink to 1Mb/s for a specific user group (group-1M).

The User-group name will represent the Filter-Id (In this case group-1M) to configure on Volare platform. For further details, check the link: https://cloud4wi.zendesk.com/hc/en-us/articles/208554056-Setting-QoS-parameters-on-Internet-plans.

# Create a new QoS profile (example to limit a bandwidth in Uplink and downlink to 1 Mb/s)

[151.0.208.150]qos-profile name limit-1M

[151.0.208.150-qosprofile-limit-1M]car inbound cir 1024

[151.0.208.150-qosprofile-limit-1M]car outbound cir 1024

[151.0.208.150-qosprofile-limit-1M]quit

# Create a new User-Group and associate it with qos-profile

[151.0.208.150]user-group group-1M

[151.0.208.150]qos-profile limit-1M

Entering the device details into the Admin Panel

For Huawei devices, the Volare platform requires only the MAC address. The Identifier field is not required.

Network 2 (APs and STAs)

Its mandatory to configure the following VLAN on a local switch:

The service VLAN with the same ID as the previously configured on the AC (Vlan200) with a DHCP server for the STAs (customer devices) will connect through the SSID. In this case, the address pool will be 192.168.50.1/24.

The Management VLAN for the APs with the same ID and pool as the previously configured on the AC (Vlan30) with a DHCP server for the APs. In this case, the pool will be 192.168.30.1/24.

We have 2 possibilities to configure the CapWap source IP address on APs.

Recommended for a small number of APsEnter for each AP via telnet or ssh with the default credentials admin/[email protected] this example AC_ip_address = 151.0.208.150 (Capwap source IP address)

[fce3-3ca3-c820]ap-address static ac-list AC_ip_address

Info: The configuration takes effect after the AP is restarted.

[fce3-3ca3-c820]reboot

Recommended for a large number of APsIn the DHCP server for management APs configure an option-43 with sub-option 2 ip-address AC_ip_address. In this specific example, we have option 43 sub-option 2 ip-address 151.0.208.150

Parameters for the Solution

Network 1 (Access Controller)

The system name of the AC has to set to a public IP address.

Configure a service VLAN in tagged mode (Vlan200).

Configure a management VLAN (to manage the APs) (Vlan30).

Capwap source IP address has to be set to AC IP address.

Configure ACL to permit navigation to *.cloud4wi.com domain and Cloud4Wi RADIUS IP address.

RADIUS server primary(Authentication) 54.247.117.188 on port 1812 secret provided by Cloud4Wi.

RADIUS server primary(Accounting) 54.247.117.188 on port 1813 secret provided by Cloud4Wi.

RADIUS server secondary(Authentication) 79.125.111.180 on port 1812 secret provided by Cloud4Wi.

RADIUS server primary(Accounting) 79.125.111.180 on port 1813 secret provided by Cloud4Wi.

Configure the RADIUS server template:

radius-server shared-key cipher secret provided by cloud4wi

radius-server authentication 54.247.117.188 1812

radius-server accounting 54.247.117.188 1813

Set URL to Cloud4Wi Splash portal

url

url-parameter user-ipaddress wlanuserip user-mac wlanusermac ac-ip wlanapip sysname wlanacname ap-mac wlanapmac ssid redirect-url wlanuserfirsturl

Set web auth-server to IP address of Splash Portal IP address:

server-ip 54.247.117.188 (Cloud4wi splash portal ip)

port 50100 (default port communication between AC and Portal)

url-template u1

source-ip 151.0.208.150 (ip address of the AC)

Configure an authentication profile

authentication-profile name portal

Configure a VAP profile and associate it with WLAN and SSID profile.

vap-profile name C4W-huawei

service-vlan vlan-id 200

ssid-profile C4W-huawei

security-profile C4W-huawei

authentication-profile portal

Create an AP group and associate it with the VAP profile previously created.en

Network 2 (Switch, APs, and STAs)

On the switch, create one service VLAN with the same ID configured on AC in tagged mode(Vlan200) and one for the AP management with the same ID and pool configured on the AC (Vlan30)

Create one DHCP server for the STAs and one for the APs (eventually with the option 43 sub option 2) recommended for large networks.

Purpose

This guide shows how to configure a Fortinet Access Controller.

Please note that the images contained in this article may contain outdated configuration data. Therefore, please check the data contained in the article "Parameters for the Solution" at the bottom of the page, as they are certainly up to date.

Prerequisites

The configuration procedure has been performed and tested on FortiNet FortiWiFi 60D Access Controller running firmware FGT_60D-v5-build1117 and Access Point FAP-221B running firmware FAP_221B-v5-build0354.

This guide will apply to the Access Controllers, Access Points and firmware version mentioned above. Later firmware versions should also work. Other configurations have not been tested yet and currently, wedon'tknow if they're supported by Cloud4Wi or not.

Before integrating the controller with Cloud4Wi, please make sure that the Access Controller is connected to the Internet and reachable on the network.

Logging to the Access Controller

By default, the Access Controller has the following IP address: 192.168.1.99. You can manage and configure the FortiWiFi by establishing an SSH connection or by opening the following URL: http://192.168.1.99 via a web browser and logging in as the admin user, without any password.

Adding the RADIUS server

Go to User & Device > Authentication > RADIUS Servers. Define the connection to the RADIUS server.

Name: myRadius

Primary Server IP: 54.247.117.188

Prim. Server Secret: provided by C4W

Secondary Server IP: 79.125.111.180

Sec. Server Secret: provided by C4W

https://splashportal.cloud4wi.com

Go to User & Device > User > User Groups. Define a firewall user group with the RADIUS server as its only member. Click Create New button, select the radius server previously created and click OK.

Enable HTTPS authentication and Radius Accounting

Go to Dashboard. Use the CLI console to enable HTTPS for authentication, so that user credentials are communicated securely.

Launch the following commands:

config user settingsset auth-secure-http enableend

Create the WiFi network

Go to WiFi Controller > WiFi Network > SSID to create the WiFi SSID.

Enter the following:

Interface Name: APSSID

Type: WiFi SSID

Traffic Mode: Tunnel to Wireless Controller

IP/Network Mask: 192.168.20.1 / 255.255.255.0

Restrict Access: RADIUS Accounting

Configure external captive portal security. Do not include http:// or https:// in the captive portal URL.

SSID: C4W-Fortinet

Security Mode: Captive Portal

Portal Type: Authentication

Authentication Portal (External enabled): splashportal.cloud4wi.com

User Groups: extRadius

Redirect after Captive Portal (Specific URL enabled): https://splashportal.cloud4wi.com

Click on button OK to save.

Create policies for the captive portal and unauthenticated users

Go to Policy & Objects > Objects > Addresses.

Create an address for the captive portal.

Name: ecp

Type: IP/Netmask

Subnet / IP Range: 54.247.177.188

Interface: wan1

Click OK to save.

Go to Policy & Objects > Policy > IPv4. Create a security policy for unauthenticated users that allows access only to the captive portal.

Name: Unauth-Users

Incoming Interface: C4W-Fortinet (APSSID)

Outgoing Interface: wan1

Source: all

Destination Address: ecp

Schedule: always

Service: ALL

Action: ACCEPT

Click OK.

In the CLI Console, enable bypass of the captive portal so that the user can make the initial contact with the external server.Launch the following commands:

config firewall policyedit <policy_id>set captive-portal-exempt enableend

Obtain <policy_id> from ID column of the policy list (Policy & Objects > Policy > IPv4).

Create your Internet access security policy

Go to Policy & Objects > Policy > Addresses.

Create a policy for the SSID created previously.Name: fortinet-C4W-netType: IP/NetmaskSubnet / IP Range: 192.168.20.0 / 255.255.255.0Interface: anyClick OK to save.

Go to Policy & Objects > Policy > IPv4. Create a policy to allow authenticated users access to the Internet.

Name: Auth_Users

Incoming Interface: C4W-Fortinet

Outgoing Interface: wan1

Source: fortinet-C4W-netextRadius

Destination Address: all

Schedule: always

Service: ALL

Action: ACCEPT

Leave others parameters as default.

Click OK to save.

Connect and authorize the FortiAP

Go to System > Network > Interface. Edit an unused interface, making it Dedicated to Extension Device. Connect the FortiAP to this interface and apply power. Go to WiFi Controller > Managed Devices > Managed FortiAPs.

Select and authorize the FortiAP.

Physical Interface Members: AP iface

Role: LAN

Admin Access: HTTPS, HTTP, FMG-Access, CAPWAP, SSH, RADIUS Accounting

DHCP Server: enabled

Starting IP: 192.168.1.100

End IP: 192.168.1.254

Netmask: 255.255.255.0

Click OK to save.

Go to WiFi Controller > WiFi Network > FortiAP Profiles. Edit the default profile for your FortiAP model. Enable your SSID for each radio.

Radio Mode: Access Point

Select SSIDs: C4W-Fortinet

Click OK to save.

Enter your policy to enable Social Login

To enable the Social Login its mandatory to configure some rules, on the Controller, to open some specific domain on the walled garden. In this guide will enable LinkedIn Login to give you an example.For the complete list of the websites/domain please check the next paragraph (Websites/domain list for social login).

Go to Policy & Objects > Objects > Addresses. Create an address for social login.

Name: api.linkedin.com

Type: FQDN

FQDN: api.linkedin.com

Interface: any

Click OK to save.

To group address previously created, add a new Address Group.

Name: Linkedin Login

Members: api.linkedin.com,licdn.com,linkedin.comstatic.licdn.com

Click OK to save.

Go to Policy & Objects > Policy > IPv4.

Edit the Unauth-Users Policy previously created and add Linkedin Address Group.

Destination Address: ecp, Linkedin

Click OK to save.

Walled garden

Based on the example above, you can create specific access-rules in order to allow unauthenticated users to enter specific domains.When configuring the walled garden, you are required to add the following domain: cloud4wi.com. This allows you a proper redirection to the Splash Page and enables the access to the CDN.For some specific use cases, you may be interested in the following articles:

Walled garden for the Social Login (websites/domains to open)

Walled garden for PayPal feature (websites/domains to open)

Entering the device details into the Admin Panel

For Fortinet devices, Cloud4Wi requires only the MAC address and the Identifier field is not required.

Parameters for the Solution

Add the radius server

Configure the radius server

Name: myRadius

Primary Server IP/Name: 54.247.117.188

Primary Server Secret: (it will be communicated by Cloud4Wi)

Secondary Server IP/Name: 79.125.111.180

Secondary Server Secret: (it will be communicated by Cloud4Wi)

Define a firewall user group and link to radius

Name: extRadius

Type: Firewall

Groups: myRadius

Enable HTTPS authentication

Execute the following commands by CLI Console to enable HTTPS Authentication

config user settingsset auth-secure-http enableend

Create the WiFi network

Create a new interface

Interface Name: APSSID

Type: WiFi SSID

Traffic Mode: Tunnel to Wireless Controller

IP/Network Mask: 192.168.20.1 / 255.255.255.0

Restrict Access: RADIUS Accounting

WiFi Settings

SSID: C4W-Fortinet

Security Mode: Captive Portal

Portal Type: Authentication

Authentication Portal (External enabled): splashportal.cloud4wi.com

User Groups: extRadius

Redirect after Captive Portal (Specific URL enabled):

Create policies for captive portal and unauthenticated users

Captive portal policy

Name: ecp

Type: IP/Netmask

Subnet / IP Range: 54.247.177.188

Interface: wan1

Unauthenticated users policy

Name: Unauth-Users

Incoming Interface: C4W-Fortinet (APSSID)

Outgoing Interface: wan1

Source: all

Destination Address: ecp

Schedule: always

Service: ALL

Action: ACCEPT

Enable bypass of the captive portal (by CLI)

config firewall policyedit <policy_id>set captive-portal-exempt enableend

Create your Internet access security policy

Policy for SSID network created previously.

Name: fortinet-C4W-net

Type: IP/Netmask

Subnet / IP Range: 192.168.20.0 / 255.255.255.0

Interface: any

Policy to allow authenticated users to go to the Internet

Name: Auth_Users

Incoming Interface: C4W-Fortinet(APSSID)

Outgoing Interface: wan1

Source: fortinet-C4W-netextRadius

Destination Address: all

Schedule: always

Service: ALL

Action: ACCEPT

Connect and authorize the FortiAP

Configure APs Profile

Role: LAN

Admin Access: HTTPS, HTTP, FMG-Access, CAPWAP, SSH, RADIUS Accounting

DHCP Server: enabled

Starting IP: 192.168.1.100

End IP: 192.168.1.254

Netmask: 255.255.255.0

Enable Radio and associate to an SSID

Radio Mode: Access Point

Select SSIDs: C4W-Fortinet

Enter policy to enable Social Login (LinkedIn Login)

LinkedIn Login (Group Address)

Name: Linkedin Login

Members: api.linkedin.com,licdn.com,linkedin.comstatic.licdn.com

Last Updated: November 21st, 2019

PLEASE READ THESE TERMS CAREFULLY BEFORE USING THE SERVICE

These Terms of Use (Terms) form a legally binding agreement between you or the entity that you represent (Company or you) and Cloud4Wi Inc. located at81 Prospect St,New York, NY 11201,United States of America, USA (Cloud4Wi, us or we) for the use of our proprietary Cloud4Wi API service (Service).

By clicking on "I AGREE (I AGREE) on the Cloud4Wi Dashboard when getting access to APIs for the first time, you represent that you have read, understood, and agree to be bound by there Terms and to use the Service in compliance with these Terms. The Effective Date of these Terms is the date that you click on "I AGREE".

If you do not agree to these Terms, please do not click I AGREE but I REJECT and you are not permitted to access or use the Service.

1.DEFINITIONS

For purposes of these Terms, the following terms have the corresponding definitions listed below:

1.1 Additional Terms means the End Customer Agreement that is applicable to the Cloud4Wi Platform.

1.2 API Information means the standard applications programming interface (API) information generally provided by Cloud4Wi to users of the Service that specifies the requirements for interfacing to (e.g. invoking or directing the functions of) the Service or software included in the Service. API Information does not include any implementation of such interface information, any development materials or any other Cloud4Wi Services.

1.3 Application means a software application or website that uses the Service to obtain and display Content in conjunction with Your Content, according to these Terms.

1.4 Authorized Users means your individual employees, consultants, contractors, and agents who access and use the Service on your or your Companys behalf and for whose compliance with these Terms you are responsible.

1.5 "Brand Features" means the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of: (i) each party, respectively, as secured by such party from time to time; and (ii) additionally, for Cloud4Wi Brand Features, the distinctive brand features of certain third parties.

1.6 Claim means any legal claim, suit or proceeding.

1.7 Confidential Information means, collectively, any information: (a) designated as confidential orally or in writing by Cloud4Wi; (b) related to Cloud4Wis business or operations; or (c) received by you by virtue of your relationship with Cloud4Wi including, but not limited to, customer information, product plans, product designs, product costs, product prices, product names, finances, marketing plans, business opportunities, personnel, research, development, customer data, or know-how.

1.8 "Content" means any data and information made available by Cloud4Wi for use with the Service.

1.9 End User means your customers and/or other users who will be using your Application.

1.10Personal Informationmeans the information that specifically identifies an individual.

1.11Platformmeans the proprietary cloud-based open Wi-Fi engagement platform, accessible via web and mobile applications, which enhances Guest Wi-Fi access at venues.

1.12 Term means the length of time the Terms are in force.

1.13 Terms means the terms and conditions in these Terms of Service, including any documents incorporated by reference.

1.14 "Your Content" means any content that you provide in your Application, including data, images, video, or computer programs (including, without limitation, any modules and components, functions and features of a computer program). Your Content does not include the Content.

2.SERVICE

2.1 The Service is a collection of web services and SaaS application APIs that allows you to develop cloud-based applications, integrate your applications with the Platform or build applications that integrate with the Platform.

2.2 Cloud4Wi may impose or adjust the limit on the number of transactions you may send or receive through the Service, including rate limits (number of transactions per second) and usage limits (number of transactions per hour or day). Such fixed upper limits may be set by Cloud4Wi at any time, at Cloud4Wis discretion.

2.3 Cloud4Wi may, at its sole discretion, choose to offer the Service as a commercial service in the future, but is under no obligation to do so.

2.4 Cloud4Wi may limit the availability of the Service to any geographical area(s) and/or any language(s)

2.5 Cloud4Wi may make backwards-incompatible changes to the Service.

2.6 You agree to use the Service only for purposes: a) that are permitted by the Terms; b) that are permitted by any applicable third party contract, law or regulation in the relevant jurisdictions; and, c) that comply with all applicable policies or guidelines, if any, made available by Cloud4Wi.

2.7 Your Application must add significant value to the Service, and not merely be an offering of any part of the Service or Content in an API to others, nor a reimplementation or duplication of the Content. Furthermore, your Application must be used in connection with the Platform.

2.8 Your Application must be generally accessible to End Users without change and must not require a fee-based subscription or other fee-based restricted access. This rules applies to Your Content and any other content in your Application.

3.LICENSES GRANTED FROM CLOUD4WI TO YOU

3.1 Subjects to these Terms, Cloud4Wi gives you a limited, non-transferable, non-assignable, non-sublicensable, revocable and non-exclusive license during the Terms to: a) use and access the Service solely for the purpose of developing, testing, integrating, operating and supporting your Application in the manner permitted by the Terms; b) access, use, publicly perform and publicly display within your Application the portions of the Content placed by Cloud4Wi within the Service, in unmodified form; c) reproduce and modify or make a derivative work of certain designated sample code for the purposes of developing the Application that interfaces with the Content; and d) distribute such sample code to your End User solely as embedded in and constituting an integrated part of your Application for the purposes of complementing and enhancing the Content, unless otherwise specifically prohibited by the licenses for certain software development tools, utilities and kits; and e) use Cloud4Wis Brand Feature solely for your marketing or promotional materials for your Application in the manner permitted by the Terms.

3.2 Except as explicitly permitted in these Terms, you must not (nor permit anyone else to): a) license, sublicense, sell, resell, transfer, assign, rent, loan, lease, distribute or otherwise commercially exploit or make available or otherwise transfer to any third party the Service or any other rights granted in these Terms in any way, or use the Service a s a service bureau; b) copy, modify, translate, adapt, arrange, make derivate works of or publicly display the Service or any Content or any part thereof except as expressly permitted herein; c) reverse engineer or access the Service for the purpose of (i) building a competitive product or service, (ii) building a product using similar ideas, features, functions or graphics of the Service or the Content, or (iii) copying any ideas, features, functions or graphics of the Service or the Content; d) decompile, disassemble or otherwise reverse engineer the Service, or determine or attempt to determine any source code, algorithms, methods, or techniques used or embodied in the Service; e) take any action that Cloud4Wi determines imposes an unreasonably or disproportionately large burden on Cloud4Wi's (or its designated third parties') infrastructure, including the Service; and f) attempt to (i) remove, defeat or circumvent any license manager technology or copy protection device provided with the Service or (ii) bypass or delete any functionality or technical limitations of the Service that prevent or inhibit the unauthorized copying or use of the Service.

4.LICENSES GRANTED TO YOU FROM CLOUD4WI

4.1 You grant to Cloud4Wi the use your name and logo as part of a customer list on our website or in connection with our other customer listings.

4.2 You grant to Cloud4Wi a royalty-free, worldwide, irrevocable, perpetual license to use and incorporate any suggestions, feedback, improvement requests or other recommendations you and/or your Authorized Users and/or your End Users provide, relating to the Service.

4.3 Your authority to grant licenses. You represent and warrant to Cloud4Wi that you have all the rights, power and authority necessary to grant the above licenses.

5.RULES FOR USING CLOUD4WI BRAND FEATURES

5.1 Your use of the Cloud4Wi Brand Features in any promotion or advertising, if any, shall be approved by Cloud4Wi. You will provide copies of all marketing and promotional materials that use the Cloud4Wi Brand Features for Cloud4Wis review. If Cloud4Wi, in its sole discretion, determines that your use of the Cloud4Wi Brand Features is not in compliance with these Terms, you will promptly change or stop using the materials as directed by Cloud4Wi.

5.2 In using Cloud4Wi Brand Features, you will not: (i) display an Cloud4Wi Brand Feature in any manner that implies a relationship or affiliation with, sponsorship, or endorsement by Cloud4Wi, other than your use of the Service, or that can be reasonably interpreted to suggest editorial content has been authored by, or represents the view or opinions of Cloud4Wi or Cloud4Wi personnel; (ii) display an Cloud4Wi Brand Feature in your Application or on your website if your Application or website contains or displays adult content or promotes illegal activities, gambling, or the sale of tobacco or alcohol to persons under 21 years of age; (iii) display an Cloud4Wi Brand Feature as the most prominent element in your Application or on any page of your website; (iv) display an Cloud4Wi Brand Feature in a manner that is misleading, defamatory, infringing, libelous, disparaging, obscene or otherwise objectionable to Cloud4Wi (or as to Cloud4Wis products and/or services); (v) display an Cloud4Wi Brand Feature in your Application or on any website that violates any law or regulation; (vi) remove, distort or alter any element of an Cloud4Wi Brand Feature.

5.3 Except as set forth in the Section 5.1, nothing in the Terms will grant or will be deemed to grant you any right, title or interest in or to Cloud4Wi Brand Features. All use by you of the Cloud4Wi Brand Features will insure to the benefit of Cloud4Wi. To the maximum extent permitted by applicable law, at any time during or after the Term you will not: (i) challenge, contest or oppose, nor assist others to challenge, contest or oppose Cloud4Wis ownership of the Cloud4Wi Brand Features or their registration Cloud4Wi; (ii) attempt to register any Cloud4Wi Brand Features (including domain names) that are confusingly similar to those of Cloud4Wi in any way (including but not limited to sound, appearance and spelling); or (iii) misappropriate the Cloud4Wi Brand Features for your or any third partys use.

6.END USER AGREEMENT AND YOUR PRIVACY POLICY

6.1 You must enter into a legally binding agreement with your End Users for your Application that explicitly states that, by using your Application, your End Users are: (i) agreeing to be bound by (1) Cloud4Wis API Terms of Use and (2) Cloud4Wis Privacy Policy; and (ii) solely responsible for any data that the End User inputs in its use of your Application. Your agreement will display to your End Users the link to Cloud4Wi API Terms of Use (located at support.cloud4wi.com/api-terms-of-use) and Cloud4Wis Privacy Policy (located at support.cloud4wi.com/privacy and as such Privacy Statement may be modified from time to time);

6.2 You must explicitly state in your Applications agreement that: (i) to the maximum extent permitted by law, Cloud4Wi provides the Platform and Content as is with all faults, and disclaims all warranties and conditions, either express, implied or statutory including but not limited to any implied warranties or conditions of merchantability, fitness for a particular purpose, lack of viruses, accuracy or completeness of responses or results, lack of negligence, title, quiet enjoyment, quiet possession, correspondence to description or non-infringement, with regard to the Platform and Content; (ii) the entire risk as to the quality of or arising out of use or performance of the Content and the Platform remains with you, as creator of the Application, and the End User as user of your Application; (iii) your End Users retain copyright and any other rights they already hold in the content and data they use in relation to your Application, and that they are responsible for the content, data, and other materials that they upload, post, email or otherwise transmit in using your Application; (iv) Cloud4Wi does not warrant that the operation of the Platform or Content will be uninterrupted or error free. Further, your agreement must explicitly state that: (1) by submitting, posting or displaying their content and/or data through your Application, your End Users give Cloud4Wi a perpetual, irrevocable, worldwide, royalty-free and non-exclusive license during the Term to reproduce, adapt, modify, translate, publicly perform, publicly display and distribute their content and/or data through the Service for the sole purpose of enabling Cloud4Wi to provide you with the Service in accordance with the Terms and (2) your End Users grant to Cloud4Wi a worldwide, royalty-free, non-transferable, and non-exclusive license during the Term to use their brand features and their content to publicize or advertise that you are using the Service (for example, by using their marks in presentations, marketing materials, customer lists, financial reports and Web site listings (including links to their website), or by creating marketing or advertising materials that show screenshots of the Service in which their content is featured).

6.3 You must protect the privacy and legal rights of your End Users: (i) you must make publicly available, and must abide by, an appropriate privacy policy in relation to your Application. In particular, if your Application enables you or any party to gain access to information about End Users of your Application, including but not limited to personally identifiable information (such as user names), your privacy policy must describe your use and retention of this information. Without limiting the foregoing, you will ensure that you have provided adequate notice to and obtained consents from your End Users, to the extent necessary, to provide personal data to be transferred to, collected, stored, used and otherwise processed by Cloud4Wi and its service providers; and (ii) your privacy policy must notify End Users that you are using the Service and incorporate by reference the Cloud4Wi Privacy Policy by including a link to the Cloud4Wi Privacy Policy (located at support.cloud4wi.com/privacy and as such Privacy Statement may be modified from time to time).

7.ENFORCEMENT

7.1 Cloud4Wi has the sole right (but no obligation) and discretion to monitor your usage of the Service to verify compliance with the Terms. If Cloud4Wi requires additional reporting mechanisms, Cloud4Wi will notify you as such per Section 17.

7.2 Cloud4Wi can take enforcement action against you if Cloud4Wi determines in its sole judgment that you and/or your Authorized User and/or your Application violate the Terms. Enforcement action can include: a) disabling or restricting your and your Applications access to the Service or the Platform; b) terminating some or all of our agreements with you; or c) any other action as Cloud4Wi in its sole discretion deems appropriate.

8.TERM AND TERMINATION

8.1 These Terms will be effective on the Effective Date and these Terms will extend from the Effective Date until these Terms are terminated or expire as described in this Section.

8.2 Cloud4Wi can terminate these Terms and/or discontinue the Service or any portion or feature for any reason and at any time without liability or other obligations to you.

8.3 You may terminate these Terms by removing the Cloud4Wi API code from your Application and discontinuing your use of the Service at any time. You do not need to specifically inform Cloud4Wi when you stop the Service.

8.4 Unless terminated earlier as permitted by the Terms, these Terms will automatically terminate one (1) year from the Effective Date.

8.5 Upon the termination of these Terms for any reason, you and your Authorized User must immediately cease using the Service. Those terms that by their nature are intended to continue indefinitely will continue to apply, including but not limited to Sections 9, 10, 12, 13, 14, 18, 19, 20, and 23.

9.INTELLECTUAL PROPERTY

9.1 You acknowledge and agree that Cloud4Wi and its licensors own all right, title, and interest (including, without limitation, patents, copyrights, trademarks, trade secrets, and all other intellectual property rights) in and to the Service, API Information, development materials, Cloud4Wi API documentation, Cloud4Wi Brand Features, sample data sets, sample models or other Content and any information, data or materials provided or used in connection with, or generated by, the Service (excluding Your Content as defined below).

9.2 You acknowledge and agree that any API Information (unless otherwise specified by Cloud4Wi in Additional Terms associated with such API Information or any related development materials): (a) is confidential and proprietary to Cloud4Wi; (b) may not be distributed, disclosed or otherwise provided to third parties; and (c) may be used only internally and only in conjunction with and for your own authorized internal use of the Service to which the API Information relates, such as the development and support of your Application.

9.3 Subject to Cloud4Wis and its licensors ownership of the Service and the Content, as between you and Cloud4Wi, you own or have the appropriate rights to Your Content and your Application. Cloud4Wi claims no ownership over Your Content or your Application, and you retain copyright and any other rights you already hold in Your Content. You, and not Cloud4Wi, are responsible for Your Content and other materials that you and/or your Authorized Users upload, post, email or otherwise transmit in using the Service and your Application. You acknowledge and agree that: (a) you have the requisite rights to submit, develop and use Your Content and your Application in connection with the Service; (b) Your Content and your Application do not infringe or misappropriate any intellectual property or proprietary right of any third party or violation any applicable laws, rules or regulations; and (c) Your Content and your Application are not subject to any restrictions on disclosure, transfer, download, export or re-export under any applicable law, rule or regulation.

10.INDEMNIFICATION

The Company shall, at its sole expense and to the fullest extent permitted by law, indemnify, defend (at Cloud4Wi's request), and hold Cloud4Wi, its affiliates, and their employees, officers, directors, successors, assigns, agents, and customers harmless against any and all losses, liabilities, expenses (including reasonable attorneys' fees) suffered or incurred by Cloud4Wi by reason of any Claim arising out of or in connection with: (a) its Application or Content, including, without limitation, any assertion that its Content or its Application or the use of either or both may infringe any copyright, trademark, or other intellectual property or other rights of any individual or entity, or are a misappropriation of any individual or entity's trade secret, or contain any libelous, defamatory, disparaging, pornographic, or obscene materials or that use thereof caused death or bodily injury or damage to the real or tangible property of any third party; (b) any breach of or failure by the Company or its Authorized Users to comply with the Terms (including, without limitation, any policies and Additional Terms); or (c) use of the Service by the Company and/or its Authorized Users and/or anyone who accesses the Service through the Company (whether or not such access is authorized by the Company or by Cloud4Wi). If requested by Cloud4Wi to defend a Claim, the Company will not agree to any settlement without the prior written consent of Cloud4Wi, and Cloud4Wi shall have the right to participate, at its own expense, in the defense of any Claim with counsel of its own choosing.

11.WARRANTIES

Each party hereby represents and warrants to the other that it has all necessary corporate power and authority to perform its obligations under these Terms and to consummate the transactions contemplated hereby. These Terms constitute legal, valid, and binding obligations of the warranting party enforceable against the non-warranting party in accordance with its terms.

12.DISCLAIMER OF WARRANTIES

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE". CLOUD4WI MAKE NO, AND HEREBY DISCLAIM ALL, REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF ANY KIND, WHETHER EXPRESS, IMPLIED (EITHER IN FACT OR BY OPERATION OF LAW), OR STATUTORY, WITH RESPECT TO THE SERVICE, INCLUDING, WITHOUT LIMITATION, ALL WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT, AND ALL WARRANTIES THAT MAY ARISE FROM COURSE OF DEALING, COURSE OF PERFORMANCE, OR USAGE OF TRADE. YOUR USE OF THE SERVICE IS AT YOUR OWN DISCRETION AND RISK. CLOUD4WI DOES NOT WARRANT THAT ANY USE OF OR ACCESS TO THE SERVICE WILL BE ERROR-FREE, COMPLETE, SECURE OR MEET YOUR REQUIREMENTS OR EXPECTATIONS; THAT OPERATION OR AVAILABILITY WILL BE UNINTERRUPTED; OR THAT ERRORS OR FAILURES WILL BE CORRECTED OR REMEDIED; AND CLOUD4WI HEREBY DISCLAIMS ANY AND ALL LIABILITY IN CONNECTION THEREWITH. CLOUD4WI DOES NOT WARRANT THAT THE SERVICE WILL PERFORM IN ANY PARTICULAR MANNER AND HEREBY DISCLAIM LIABILITY FOR NEGLIGENCE AND GROSS NEGLIGENCE. WITHOUT LIMITATION OF THE GENERALITY OF THE FOREGOING, YOU ACKNOWLEDGE AND AGREE THAT YOU ARE SOLELY RESPONSIBLE FOR (AND CLOUD4WI ASSUMES NO RESPONSIBILITY AND WILL HAVE NO LIABILITY OF ANY KIND FOR) (A) THE DECISIONS THAT YOU MAY MAKE REGARDING THE SERVICE, (B) USE OF THE SERVICE INCLUDING ANY CONTENT, DATA, INFORMATION, OR OTHER MATERIAL ACCESSED BY YOU IN CONNECTION WITH THE SERVICE, OR (C) ANY EFFECTS ON YOUR BUSINESS THAT MAY RESULT FROM SUCH USE. CLOUD4WI MAKES NO WARRANTIES TO ANY THIRD PARTY. YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE IN CONNECTION WITH THE SERVICE INCLUDING ANY CONTENT, DATA, INFORMATION, OR OTHER MATERIAL ACCESSED BY YOU IN CONNECTION WITH THE SERVICE, INCLUDING, WITHOUT LIMITATION, TO YOUR COMPUTER SYSTEM OR LOSS OF DATA. CLOUD4WI DOES NOT REPRESENT OR WARRANT THAT THE SERVICE IS OR WILL BE APPROPRIATE OR AVAILABLE FOR USE IN ANY PARTICULAR JURISDICTION AND YOU ACKNOWLEDGE AND AGREE THAT CLOUD4WI MAY LIMIT THE SERVICES AVAILABILITY, IN WHOLE OR IN PART, TO ANY GEOGRAPHIC AREA, JURISDICTION OR LANGUAGE THAT CLOUD4WI CHOOSES, AT ANY TIME, IN CLOUD4WI 'S SOLE DISCRETION. NO INFORMATION OR ADVICE (WHETHER WRITTEN, ORAL OR OTHERWISE) PROVIDED BY CLOUD4WI OR ITS REPRESENTATIVES WILL CREATE ANY WARRANTY OR IN ANY WAY AFFECT THE DISCLAIMERS OF WARRANTIES OR LIMITATIONS OF LIABILITY EXPRESSLY PROVIDED IN THE TERMS.

13.LIMITATION OF LIABILITY

IN NO EVENT WILL CLOUD4WI BE LIABLE HEREUNDER FOR SPECIAL, INDIRECT, CONSEQUENTIAL, OR ANY OTHER DAMAGES WHATSOEVER (HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WHETHER DERIVED FROM CONTRACT, TORT (INCLUDING WITHOUT LIMITATION NEGLIGENCE) OR OTHERWISE), INCLUDING WITHOUT LIMITATION LOSS OF PROFITS, LOSS OF REVENUE, LOSS OF USE, LOSS OF DATA, BUSINESS INTERRUPTION, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES OR OTHER COVER, OR ANY OTHER COMMERCIAL OR ECONOMIC LOSS OF ANY KIND, EVEN IF ADVISED OF THE POSSIBILITY THEREOF, NOR CLOUD4WI BE LIABLE FOR ANY DAMAGES WHATSOEVER RESULTING FROM A FORCE MAJEURE EVENT OR AN ACT OF A THIRD PARTY OR THROUGH NO FAULT ON THEIR RESPECTIVE BEHALVES. You agree that you are solely responsible for (and that Cloud4Wi has no responsibility to you or to any third party for) any breach of your and/or your Authorized Users and/or your End Users obligations under these Terms and for the consequences of any such breach (including any loss or damage that Cloud4Wi may suffer).

14.CONFIDENTIALITY

Except as described in Section 4.1, any and all information provided directly or indirectly by one party (the Disclosing Party) to the other party (the "Receiving Party"), including, but not limited to, any software, hardware, inventions, processes, designs, drawings, specifications, blueprints, technical information, know-how, trade secrets, product, marketing, business, or financial information related to the Disclosing Party (collectively, "Confidential Information"), will be kept confidential by the Receiving Party and may not be used, communicated, disclosed, or divulged, except as necessary in the performance of the Receiving Partys obligations under these Terms or otherwise in connection with the deployment, operation, and maintenance of the Service. The Receiving Party agrees to limit access to the Confidential Information to those of its employees or contractors as are reasonably required for the purpose of performing the Receiving Partys obligations under these Terms or otherwise in connection with the deployment, operation, and maintenance of the Service. Prior to disclosing any Confidential Information to any of its employees or contractors, the Receiving Party will obtain from each such employee or contractor an agreement substantially as protective of the Disclosing Partys Confidential Information as the provisions hereof and each employee or contractor agrees not to use such information except in the performance of obligations hereunder. Notwithstanding the foregoing, Confidential Information does not include any information that the Receiving Party can verify based on its written records was (a) already lawfully in the Receiving Party's possession without confidentiality obligations prior to receiving it from the Disclosing Party, (b) independently received from a third party without an accompanying duty of confidentiality and without breach of such third party\s obligations of confidentiality, (c) becomes available in the public domain through no action or inaction of the Receiving Party, or (d) developed independently by the Receiving Party without use of or reference to Disclosing Partys Confidential Information. If Receiving Party becomes legally compelled to disclose any Confidential Information, other than pursuant to a confidentiality agreement, Receiving Party will provide Disclosing Party prompt written notice, if legally permissible, and will use its best efforts to assist Disclosing Party in seeking a protective order or another appropriate remedy.

15.PRIVACY AND DATA PROTECTION

15.1 You understand and agree that by using the Service, you consent to the collection, use, processing, and storage of your Personal Information, including cross-border transfers as described in the Privacy Policy.

15.2 You acknowledge and agree that you are responsible for compliance with all applicable privacy and data protection laws related to Personal Information provided to Cloud4Wi in connection with use of the Service by you or your Authorized Users, including any applicable requirements related to notice, consent, transfer (including cross-border transfer), disclosure, and use of Personal Information in connection with the Service, including as described in the Privacy Policy. Without limiting the foregoing, you will ensure that you have obtained consents, to the extent necessary, to provide Personal Information to be transferred to, collected, stored, used and otherwise processed by Cloud4Wi and its service providers, and that any individual who accesses or uses the Service has been made aware of the Privacy Policy.

15.3 You acknowledge that Cloud4Wi may use third-party service providers in connection with the Service, including without limitation the use of cloud computing service providers which may transmit, maintain and store Your Content and data using third-party computers and equipment in locations around the globe. You acknowledge that any data storage functionality associated with the Service is not intended for the storage of Sensitive Personal Information. You agree not to upload or otherwise submit any Sensitive Personal Information in connection with the Service and further agree that Cloud4Wi Parties will have no responsibility or liability with respect to any such Sensitive Personal Information that is processed, transmitted, disclosed, or stored in connection with the Service.

15.4 You must publicly post and make easily accessible your privacy policy, which clearly explains what data you are collecting and how you will use that data. You will abide by your privacy policy and will comply with all applicable laws relating to the collection of information from visitors to your Application in accordance with the specific requirements of Section 6.

16.CONSENT TO ELECTRONIC COMMUNICATIONS; NOTICE.

By using the Service, you consent to receiving electronic communications from us. These communications may include notices about your account and information concerning or related to the Service. You agree that any notices, agreements, disclosures, or other communications that we send to you electronically will satisfy any legal communication requirements, including that such communications be in writing. Any notice that you provide to us under these Terms will be effective if it is in writing and sent by certified or registered mail, or insured courier, return receipt requested, to Cloud4Wi at the address set forth above and with the appropriate postage affixed.

17.AMENDMENTS TO THESE TERMS

We may periodically make changes to these Terms. It is your responsibility to review the most recent version of these Terms frequently and remain informed of any changes to it. You agree that your continued use of the Service after such changes have been published to our website at support.cloud4wi.com/api-terms-of-use will constitute your acceptance of such revised Terms. For any material modifications to these Terms, such modifications will automatically be effective 30 days after they are initially posted on or through our website. In the event that such modifications materially alter your rights or obligations hereunder, such modifications will become effective upon the earlier of (i) your continued use of the Service with actual knowledge of such modifications, or (ii) 30 days from publication of such modifications on or through our website. If and when we release a commercial version of the Service, we will notify via email to you and you will be required to accept the new Terms before you can use the commercial version.

18.WAIVER

No failure or delay by you or by us to exercise any right under these Terms will constitute a waiver of that right.

19.SEVERABILITY

If any portion of these Terms is held invalid by a court of competent jurisdiction, then such portion will be deemed to be of no force or effect, and these Terms will be construed as if such portion had not been included herein. If the deletion of such provision materially impairs the commercial value of these Terms, then the Company and Cloud4Wi will attempt to renegotiate such provision in good faith.

20.INDEPENDENT CONTRACTORS

The Company and Cloud4Wi are independent contractors. Neither of you, nor Cloud4Wi, nor any of your or our respective employees, customers or agents, will be deemed to be the representative, agent, or employee of the other for any purpose whatsoever, and none of them have the right or authority to assume or create an obligation of any kind or nature, express or implied, on behalf of the other, or to accept service of any legal claims or notices addressed to or intended for the other.

21.ENTIRE AGREEMENT

These Terms in conjunction with the Additional Terms constitute the entire agreement between Cloud4Wi and the Company with respect to the subject matter of the entire agreement and supersede all prior agreements, understandings, and arrangements, oral or written, between Cloud4Wi and the Company. No agreement or representations, oral or otherwise, express or implied, with respect to the subject matter of the entire agreement have been made either by Cloud4Wi or the Company which is not expressly set forth in the entire agreement.

22.JURISDICTION AND LAW

These Terms will be governed by and construed in accordance with the laws of the state of California, USA. The Company and Cloud4Wi both agree to submit to the non-exclusive jurisdiction of the courts located in San Francisco, California.

23.MISCELLANEOUS

23.1 The headings used in these Terms are for convenience of reference only and do not affect the meaning or construction of these Terms.

23.2 The official language of these Terms is English. All contract interpretations, notices and dispute resolutions will be in English. Any attachments or amendments to these Terms will be in English. Translations of any of these documents will not be construed as official or original versions of such documents.

24.CONTACTS

If you have any questions or comments about these Terms, please contact Cloud4Wi using the following contact information:

81 Prospect St,New York, NY 11201United States of America

[email protected]

09/26/2019

Dear customer,were delighted to bring you some important updates to the Cloud4Wi product suite.

Data Processing Control(Compass, Splash)

We introduced new and powerful settings to let you control how the collection of customers consent is reflected in their personal data processing. Now you can specify the minimum opt-ins to be collected from customers in order to process their personal data, track their visits and profile them.

You can learn more in this detailed article.

Customer Visit History (Compass)

Compass identifies customer visits by leveraging data that signals customer interactions in the store including the data from passive WiFi tracking and WiFi Connections. The data from multiple sources are blended and processed with sophisticated algorithms to distill the relevant interactions, called Visits. The history of each customers Visits can now be visualized in the profile page.

Behavioral Metrics(Compass)

Based on the history of the Visits, the system computes statistical metrics that describe and summarize how a customer interacts with the organization (for example, date of the last visit, most visited location, average visit time, etc.). These metrics are refreshed daily to make sure they reflect the actual interactions of each individual.The behavioral metrics can be used by marketers to identify and target specific audiences based on their behaviors and interactions with the stores, for example, customers who havent visited in a long time, customers who visited during a specific event, or most loyal customers.The metrics are part of the contact profile and they are available in the contact exports via CSV, in the related API endpoints.

The full list of available metrics can be found in this detailed article.

Dashboards and Metrics Review(Spaces)

We revisited the metrics provided by Spaces and we collapsed the Overview and Trends dashboards into a new one simply called Behaviors.We removed some of the metrics that refer to the count of unique individuals and focused instead on those that support use cases related to marketing initiatives by informing the strategy and measuring the impact of store-related campaigns.

Please read this detailed article for more details.

Minor improvements

A new file, called External Venue ID, has been added in the Venue configuration. The ID is exposed in the /venues API end-point and offers an easier sync of the data with external systems that use existing codes to identify the stores

Minor improvements to the Promo Page tool, including the possibility to change the style via custom CSS

As anticipated in previous communications, wemade some changes to Spaces as a strategic step in the evolution of Cloud4Wi solutions. Spaces will focus on supporting use cases related to marketing initiatives byinformingthe strategyand measuring the impact of store-related campaigns.

How it works

Let's refresh some of the basic... Spaces collect a large amount of presence/location signals from all the nearby devices and process them to extract and classify the meaningful interactions that represent actual store visits. In fact, not all the signals we collect are related to actual visitors, shoppers or clients, but comes from walk-by traffic, nearby stores or even other network devices; Spaces elaborate these data with intelligent algorithms that automatically separate relevant data from noise and turns it in actionable metrics.

It is important to highlight that the baseline tracking technology used to track these events, cannot detect deterministically all the devices that are in proximity of the sensing devices; in fact, many smartphones adopt measures to protect their identity using random identifiers and many sensing devices (for example Cisco Maraki) do not even track these devices in the first place. This is one of the reasons why we focused the solution on those analysis and use cases that are not affected by this phenomenon.

Product changes

We removed some of the metrics that refer to thecount of unique individuals. The metrics have been removed from the Cloud4Wi Dashboard(including Custom Reports), from theCSV exportand fromAPIendpoints.

In particular, we removed the following metrics:

Visitors /Potential Visitors / Missed Visitors

Visits /Potential Visits / Missed Visits

Identified Visitors

New Visitors Rate (complement of Returning Visitors Rate)

Engagement Rate (complement of Bounce Rate)

We introduced a new metric called Traffic Index that is a proxy of the number of unique visitors, and it replaces the one previously called "Visitors". The new nomenclature reflects the fact that the metrics don't represent the exact count of individual that have visited a location.

The new "Behaviors" dashboard

The new dashboard includes multiple charts and metrics.

The top chart includes a history chart that plots the metrics across the observation period. In the history chart,each value represents the average value of the metrics for each time slot (for example a day) represented in the chart. The spot values on top of the chart, instead, represent the average value of the selected metric across the entire observation period.

The metrics in this chart are:

Visit duration: this is the average duration of the visits.The time visitors spend in the store is a good proxy of engagement. By tracking the history of this metric, brands can understand what store marketing initiatives are working and which onesdon'tkeep visitors engaged

Bounce Rate:this metric represents the percentage of visits shorter than a threshold (customizable) minutes. This metric, for example, helps measure the effectiveness of promotions displayed in the store entry area to capture visitor attention.

Attraction Rate: this metric is a proxy of the attractiveness of the store, and it is calculated as the percentage of foot traffic detected inthe proximity of the location that is converted into an actual visit.By comparing this value across multiple stores, the client can, for example, identify what displays and window setups work better for attracting visitors.

Returning Rate: a returning visit represent a visit done by an individual that already visited the brand before that specific event. The returning rate reported for a specific time slot is computed as the percentage of visits in that time slot that are classified as returning.If a device does a visit on day 1 and then a second visit from the same device on day 2, the second visit is classified as "returning". Note that a visit is considered returning only if the previous one happened on a different day.The Returning Rate is a proxy for customer loyalty and its evolution can help assess the effectiveness of retargeting campaigns and customer satisfaction.

The second chart is a histogram that shows the distribution of theVisit duration, to help you understand, other than the average value shown above, how the metric is actually distributed.

The last history charts represent the value of the Traffic Index.Traffic Indexis a proxy for the store traffic. While it can't tell exactly how many visitors visited during a certain period, this metric will help you understand how traffic intensity changes over time or how different stores perform compared to each other.Traffic Index is still represented with a number to facilitate comparison in time and across the stores, but it actually does not represent a count of visits or visitors.

Blacklist

As a consequence of these changes, also the parameters forblacklisting staff and network deviceshave changed. For analytics and reporting purposes, you can now discard any visit longer than a configurable visit time.

APIs

If you are currently using theAPIsto extract those metrics, you probably don't need to adapt your integrations. The existing API endpoint won't be removed and data model won't change, but they won't return any data for the metrics that will be removed.

Privacy and security

The signals collected from presence/location sources include the WiFi MAC address of the individual's phones, which is considered personal data under GDPR and other privacy regulations. Spaces immediately anonymize these identifiers inan irreversible fashion employing sophisticated processing, not using simple pseudonymization, but actually introducing a considerable level of information loss thatmakes mathematically impossible to know with a reasonable degree of certainty what the original client MAC address was.Moreover, for further robustness, Cloud4Wi also completely deletes the anonymized identifiers within 24 hours.

Segment Builder (Compass)In the segment builder, you can now specify relative periods on the date attributes. For example, you can define a rule to include all the users where the Last Visit Date is within the Last 6 months.

This new feature allows you to identify actionable audiences for your targeted marketing campaigns, exporting the customer data into your external marketing platform or using them as a filter for the real-time campaigns orchestrated with Cloud4Wi Triggered Campaigns.

Survey (Compass, Splash)You can now create multiple survey campaigns and publish them in the Access Journey of any location or group of locations identified by tags. For example, if you have two different brands in your organization, you can create a dedicated survey for each of them and publish it to the correct group of locations by filtering them using the tags.

Phone validation with a short link (Compass, Splash)We introduced a new experience to validate the phone number of the customer during the sign-up process with less friction. Prior to the update, the only method was to block the user during the sign-up, send him a text with a one time code, and ask the user to insert it in the Splash Page.

This new option works in the same way as the email validation process, by allowing the customer to go online without any friction granting him 5 minutes of time to validate his number.

Instead of sending a code, this new method sends a short link and simply clicking on it will confirm the phone number and extend the time allowance.

New paid service experience (Splash)

We improved the overall end customer experience when charging for premium internet access. In order to improve the user experience, we created a new dedicated Splash Portal template optimized for this experience and revisited the overall onboarding workflow. For example, users can now pick a plan before signing up, then sign-up with their preferred method and finally pay with the credit card for the plan they selected.You can explore the details in this article.

More personalization (Compass, Splash)

We extended the look and feel of our personalization capabilities so you can create a consistent experience across the entire access journey. The custom CSS file you upload in the Splash Portal settings is now applied to all the screens of the onboarding process, including, for example, the page that notifies the users to validate their email.

Other apps, such as Survey and Promo Page, have their own CSS customization capabilities.

New Splash Page template (Compass, Splash)

We introduced new Splash Portal templates to extend your personalization capabilities. The new template includes more content areas, including the possibility to show a permanent footer with the link to the terms and policies.

Location services support on Extreme Wireless (Spaces, Compass)

We now support presence and location services on Extreme Wireless Controllers. With Volare Spaces you can measure customer behaviors and with Volare Compass you can profile individuals based on their store visits.To see the detailed list of supported capabilities read this article.

Spaces Zoning processing update (Spaces)

In order to improve the accuracy of the metrics shown in the Zone dashboard, we introduced a filter to consider only the devices that have been seen with an RRSI greater than the threshold configured in the Spaces settings. This change can cause a minor change of the value represented in the Zone Analytics table, both for the virtual and physical zones.

Google+ SSO end of life (Compass, Splash)

Google discontinued Google+ in April 2019, but existing users can keep using it to log in to external services. We will discontinue its support by December 15th for all existing accounts.

Product Description

Splash Plus provides all the Guest WiFi service management capabilities included in Splash, and includes the following marketing capabilities:

Triggered Campaign : trigger messages, emails or texts, when a Customer logs in or sign-up on the guest WiFi service in a specific location

Email templates: create beautiful emails with a simple visual composer and send them using Triggered Campaigns

Offers : create promotions to be redeemed in-store to incentivize sign-ups, loyalty, and products, and send them via text or email with Triggered Campaigns

Survey : create beautiful surveys to collect customers feedbacks while they are in-store or after their visit

Promo Page : promotional pages with call to actions published in the Access Journey (for example to download a product catalog, a menu or onboard them on a chatbot)

Advertising Pages : informative advertising pages published in the Access Journey (for example to inform the customer about a program, temporary product promotions or an event)

Limitations

Splash Plus does not include the Segment Builder to create custom segments but it provides built-in options in Triggered Campaign to set the following filters:

Customer Age range

Customer Gender

Cumulative number of logins of the Customer

Sign-up method the Customer used to register the first time

Store where the triggering event happens

Time range when the triggering event happens

Campaign Delivery frequency (just once or once a day/week/month)

Campaign validity date range

Moreover, please note that Splash Plus does not:

provide the possibility to detect returning Customers passively based on their behaviors and interactions.

allow triggering campaigns based on the interactions in specific zones of the store

allow track customer visits, profile and cluster them based on their past visits and interactions

Marketing Use Cases

With Splash Plus, the Client can implement the following marketing oriented use cases.

Welcome campaigns: welcome emails are those with the highest open rate and conversion and used to convert new users in returning users by means of rewards or incentives (Offers)

Loyalty reward: reward returning customers sending them an Offer at their X visit

Incentivize frequency: send Offers when the customer leaves the store to incentivize his next visit

Interest discovery: discover what customers are interested in or the reason for their visit with Survey published during the WiFi onboarding

Experience feedback: collect the customer feedback about their visit to measure their satisfaction triggering a message with a Survey after their visit

Program promotions: inform customers about ongoing programs (loyalty, sales) and events using the Advertising pages published during the WiFi onboarding

Promote Mobile App: promote the download and usage of the mobile app, using the Promo Page tool

Onboard in chatbots: invite customers to join the chatbot channels in Messenger or Whatsapp, using the Promo Page tool

Subscriptions

Each Splash Plus Subscriptiongrants the following resources:

configure their own Twilio gateway

Access Points

Contacts

Emails

APIs

1Access Point

1200Contacts

35K Emailsper Year

100 API calls/month

Contacts

A Contact is a single person whose profile and contact information is stored in your account.Each Subscription includes 1200Contacts.

For example, a Client with 25Subscriptions would be allowed to keep in their account up to 30K Contacts

If Clients exceed this allowance, they can purchase additional Subscriptions to extend the limit of maxContacts or new registrations via guest WiFi will be blocked automatically.

Note: 10 X 3-year Subscription grant an allowance on the Account for 12K Contacts at any given time. The Contacts are not cumulative year over year, the 3-yearSubscription does not grant 12K X 3 contacts.

Emails

Splash Plus includes 35K emails perSubscription per Year. Considering that each Subscription allows 1200 Contacts, this cumulative Email limit allows an average fair usage of 4 emails/contact /month.Emails accounted in the limit include both marketing and service emails sent to Contacts (excluding account administration emails, such as password recovery)

For example, a Client with 1Subscription would be allowed to register up to 1200 Contacts and send up to 35K emails.If the number of Contacts grows linearly, for example 100 per month, the 35K emails are enough to send 4 emails per Contacts per month.

If Clients need to exceed this allowance they can buy and configure an external commercial SMTP service and connect it to their account.

APIs

Splash Plus Subscription includes 100 API calls/Month. API calls are counted from calls from the Cloud4Wi REST APIs and Connectors.

For example, a customer with 100 Splash Plus Subscriptions would be allowed 10,000 API calls per month

Usage of webhooks is subject to our fair usage policy of a maximum of 5 events webhooks per User per month.

API calls will be monitored on a monthly basis. If Clients exceed this allowance in the previous month, they can purchase additional Subscriptions to extend the overall limit of max API calls/month. If they do not extend the allowance, a hard threshold on the API rate will be enforced.

SMS

Clients have to to be able to send SMS messages and they can send unlimited messages at their own expenses.

Product Description

Splash provides all the capabilities to manage the Guest WiFi service:

Splash Pages

Create Splash Pages in line with corporate branding

Prebuilt, easy-to-customize templates

Flexible CMS to create custom page layouts

Style customization with custom CSS

Customizable Success page redirect

Multi-language support and possibility to create custom languages

Offline preview of the Splash Pages

Customizable domain (add-on)

SignUp via Kiosk and login with Splash Page via a one-time access code

Login options and Onboarding

Simplify guest WiFi onboarding by offering with multiple login options

Create multiple Login Profiles to be provisioned on different groups of Locations

Login with social network accounts (Facebook, Twitter, LinkedIn, Instagram, Google+, Pinterest, VKontakte, Foursquare, Sina Weibo, Baidu, QQ and Renren) and Gmail

Enrichment of social profiles with missing attributes

Login with click-through (passwordless) access with custom forms

Sign up with username and password

Automatic authentication of returning users

User account validation by email, text message or through a sponsor

Access Control via a shared password

Customizable consent collection experiences and agreements text(Privacy Policy, Terms of Use, Promotional Communications and text versioning)

Customizable, optional opt-ins

Age verification

Internet Access Policies

Define the policies to use your guest WiFi

Possibility to create multiple Internet Plans, assigns a default plan on each location

Change or add Internet Plans on specific Users

Time or traffic allowance per session

Recurring or one-time policies

Access code management for self-provisioning process

Pay-per-use service support with online payments

Control of plan bandwidth (QoS)

Control of plan traffic (on supported WiFi vendors)

Support of multiple concurrent devices on the same account

User management

Easily manage the WiFi users

User list with individual User Profile

Export in CSV filtered list of Users

Possibility to export all the data of each User to fulfill Data Subject Requests (GDPR)

Possibility to permanently delete all the data of a specific user (GDPR)

WiFi Connections logs

Troubleshooting logs and reports

Marketing and engagement

Extend the capabilities of your guest WiFi

Access Journey, to publish contents and apps before or after the Splash Page main screen

Advertising (with custom HTML pages or standard banner images)

Survey

Video advertising

Slack Connect

Social Media Marketing

Guest WiFi analytics

Monitor guest WiFi usage across multiple locations

All analytics can be filtered by Location, custom time Period and exported into a CSV

New Users (breakdown by the time of the day, day of the week, Location)

New vs. Returning users

Sign-up methods

Connections(breakdown by the time of the day, day of the week)

Active Users (Unique Connections)

Max Concurrent Connections

Average Connections per User

Splash Page Impressions (breakdown by the time of the day, day of the week, Location)

User analytics

Get an in-depth understating of WiFi users

All analytics can be filtered by Location, custom time Period and exported into a CSV file

Acquisition sources

Touchpoints and validated touch points (email and phone)

Marketing opted-in users

Breakdown by demographics (gender and age)

Breakdown by geo (country and language)

Breakdown by device (type and model)

Breakdown by operating system

Custom reports

APIs and Webhooks

Integrate into third-party systems

User profile APIs

Network inventory APIs (Access Points, Locations)

Guest WiFi Analytics APIs

Troubleshooting logs APIs

Connections logs APIs

Service configuration APIs

Webhooks

Sign-up

Login

My Apps

Publish custom web content during the login process or on the dashboard

Integrations

Seamless integration with third-party systems

Twilio (text messages sending)

SMTP (senders email customization)

PayPal (payment service)

Robokassa (payment service)

PayU (payment service)

OpenPay (payment service)

Salesforce (contact list synchronization)

MailChimp (contact list synchronization)

Slack (collaboration platform)

Service management

Simplify the guest WiFi management

Support most of the commercial WiFi Vendors

One single, cloud-based dashboard

Configuration of a customizable Email sender address

Support for international settings (33 languages, time zone settings)

Secure Cloud4Wi Dashboard login with Two-Factor Authentication

Customizable service communications

Multiple locations organized by TAG for bulk configuration operations

Multi-level management

Multi-role management and Location configuration templates

Multiple managers per account

Customizable domain of dashboard

Personalization of Cloud4Wi Dashboard login page and Logo

Subscriptions

Each Splash Subscription grants the following resources:

Access Points

Contacts

APIs

1Access Point

unlimitedContacts

100 API calls/month

APIs

Usage of APIs is subject to our fair usage policy of100 API calls/Month per Subscription. API calls are counted from calls from the Cloud4Wi REST APIs and Connectors.

For example, a customer with 100 Splash Subscription would be allowed 10,000 API calls per month

Usage of webhooks is subject to our fair usage policy of a maximum of 10 events webhooks per Contact per month.

API calls will be monitored on a monthly basis. If Clients exceed this allowance in the previous month, they can purchase additional Subscription to extend the overall limit of max API calls/month. If they do not extend the allowance, a hard threshold on the API rate will be enforced.

Product Description

Foot traffic metrics Accurately measure foot traffic to your Locations, and discover the related trends, including:

Average visit duration

Returning visitors

Attraction rate

Bounce rate

Traffic Index

Traffic metrics can be analyzed on multiple dimensions:

Custom analysis periods

Locations (single Location or all the Locations)

The main dashboard ( Behaviors )allows analyze the traffic metrics as overall counters over the analysis period or to visualize the evolution of each metric along the period.

The Customer Reports tool, instead, allows to easily compare a specific group of metrics across multiple locations.

Peak Traffic Analysis Discover the busiest day of the week and hours of the day on any custom analysis period

Distribution of foot Traffic across the hours of the day on any custom analysis periods

Distribution of foot Traffic across the days of the week on any custom analysis periods

Heatmaps Find out where visitors gather and spend most of their time on-site, and how they move within your Locations

Heatmaptimeline

Footfall timeline

Filter and analysis by gender(*)

Filter and analysis by age(*)

Zones Understand the foot traffic distribution across different areas within your location

Percentage of foot traffic in any given period that visited each zone

Distribution of foot traffic across the hours of the days and days of the weekin any given period and on each zone (available in the Peak Traffic dashboard)

Zones can be Virtual Zones (groups of proximity areas around sensors) or Polygon Zones.

Tuning Tune up the platform to adapt to your unique scenario to get more accurate results

Filtering rules to exclude fixed devices and employees form the analytics

Customization of the definition of Visit, Engaged Visit and Bounced Visits

APIs and Webhooks Feed location analytics into third-party business systems

Analytics REST APIs to extract metrics on any given period and location

Send real-time notifications to external applications when identified visitors interact within your locations (*)

Nearby location event webhook

Enter into a zone event webhook

Dashboard management Easily access and manage your insights

One single, cloud-based dashboard

Management of multiple locations

Support for multiple time zones and multiple languages

Floor plan maps management

Virtual and Polygon zones builder

Multi-level management

Role-based access management

Custom branding of the dashboard

Support for multiple WiFI and sensors vendors

* available only when bundled with Splash

Product Description

OnboardingOnboard customers via Guest WiFi

The pages content and design are customizable

Multiple sign-up methods including passwordless forms and social login are available

Options to validate each customer's phone number or email

Granular control of agreements and consent management

Contacts data managementEasily manage collected contacts profiles

Individual Contact Profile card with attributes, events, and metrics

Contact Profiles list management with search, filter and export capabilities

Contact Profile delete (GDPR compliant)

Contact Profile portable export (GDPR compliant)

Contacts analyticsGet an in-depth understanding of your customers

Breakdown by demographics (gender and age)

Breakdown by geo (country and language)

Breakdown by device (type and model)

Breakdown by operating system

Track performances of onboarding channels

Contact list growth

Identification sources

Touchpoints and validated touchpoints

Consents and subscriptions reports

Segment BuilderGroup contacts into segments filtering them with multiple conditions based on profile attributes and events

Audiences based on profile attributes and customer events

Bulk export all members of a segment

Analytics breakdown by segment

Target campaigns on segments (using Triggered Campaigns)

Triggered campaignsReach customers at the right time and place via text messages or email

Multiple channels (email and text messages)

Multiple events triggers (nearby a location, enter in a zone, dwell in a zone or in a location, leave a location, sign-in or sign-up to guest WiFi)

Use of smart content in emails and text messages

Targeted campaigns based on the Segments

Sophisticated delivery and scheduling rules

Campaigns reports

WiFi engagementEngaged customers during the guest WiFi onboarding publishing:

Workflow control by publishing before or after sign-up/in

Support of multiple native Smart Content types: Advertising, Promo Pages, Video Advertising

Allows to publish custom contents from external apps and content managers to deliver a personalized experience (using MyApps)

Smart Content Content management tools to create interactive content for your marketing campaigns, via emails, SMS or via Splash Pages

Offers

Survey

Static advertising pages

Promo Pages with a call to action feature

Video advertising

My Apps Publish custom web content during the access journey

Web SDK to facilitate development and integration

Context enrichment with customer and location attributes to deliver personalized experiences

APIsIntegrate into third-party systems

Contact profiles

Visit events logs

Connection events log

WebhooksSend real-time notifications to external systems about events

Sign-up via Guest WiFi Splash Page

Logininto Guest WiFi

Nearby location

Enter into a zone

Connectors and integrationsSeamless integrate your data and services with third-party systems

Twilio (text messages sending)

SMTP (senders email customization)

Salesforce (contact list synchronization)

MailChimp (contact list synchronization)

Slack (collaboration platform)

Service ManagementSimplify the management of your campaigns

One single, cloud-based dashboard

Multiple locations

Multi-level and role-based access management

Multiple managers per account

Personalization of the dashboard (logo, login page, domains)

Support for multiple languages and time zones

Personalized templates of service communications

GDPR Compliance

Customizable user agreements (Privacy Policy, Terms of Use, Promotional Communications)

Custom opt-in policies

Flexible data retention periods

Granular data processing control

Subscriptions

Contact Profiles

The main subscription metric of Compass is the number of Contact Profiles managed in the Client account.

The Contact Profiles metric includes every contact records managed in the account, independently from the number of attributes associated with the profile and the consents obtained by the subscriber.

Clients can manage Contact Profiles autonomously and remove any record that is not considered useful for his purposes. By deleting a record, the entire profile and history of visits and activity of the individual are erased from the account.

Note: a 3-yearSubscriptionfor a bulk of 5K Contact Profiles grants an allowance on the Account for 5K Contact Profiles at any given time. The contacts are not cumulative year over year, the 3-yearSubscriptiondoes not grant 15K X 3 contacts.

Emails

Free emails can be sent through Compass but usage is subject to our fair usage policy of a maximum of 4 emails per Contact per month.

Webhooks

Usage of webhooks is subject to our fair usage policy of a maximum of 10 events webhooks per Contact per Month.

If you need higher rate limits, please contact your sales representative.

Contact us

In most of the offices today, there is no simple and intuitive process for visitors and guests to get access to the WiFi. The first thing usually a visitor does is to check on the list of the available networks looking for something that resembles "Company Guest".

However, internal security policies might require additional checkpoints to make sure the person trying to access is authorized.Cloud4Wi offers multiple solutions to get your office guests online.

1. Standard Guest Portal

The first simple option is a dedicated SSID with a Guest Portal experience, where guests can self-register using their data. The experience is similar to the public guest WiFi experience in stores and public spaces. By using a Guest Portal instead of a simple WiFi password you can track the identity of the users accessing the network, consult reports and analytics, impose access policy and credentials expiration.

2. Guest Portal and Sponsorship validation

The second option consists in the possibility to limit the WiFi access only to the visitors authorized by a "sponsor". The sponsor can be any employee whose email has been specified by the visitors on the Guest Portal or can be a predefined email address (for example an IT administrator). More info about this feature can be found in this article.

Click here to see a demo

* tip: use your own email as the sponsor email to test the full experience.

3. Kiosk

Sometimes, the main requirements are simply to make sure that the users attempting to connect to the WiFi are actual visitors inside the office. In this case, another possibility is to have the visitors sign-up on a Kiosk and receive a One Time Password (OTP), delivered also via email, that can be used to login to the Guest Portal with their devices.

Step 1 Register on the kiosk and get the One Time Password

Click here to try the kiosk

Step 2 Connect to the WiFi and insert the One Time Password

3. Shared password

Another simple method to make sure that the users attempting to connect to the WiFi are actual visitors inside the office is to set an access password in the Guest Portal. The password can be changed periodically and can be communicated to the guests by means of signs and notices in the meeting rooms or at the reception.

The advantage of this solution versus a simple WiFi password is that the visitors still have to register, so you can track their identity and apply access policies (for example duration or assign specific VLANs) and block their access automatically after a certain expiration period.

Experimental features

At Cloud4Wi we work with hundreds of clients that feed us new ideas and use cases every day. Often, we work with them to develop new solutions before releasing them as generally available capabilities of our products. Here some of the features we are working on that might be also of your interest:

WiFi Acces with Identity Pre Shared Key: with this solution visitors can register from the Guest Portal or a Kiosk and receive an individual PSK for a specific SSID. This solution has been currently tested on Cisco Meraki network only. Interested in this use case? Contact us.

Integration with existing check-in solutions. If you already have a check-in solution in your office, we can integrate it with Cloud4Wi to automatically generate an access credential (for example an OTP) delivered to the visitors to access the guest WiFi network Interested in this use case? .

This article explains the end-user login experience when click-through login and account verification features have been enabled. These settings can be managed from Login Profiles and if you are not familiar with settings, see the following article for more information Login Profiles.

Currently, the following verification methods are available:

Verification link via email

Verification code via text message

Verification link via text message

In this example, we are going to talk about email verification and end-user journey. For any information about verification via text message, see the following article Verifying end-users' phone number using a confirmation code.

Example #1: Email verification set before the first access

We consider a Location associated with a Login Profile with Click-through login, no Registration fields, and Email verification option enabled.

First access

During the first access, the end-user needs to provide an Email address even if this information was not set under Registration fields.

Then the user is asked to confirm the provided email address.

Finally the Splash Page asks the end-user to complete the verification process.

Next access

The Email address field is asked until the verification process is completed. After this action is done, the field does not ask anything more.

Example #2: Email verification set after the first access

In this case, we consider a Location that uses Click-Through and has noRegistration fields or verification set in the corresponding Login Profile. So, the end-user can sign up without providing any data during first access.

Later, from Cloud4Wi Dashboard the Email verification option is enabled.

First access

As mentioned above, noRegistration fields or verification methods are enabled at the beginning, so end-users can sign-up without providing any additional data.

Change of configuration

After the first access, the Primary Sign-Up Verificationis set to Email. This action can be done through the Cloud4Wi Dashboard, by modifying the active Login Profile assigned to the Location.

Second access

Now the email verification option is active, but no email address was specified by the end-user during first login/registration.

If the end-user opens the Splash Page with the same device used during the first access, then Cloud4Wi recognizes the device's MAC address and retrieves the details of the end-user.

The end-user then needs to provide the Email address.

Next accesses

The Email address field is asked until the verification process is completed. After this action is done, it will not be asked anymore.

Have many access points?

Do you have many access points to insert? Read here how to import them at once from a CSV file.

An Organization Manager may need to add an access point by clicking Manage Locations in the left menu toolbar, and selecting a location by clicking its name.

Then click the Access Points tab and on the Add button.

Enter all the required information and then click on the Save button.

Please keep in mind that adding a new access point requires a set of information such as:

Name: your unique name.

Description: an optional short description, useful for displaying purposes.

Router type: you can select the type of the device or, if used, one of supported firmware.

MAC address: the MAC address.

Identifier: a unique string that allows our platform to identify the access point. For some device types, this information is not required.

Country, City, Address: geolocation data

When you have entered all the information, please click on the Save button and check that the operation gets success.

Problem

In some areas, it is possible to encounter latency problems in loading the Splash Page.This problem can be solved and the time can be significantly reduced, as explained below.

Solution

The solution is to enable the support of the CDN (Content Delivery Network) for your Tenant.The CDN is a network of nodes distributed worldwide that deliver resources closer to users. This, as already said, allows to sensibly improve performances (even more than 90% in some areas of the world!).

In order to enable the CDN, you can open a ticket in our Support Center.This operation requires whitelisting some additional domains in the walled garden of the access device used. Please check the two cases below:

Your device allows you to enter domain names into the walled garden list

Your device does not allow you to enter domain names into the walled garden list

Your device allows you to enter domain names to the walled garden list

In this case, you are strongly recommended to add the following entries:

c4wstatic.cloud4wi.com

c4wstaticjs.cloud4wi.com

Your device does not allow you to enter domain names into the walled garden

In this case, you have to add the following IP addresses:

50.18.178.180

54.248.102.194

54.246.86.254

46.137.206.166

54.232.119.5

54.253.118.101

In case your device asks you for a subnet mask (e.g. Aerohive Networks), this is 255.255.255.255 in all cases since they are single IP addresses (so, for example, you have to enter: 50.18.178.180/255.255.255.255, 54.248.102.194/255.255.255.255, etc.).

In the Dashboard brand option settings can be accessed by going to:

Manage Settings Preferences Branding.

From here, you can modify Cloud4Wi Dashboard appearance by adding custom logos and background images. Available options include:

Logo: you can upload a custom logo for your branding. We strongly recommended uploading a picture thats 120x40 pixels, since logos will be automatically resized.

Background image for Dashboard login page: you can upload a custom background image to display on the login page ( see Login page URL option below). We recommended uploading images smaller than 500 KB with 1160 width. That way, images can be properly displayed on devices with larger resolutions.

External help URL: by specifying this option, it is possible to change the default Help URL in the main menu.

Dashboard unique alias URL: by specifying this option, you can set a customized access login URL by entering an alphanumeric string. The URL is https://volare.cloud4wi.com/auth/login/entered_name. You have to enter the"entered_name" suffix.By clicking the Check button, you can see if this URL is available or not.

By setting the unlock option next to each configuration, the Organization Manager can delegate configuration controls to the location manager of each corresponding location.

On the contrary, setting the lock option will only let those at Organization Manager make changes, and the configuration option will not be visible to location managers. If all configuration options of a section are locked, then the whole section is hidden from location managers.

Location profiles define a set of rules created by the organization owner and are assigned to specific Locations. Location Managers can manage the features available and delegated to them. You can access Location profiles by opening it from the quick access toolbar on the left Manage Settings Location Profiles.

How to create a Location

Please note that organization accounts have two default location profiles that can be used when creating a new location. These profiles can be assigned based on access rights that would be provided to the location manager and these default location profiles cannot be edited.

Creating a new location profile

You can create a new template by clicking the Add button and choosing to edit templates. All changes made and saved will be applied dynamically to all locations where the template is applied.

You can assign these location profiles in the Locations section under Settings by choosing the appropriate template from the drop-down menu. For additional information on how to create a location, check out the following article: How to create a location.

A location profile template is divided into four main sections.

Login

Facebook: if this option is enabled, the Facebook Social login feature is enabled on the Location.

Twitter: if this option is enabled, the Twitter Social login feature is enabled on the Location.

Google+: if this option is enabled, the Google+ Social login feature is enabled on the Location.

Gmail: if this option is enabled, the Gmail Social login feature is enabled on the Location.

LinkedIn: if this option is enabled, the LinkedIn Social login feature is enabled on the Location.

VKontakte: if this option is enabled, the VKontakte Social login feature is enabled on the Location.

Instagram: if this option is enabled, the Instagram Social login feature is enabled on the Location.

Foursquare: if this option is enabled, the Foursquare Social login feature is enabled on the Location.

Pinterest: if this option is enabled, the Pinterest Social login feature is enabled on the Location.

Guest Wi-Fi

Add Internet plans: Allow location manager to add Internet plans (this will be applied for locations where the option "Internet Plans Domain" is set to Organization, find more information here: How to create a Location ).

Edit Internet plans: Allow location manager to edit Internet plans (this will be applied for locations where the option "Internet Plans Domain" is set toOrganization, find more information here: ).

Set default Internet Plan: Allow location manager to assign default internet plan for a location.

Generate access codes: Allow location manager to generate PIN codes for Internet access.

Manage online payments: if this option is enabled, then the location manager is able to manage paid internet plan and payment gateways.

Cloud4Wi Dashboard

By selecting Show or Hide from the drop-down, we can toggle displaying some Cloud4Wi Dashboard sections/subsections on the location manager dashboard. The available options are:

Dashboard

People

Guest WiFi

Setup

Splash Pages

Login Profiles

Internet Plans

Kiosk

Tools

Access Journey

Logs

Connections

Troubleshooting

Analytics

Guest WiFi

People

Presence

Marketing

Manage

Devices

Access Points

FogSenses

Settings

Marketplace

Preferences

Managers

Account

It is also possible to enable the location managers to perform the following options:

Add new Access Point

Add new FogSense

Settings

Upload custom stylesheet (*CSS): if this option is enabled, then the location manager is able to upload custom CSS files to be used on the Splash Page.

Manage Custom Privacy Policy: if this option is enabled, then the location manager is able to edit the Privacy Policy that is displayed during the sign-up process on the Splash Page.

Manage Custom Terms of Use: if this option is enabled, then the location manager is able to edit the Terms of Use displayed during the sign-up process on the Splash Page.

Enable Splash Page branding: if this option is enabled, then the location manager is able to use Cloud4Wi Dashboard branding options.

Use outbound Text Message: if this option is enabled, then the Outbound SMS feature is enabled on the location. The location can inherit outbound SMS text messages from the Organization.

Use Inbound Text Message: if this option is enabled, then Inbound SMS feature is enabled on the location. The location can inherit Inbound SMS text messages from the Organization.

Use the self-care Portal: if this option is enabled, then the location manager is able to activate the Self-Care option on the Splash Page during sign-up.

Have you many locations?

If you have many locations to create, please contact our support team and we'll help you to bulk upload all of them.

The APIs for creating locations are also available upon request.

When a new Location is created, the Organization Manager has administrator rights to create Splash Pages, Internet Plans and manage end-user sign-up processes. With the creation of a new Location, an account for a Location Manager is also created. This credential can be used to log in to the Cloud4Wi Dashboard and depending on the Location profile assigned, the Location Manager will be able to customize and manage the Location or will have restricted access to view certain functionalities

Before creating a new Location, please make sure to have the following information:

An access point configured to use the Splash Page (see our compatibility list here )

The "identifier" of this access point (if required, click here for explanation)

The MAC address of the access point (optional for some vendors)

You can create a new Location by clicking Manage Locations from the quick access toolbar on the left and then clicking Add. Follow the wizard and fill in all the information as described below, the data entered in this step can be subsequently modified.

Step 1 - General

The first step to creating a new Location is to provide inventory information such as:

Location details

Name: the unique name for the Location. This field is mandatory.

Business name: the name of the business which the Location belongs to. This field is optional.

Description: a short description of your Location.

Category: the merchant category which represents the Location. It is strongly recommended to set this value since some applications need this value set in order to correctly work. This field is optional.

Country: the country of the Location. This field is mandatory.

Tags: one or more keywords that describe the Location and allow you to simplify some operations (search, fast splash portal/login profile assignment operations). This field is optional.

Address: the address of the Location. This field is mandatory.

City: the city of the Location. This field is mandatory.

State/province/region: further geoLocation data of the Location. This field is mandatory.

ZIP/postal code: the ZIP or the postal code of the Location. This field is mandatory.

Time zone: defines the timezone for the Location. Recurring Internet Plans automatically reset at 00:00 AM of each day and in order to ensure that end-user is able to utilize corresponding internet plans, it is necessary to set the correct timezone. This field is mandatory

Location administration

Location Profile: indicates access rights assigned to Location Managers. See the following article for more details: Location profiles. This field is mandatory

Admin

First name: the first name of the Location Manager. This field is mandatory.

Last name: the last name of the Location Manager. This field is mandatory.

Email: the email address of the Location Manager. This field is mandatory.

Phone number: the phone number of the system user. This field is mandatory.

Send activation details by email: if the box is checked, Cloud4Wi Dashboard username and password are emailed to the specified address.

Send activation details by text message: if the box is checked, login credentials to access the Cloud4Wi Dashboard can be sent by SMS if service is active.

Location profiles

Step 2 - Services

The second step requires the configuration of basic options for the service management:

Devices: indicates the device types the Location will be supporting (Access Point, FogSense, Sensor, etc.).

Service status: indicates if the Location is currently active (Enabled) or not (Disabled).

Identity domain: indicates if end-users are provided with Internet only for the current Location (Locations) or for all the Locations under the main Organization (Organization).

Login Profile: indicates the sign-up and social login options assigned to the Location. See the following article for more details: Login Profile configuration and options. This field is mandatory.

Splash Page: identifies the Splash Page assigned to the Location. See the following article for more details: Different methods to create a Splash Page. This field is mandatory.

Internet access policies

Internet Plans Domain: indicates if the Location inherits the Internet plans from the main Organization (Organization), or has its own standalone set of Internet plans (Location). If you are choosing Location, then you can select between a set of Internet plans. Anyway, the Location Managers will be able to create or edit Internet plans, according to the settings.

Default Internet Plan: Indicates which internet plan is assigned to the Location. This field is optional.

Step 3 - Device

The third step of this guide shows how to activate the first access point in the Location. It is mandatory to add at least one access point during the creation of a Location. If you don't have the necessary access point information, choose Chillispot/Coovachilli as the hardware manufacturer, since this allows fake data to be entered for the MACService status address and the identifier field.

Name: the unique name for the access point. This field is mandatory.

Type: through this field, it is possible to select the type of device. This field is mandatory.

Description: an optional short description of the access point.

Hardware manufacturer: this field identifies the vendor or one of supported firmware. This field is mandatory.

MAC address: the MAC address belonging to the access point. This field is mandatory.

Identifier: the Identifier used by the platform to identify the access point, depending on the access point vendor, this field is optional.

Country: the country of the access point. This field is mandatory.

Address: the address of the access point. This field is mandatory.

City: the city of the access point. This field is mandatory.

State/province/region: further geoLocation data of the access point. This field is mandatory.

ZIP/postal code: the ZIP or the postal code of the access point. This field is mandatory.

The Same as Location address checkbox lets you use the same Location data provided during the first step

Go to Manage Settings Preferences from the quick access toolbar on the left to set international options.

The following options are available (some of them might not be available depending on your license):

Currency: choose the currency you want to use for the selected Location.

Default country code: choose the default international call prefix that is displayed to end-users during the registration process.

CSV separator: indicates the character that is used as a separator in all the CSV files generated. Typically this character can be "," or ";". This option is available only for the Organization and is applied to all the Locations.

Decimal mark: indicates the mark used in the Cloud4Wi Dashboard to separate the integer part from the fractional part (for example in the Analytics section). It is possible to select "." (decimal point) or "," (decimal comma). This option is available only for the Organization and is applied to all the Locations.

Default account language: indicates the default language for the Cloud4Wi Dashboard.

Default time zone: indicates the time zone to be used in the Cloud4Wi Dashboard.

Splash Page languages: indicates the languages that are available in the Splash Page management section. In order to add a new language to the Splash Page, you must add it here and then add it in the Splash Page management section, as described in Configuring the Splash Page: appearance, languages and public URLs.

Dashboard languages: indicates the languages that are available in the Cloud4Wi Dashboard.

Please note, some languages are made available through free online translation services. Then some translations may not be accurate.

In order to overcome this limitation, the Organization Manager can add a custom language to the Splash Page from scratch, or start with an existing language. This approach provides more options in the customization of the Splash Page. Please visit Configuring languages on the Splash Page for more information.

By setting the unlock option next to each configuration, the Organization Manager can delegate configuration controls to the Location Manager of each corresponding Location.

On the contrary, setting the lock option will only let those at Organization level make changes, and the configuration option will not be visible to Location Managers. If all configuration options of a section are locked, then the whole section is hidden from Location Managers.

The Cloud4Wi solution provides a bundle of integrated application modules that can be displayed and accessed by end-users on the Splash Page.

The number of applications available depends on the license purchased. Applications are managed by the organization manager through the Cloud4Wi Dashboard. There, they can:

Enable applications for each location

Configure and manage applications

The organization manager can directly manage applications for each location or delegate this job to the location manager. To view available applications, click on the quick access toolbar on the left Manage Apps All.

Managing your applications

Configuring applications can be managed by organization managers or delegated to location managers. But keep in mind, it is not an all or nothing situation. Only some applications can be delegated to location managers while others can remain in the control of organization managers. If delegation option is available, it can be configured by clicking on the top right corner of the application. This opens a drop-down and you can choose Settings.

Access Journey

Some applications by default are available at both organization and location level. Organization managers can choose whether or not they want to provide access to location managers. For example - the Advertising app is available at both organization and location level by default. If the organization manager wants to either enable or disable the Advertising app for the location manager, then he or she has to go to the Location section, open the Apps tab, and click manage the app. Delegating this app using the drop-down menu mentioned earlier is not an option.

Setting access policies

By clicking the Settings button for any application, organization managers can indicate who can configure the app. Possible choices are:

Owned by organization, same for all locations: only the organization manager can configure the application. Location managersdon'thave access to configure or edit the app. The configuration Setting is applied to all locations managed by the organization manager. In this case, only the organization manager is able to uninstall the application.

Owned by organization, different for each location: Configuration settings are different for each location. The app is managed by the organization manager, and he or she has to open the Apps tab in the Location section, select the desired Location, and then click manage the app. Only the organization manager can configure the application and location managersdon'thave access to configure or edit the app.

Owned and managed by location manager: Both organization manager and the location manager will be able to configure the applications. The location manager can do this by accessing the toolbar on the left Manage Apps, but the organization manager has to open the Apps tab in the Location section, for the desired Location and then click manage the app. This app can be removed and managed on both levels.

Adding to sidebar / Removing from sidebar

For some applications, at Organization level, you can find Add to sidebar or Remove from sidebar in the marketplace. This allows you to add (or remove) the link to an app to the (from) the sidebar and improve your user experience for frequently-used apps. If you click the Add to sidebar link, you will be asked the sidebar section where you want to move your application. You can choose between:

Guest Wi-Fi

Analytics

Marketing

Manage

Please note: if the application is enabled at Location level, then locations owners will also display the link in the sidebar

List of applications

On the main screen, you will see All at the top right corner. This filters and displays all licensed applications available for your Organization/Location by category.

All

Marketing

Analytics

Guest Wi-Fi

Integrations

Dev Suite

Installing an application

On the top part of this section you can filter installed applications by their category:

All - lists all applications licensed to the account

Installed - lists only the applications that have been installed

To install a new app, choose the app from the All section and click on the Install button, you can install the selected application and move it to the Installed page.

Applications can be removed by clicking on the top right corner of the application. This opens a drop-down menu from which you can choose remove. This option is available depending on the application and not all applications can be removed. Uninstalling an app can be delegated to organization managers or location managers, depending on who has the rights to. Uninstalled applications can be reinstalled again at a later time.

Getting more info

By clicking on info, you can see a detailed description of the application.

Access Journey

Please find more information in this article: .

Display options

You can change the details regarding how the application is displayed on the Splash Page. To do this, you must open the desired application by clicking on the icon of the application and then clicking on the Settings button.

Once inside the application, you must set the following fields:

Icon: this is the application icon displayed within the App Bar on the Splash Page.

Pre-authentication: this indicates whether the application is visible and can be used when the end-user is not authenticated.

Changing the name of an application

To change the name of an application on the Splash Page, you must create a custom Splash Page language. From there, you can modify application names. Using the same process, you can change application names for all languages supported by the Splash Page.

When you log in to the Cloud4Wi Dashboard with your manager account for the first time, you are required to accept the terms of use before doing anything else.

After this step, you are asked to change your password for security reasons. Our requirementsfor a new password is to be at least 8 characters long and include at least one uppercase letter, one lowercase letter, one number and at least one special character from the following characters: @ :, . - _ ( ) = ' + [ ] # ?

This step can be skipped but you'll be asked again until you don't change this password

Finally, you'll be asked to confirm your personal data and, if you are the administrator of your organization instance (if you are able to create other manager accounts), also organization data.You also may decide to accept to receive electronic communications from Cloud4Wi.

The System Manager is a user who has access to the Cloud4Wi Dashboard and has full or limited access depending on the role defined while creating the account. To access the Managers section, click on the quick access toolbar on the left Manage Settings Managers. From here you can manage existing users or add a new user.

An Organization Manager is able to see all System Managers of the Organization and is also able to view the Location Managers of a particular Location by getting down to the Location level.

A Location Manager is able to see all Location Managers that are registered to the same Location.

Each Organization/Location can contain at least one manager with "admin" rights, who is the only one having the ability to create new System Managers in the platform. The system Managers created hereafter are able to access the platform according to their role, but they are not "Admin" and they cannot create new System Managers. You can view a table showing all System Managers and their roles:

Username: the username for the end-user

Name: the full name of the end-user (first and last name)

Role: A set of privileges allocated to the end-user.

Admin: this field indicates if the manager is able to create and delete other users. Usually, the "admin" is the first manager created in an Organization/Location instance.

By clicking on the single System Manager, you can view the following information:

First Name

Last Name

Phone number

Email

Username

Role

and you can perform the following actions:

Lock / Unlock: allows you to disable the selected System Manager account without having to delete it. By clicking on the Unlock button you can enable access.

Edit: allows you to update the previously entered data.

Reset password: allows you to reset the password to access the Cloud4Wi Dashboard.

Delete: allows you to permanently delete the selected System Manager. This action is available if the logged system user is "Admin".

If you have many Managers in a single instance, it is possible to use the search filter to refine your results.

As already mentioned, "admins" can create new users. During this process, the following information is required:

First Name

Last Name

Phone number

Email

Role

Send activation details by email: a notification e-mail to the provided e-mail address, including the access credentials for the Cloud4Wi Dashboard. The email does not need to be sent.

Send activation details by text message: a notification text message to the phone number including the access credentials for the Cloud4Wi Dashboard. The text message does not need to be sent.

First access

Please read First-time login to the Cloud4Wi Dashboard to learn more about the first access of a System Manager to the Cloud4Wi Dashboard.

System Manager roles

Currently, the following available roles are:

Full: This role has full access to all the sections (the "classic" System Manager).

Analysis: this role only has access to Analytics.

Applications: this role only has access to Applications.

Provisioning: this role can access the following sections: Dashboard, Users, Guest Wi-Fi and Manage.

Marketing: this role can access the following sections: Dashboard, Analytics, Apps, Splash Page.

Customers: this role can only access the Users section.

The Dashboard is the first screen you see when you log into the Cloud4Wi Dashboard. In order to access this section from anywhere else in the Cloud4Wi Dashboard, click on the Dashboard button in the quick access toolbar.

Please note, the widgets displayed in the Dashboard depend on the access rights of the account manager and each manager has his/her view of the dashboard. If an organization manager descends to the location level, he/she will be able to see the data from the location on the dashboard.

The default view of the dashboard presents data gathered over the Last 7 days, with the option to change and view data collected over the Last 30 days or Last 90 days. For certain widgets, the Manager will see a comparison of data with the previous 7, 30 or 90 days depending on which dropdown option selected. These data point to the widgets will be noted as a percentage, comparing the last 7, 30 or 90 days with the previous 7, 30 or 90 days.

The following widgets are displayed with the result of data gathered over the Last 7 days. The view of some widgets can vary based on the access rights starting from MSP Owner (view of organizations managed), Organization Manager (view of locations managed) and Location Manager (view of access points).

Connected Users: this is a line chart reporting how many end-users successfully authenticated through the Splash Page and how many of them are connected once (New User)/multiple times (returning user).

New Users: the number of end-users who register on the service.

User Loyalty: the percentage of end-users who logged in more than once.

Busiest Day of the Week: identifies the busiest day of the week based on the number of connections.

Busiest Time of the Day: identifies the busiest time of the day based on the number of connections.

Max Online Users: the maximum number of simultaneous Internet connections in a particular Organization account (for MSP Owners) or Location (for Organization Managers).

Users Online Now: identifies the number of users that are currently active

Average Time Online: The average time users were online.

Sign-up: The percentage of registered end-users organized by their account type (e.g. based on username/password, Click-through, Facebook, Twitter, Google+, LinkedIn etc.)

Demographics: Age and gender distribution:

<20

21-35

36-40

41-50

>50

Devices: This chart indicates the distribution of end-user device type (e.g. Android, iOS, Windows etc).

Connection Map: general user clusters when connected.

Overview: Depending on your user access, this section will display a different chart

MSP Owner: summary of the total number of organizations, locations, access points, and beacons.

Organization Manager: summary of the total number of locations, access points, and beacons.

Location Manager: summary of the total number of access points.

Top Organizations/Locations/Access Points: based on system user access the chart will provide a summary of top organizations (for MSP Owner) based on the usage in the specific MSP account. When viewed as Organization Manager, it provides an overview of top locations based on usage in the specific organization account. When viewed from location this would provide information of top access points based on the number of connection.

The General Data Protection Regulation (GDPR) affects European and non-European businesses targeting users in the European economic area.

At Cloud4Wi we've always been strong advocates of privacy and we had since 2014 all the features and options in the Splash Pages to be compliant with the privacy regulations.

1. Collectconsent

The main legal basis for collecting and processing your users personal data is consent. Cloud4Wi products include many features and capabilities that allow us to serve global brands. It is your responsibility to make sure you configure the service in compliance with GDPR and we are here to help you in this process.

The Privacy Policy has to be accepted explicitly. Acceptance checkboxes cannot be pre-checked. Log in to your account and check the settings of the active login profile and:

make sure you selected the option to get an explicit acceptance of the Terms ofUse andPrivacy Policies.

if you are collecting the data for promotional communications, make sure toselect the opt-in consent mode

[email protected]

As part of the options, you can also decide to split the consentfor the Privacy Policy and the Terms of Use.

2. Update your Privacy Policy

We provide a solution for our customers to operate their own service. In this scenario, Cloud4Wi operates as a Data Processor, while our customer operates as a Data Controller. Its essential that our terms and our customers terms reflect this. The user of the WiFi hotspots must also be made aware of the role of Cloud4Wi and our customers. It is essential that you review your own privacy policy and make sure it reflects GDPR needs and benefits.

In the Login Profile, you can customize your Privacy Policy text, even in multiple languages.

New accounts come with a default Privacy Policy template, but you are required to reviewand personalize it.

3. Identify the users

Visitors should be identifiable as they have the right to reach you out with subject access requests, asking to retrieve thedata you hold about them or to delete their personal data. To that extent, it is important to collect enough data about users to permit their identification, for example, their email, social network or phone number.

In the Login Profile, you have full control over what type of data tocollect from the users.

If you want to be even more certain that you collect a valid contact point of your users, you can activate the options to validate the email and/or the phone number.

4. Update your company contacts

As controller of your customer data, it is important that your customers know who is controlling their data and how to contact you. To make it even more explicit and at the same time to facilitate your compliance with CAN-SPAM and CASL regulations, we added aSendersection in thePreferencespage where you can set the company data that will be appended in the footer of every email to inform your users who is the provider of the service. By default, the footer will be configured using the data from your Account page.

In the same page, you can also add a custom default message that will be appended to all email communication, where you can better explain why your users are receiving that email and eventually how to reach you.

By personalizing the email address from which the emails are sent, your customer can better identifywho is sending the emails to them.

When using Cloud4Wi default SMTP service, you canconfigure your e-mail address as the default sender for your messages in theSendersection into thePreferencespage, underConfigure your default email settings.If you use your own SMTP, this option is not available since you can customize this parameter directly on your SMTP server configuration.

The procedure requires you to validate theemail address you chose in order to avoid spam filters; we are going to explain it step by step. Check here the full user guide.

Read our Data Processing Agreement

To comply with the new laws, added a Data Processing Addendum (DPA) to our Terms of Service and updated our Customer Terms of Service to reflect the new requirements.We encourage you to review them.

If you would like a countersigned copy, please contact our team and

You can view and manage your organization account data by going to Manage Account.

This page consists of the following sections:

Details

Licenses

Data and privacy

Details

This section is read-only and contains the details of your Organization or Location.

Licenses

This section displays the details of the license constraints assigned to the Organization or Location.The following items are available:

Services

Number of Locations: this item is available only for the Organization. The two values displayed refer to the number of Locations currently present, and the maximum number of Locations allowed in the system. If the first number is not lesser than the second one, no further Locations cannot be created in the system.

Number of Access Points: the two values displayed refer to the number of Access Points currently present, and the maximum number of Access Points allowed in the system. If the first number is not lesser than the second one, no further Access Points for any Location cannot be created in the system.

Number of Fogsenses: the two values displayed refer to the number of Fogsenses currently present, and the maximum number of Access Points Fogsenses in the system. If the first number is not lesser than the second one, no further Access Points for any Location cannot be created in the system.

Number of Registered Users: the two values displayed refer to the number of end-users currently registered, and the maximum number of end-users allowed in the system. If the first number is not lesser than the second one, end-users will be not able to register to the service, and the Organizations or the Location Managers will be not able to add new end-users from the Cloud4Wi Dashboard.

Max. Online Users: the two values displayed refer to the maximum number of end-users that have been simultaneously online in the system, since the time of the first setup of the Solution, and to the maximum number of simultaneously online end-users allowed in the system. At any time, it is not possible to have any number of simultaneously online end-users higher than the one indicated by the second number.

Communications

Internal Outbound text message: the two values displayed refer to the number of text messages sent to all end-users (since the time of the first set-up of Cloud4Wi, and the maximum number of text messages that it is possible to send. If the first number is not lesser than the second one, Cloud4Wi will not send any text message to end-users, until a new SMS recharge is performed.

Internal Inbound text/call: the two values displayed refer to the number of text messages or phone calls performed by end-users to confirm their registrations, and the maximum number of text messages and phone calls allowed. If the first number is not lesser than the second one, Cloud4Wi will not confirm further registrations performed by the end-users via text message or phone call, until a new SMS recharge.

By clicking View details, the Tenant is redirected to a page where it is possible to see statistics about communications. The information displayed are:

Email

Outbound SMS

Inbound SMS/Call

It is possible to view the results for all Venues, or only a particular Venue, and view the results for the following time intervals:

Today

Yesterday

Last seven days

Current month

Last month

Last six months

Current year

Last year

Data and privacy

This section makes possible to enable the following options:

Prevent provider support from viewing this organization: by checking this option, Cloud4Wi Team won't be able to do any action in the Cloud4Wi Dashboard behalf of your Organization. Please note that it may be an option to temporarily uncheck this if you are sending a support request to Cloud4Wi Team

Exclude unknown user data from analytics calculation: by checking this option, unknown users will be excluded from any calculation on our Analytics

As controller of your customer data, it is important that your customers can identify your brand as the controller of the service. To make it even more explicit and at the same time to facilitate your compliance with CAN-SPAM and CASL regulations, you can find the Sender section into the Preferences page.

In this article, we specifically deal with the Contacts and Transparency section of this page. If you are looking for how to configure the sender of your emails, please read the following article: Senders configure the sender of your emails.

Under Contacts and Transparency:

in the input field above, you can set the company data that will be appended to the footer of every email to inform your users who is the provider of the service.You are strongly recommended to configure this field. If you didn't do that, the footer will be filled with the data configured in the Account page, but you also will see a warning message on the Cloud4Wi Dashboard asking you to configure the Senders section.

in the input field below, you can add a custom default message that will be appended to all email communication, where you can better explain why your users are receiving that email and eventually how to reach you (e.g. You are receiving this message because you registered to our Guest WiFi Service).

As controller of your customer data, it is important that your customers can identify your organization as the controller of the service. By personalizing the email address from which the emails are sent, your customer can better identifywho is sending the emails to them.

When using Cloud4Wi default SMTP service, you canconfigure your e-mail address as the default sender for your messages in the Sender section into the Preferences page, under Configure your default email settings. If you use your own SMTP, this option is not available since you can customize this parameter directly on your SMTP server configuration.

The procedure requires you to validate theemail address you chose in order to avoid spam filters; we are going to explain it step by step.

Step #1: Make sure you are using Cloud4Wi SMTP

Go to Manage Settings Preferences, open the Gateways tab and make sure that in SMTP Provider Lists "Default" settings are configured (e.g. Default - Cloud4wi<[email protected]>).If you configured your custom SMTP settings in this field, then you won't be able to go ahead with this procedure.

Step #2: set up your custom sender data

Go to Manage Settings Preferences, open the Senders tab, go to the Configure your default email settings section and click on Change. Then provide the name and e-mail address of your sender and click on Send verification link.

Step #3: go to your mailbox and click on the validation link

Enter your mailbox and find a message coming from "Amazon Web Services". Then click on the validation link and check the confirmation message from Amazon SES.Please note that the validity of this link expires after 24 hours, so you will need to restart from step #1 if your link is expired.

Step #4: confirm your e-mail data

Go back to the Configure your default email settings section and click on Confirm email validated. If you see the message Congratulations! your mail has been verified., then you're done.

Note: please remember that if you configured your SMTP data in some applications (such as Triggered campaigns or Email Marketing), these data will override any setting defined in the Senders section.

Cloud4Wi Dashboard provides you an with an extra layer of protection, besides passwords.If you enable the two-factor authentication on your organization instance, your managers will be asked first for their password and then, as a second step, they will have to provide an extra code.

What do I need to enable the two-factor authentication?

First of all, you need a Cloud4Wi manager account (Dashboard account). The two-factor authentication is supported for organization and location managers.Cloud4Wi relies on Google Authenticator application for generating verification codes. So you also need a Google account and you need to install theGoogle Authenticator application on your mobile device.

How does it work in detail?

If you are a Cloud4Wi account manager:

Enter your username and password for the Dashboard

You'll be asked for a verification code. To get this code, you have to open the "Google Authenticator" application on your mobile phone. If you don't want to enter the code each time you log in, just check the option Trust this device for 30 days (see the note below)

If everything is correct, you'll be authenticated

Note: the option Trust this device for 30 days will not work if you log in from a different browser than the first time, or if you frequently clear your browser cookies.

open a ticket

How can I enable the two-factor authentication?

To enable the two-factor authentication for your account, click on the quick access toolbar on the left Manage Settings Managers. From this page, find your account username (the username must correspond to the one you entered on login) and click on it. Finally, find the Enable button and click on it.If you cannot find the Enable button, make sure that the username corresponds to the username you used on login. Otherwise, in our Support Center.

If you are "admin" (and so you are able to create new managers in your instance), you can also enforce your managers to use the two-factor authentication.In this case, you will see the Enable button in the page of all the managers (not only for your account). Just click it and enable this feature also for them.

Once you click on the Enable button, you need to complete the following steps before finalizing the procedure:

Make sure you have the "Google Authenticator" application installed on your mobile device. If you are enabling the two-factor authentication for another manager, make sure that he also has this application installed and available

Open the "Google Authenticator" application, then scan the QR code or manually enter the alphanumeric code displayed in the Dashboard. If you are enabling the two-factor authentication for another manager, provide the owner of the mobile device with this alphanumeric code

Save the backup code displayed somewhere safe. It will allow you to log in even if you lose your mobile device (see the related paragraph below). If you are enabling the two-factor authentication for another manager, provide him with this code

Read the six-digit numerical passcode on your mobile device (or in the mobile device of the manager) and enter it into the Dashboard

Check that everything went well. The two-factor authentication is now enabled on the desired account

How does the backup code work?

If you lose your device with Google Authenticator, then you can use the backup code to access your account instead of the Google Authenticator code. This code works like the temporary code, but it will also disable the two-factor authentication for your Cloud4Wi account, so you will need to re-enable it from scratch.

I clicked the option "Trust this device for 30 days", but I am still required for the code. Why?

This happens when you log in from a different browser, or if you recently cleared your cookies.

If you are using Splash or Compass and you are dealing with a massive deployment, you may need to add many access points or update the information. To make it easier, we added the possibility to do this for 100 access points at once, by uploading a CSV file.

Import

Click Manage Access Points in the left menu toolbar, then click Manage and select IMPORT FROM FILE from the dropdown menu.In the resulting modal window, select your hardware manufacturer, and download the related template. You can enter up to 100 entries in your CSV file.

Please find below the structure of available templates:

Name

Description

Location

MAC address

Identifier

SSID

Template 1

required

optional

required

required

required

-

Template 2

required

optional

required

required

-

optional

Template 3

required

optional

required

required

-

-

Data format:

Name: only letters, digits, colons, dots, hyphens, spaces, and underscores

Description: only letters, digits, colons, dots, hyphens, and underscores

Location: the name of an existing location in your instance

MAC address: 12 hex digits, no colons or hyphens (e.g., 0123456789ab)

Identifier: only letters, digits, colons, dots, hyphens, and underscores

SSID: only letters, digits, colons, dots, hyphens, and underscores

Notes:

When you upload a CSV file, you assume that the hardware manufacturer is the one selected in the modal window

Importing different hardware manufacturers may require different templates. Please make sure you are using a suitable one for your use case

After the file is uploaded, the platform checks all the provided values. If all of them are valid, then the access points are copied.Otherwise, the platform does not import any entry (not even valid ones), and the page returns you a CSV file containing the list of the errors that occurred. So you will need to change your CSV file with the required changes and import it again.

Update

Click Manage Access Points in the left menu toolbar, then click Manage and select UPDATE FROM FILE from the dropdown menu.In the resulting modal window, download the related template. You can enter up to 100 entries in your CSV file.

You are required to provide the following information: Name, Description, Location, MAC address, and Identifier.So, for each row, enter the Identifier of the access point that you want to modify (since this field is unique in the platform). You can find this value in Manage Access Points (see the picture below).Then, in the same row, enter the desired values for the remaining fields (Name, Description, Location, MAC address).

Note: For any access point, you can provide a Location different from the current one. In this case, if you confirm your action, the access point will be deleted from the old Location and inserted again into the new one.

The Third-Party Software components that are incorporated into the Cloud4wi Products at this time are listed below. As Cloud4wi will keep updating, enhancing and maintaining the SoftwareProducts by issuing revisions or new versions of the Software Products, the updated list of Third-Party Software components will be updated.

Nginx

Php-fpm

freeradius

Jradius

Java JDK

dbus-java

log4j

Apache Tomcat

Spring

Hibernate

Php

cakephp

Jquery

JQuery Flot

Openx Market

Swagger

Jcrop

DateRangePicker

Jquery Flexslider

Bootstrap

Jquery Datatable

Select2js

Bootstrap

Bootmetro

Nodejs

Angularjs

Moderniser

Font-awesome

Customiser

google-charts

MySQL

MongoDB

redis-server

Spark

Hadoop

Elastic

d3js

We have a portfolio of different support services based on our customer various needs. Our support team is a group of highly knowledgeable and experienced specialists that are ready to keep our customers connected and operational.

Cloud4Wi support includes:

Technical documentation and FAQ

C4W community

Software upgrades and updates

Ticket-based support

Business hours telephone support (CET time).

Contact support

Submit a ticket

Telephone support

+39 050 7916786

SECURITY TOOLS

Last Updated: June 3, 2015

Cloud4Wi offers a number of tools for administrators to maximize the security of their network deployments. Use of these tools provides optimal protection, visibility, and control over your access to the Cloud4Wi Platform. This page contains information about how to quickly and easily increase the security of your Cloud4Wi Accounts.

1. CREATION OF A PASSWORD

At the first access to the Cloud4Wi Platform, the System User is requested to change the password received via email or text message.

The new password has to be created according to the following criteria:

It has to be at least 8 characters

It has to include 1 uppercase, 1 lowercase, 1 number and 1 special character (@.,:;-_()=?'+[]#!).

After the password change, the Cloud4Wi Platform logouts the System User.

2. STORAGE OF A PASSWORD

The password is encrypted before it is stored on the Cloud4Wi Platform. An encrypted password cannot be reverse-engineered to reveal the real password.

3. RECOVERY OF A PASSWORD

A password can be recovered in two different ways:

The System Admin can reset the password on behalf of another System User. The System User will receive the new password via email or text message.

The System User can reset the password before logging in to the Cloud4Wi Platform.

4. LOCK SYSTEM USERS

The System Admin can lock or unlock the other System Users.

5. LOGS

The Cloud4Wi Platform logs all System Users activities (e.g. login, add or edit entities), including the IP Address of the used device.

6. VERIFY SSL CERTIFICATES

The System User can access to the Cloud4Wi Platform only via https. This ensures that all communications between the System Users and Cloud4wi Platform are encrypted.

7. IDLE TIMEOUT

The Cloud4wi Platform has an idle timeout of 300 seconds. After 300 seconds of inactivity, the Cloud4Wi Platform logouts the System User.