This guide describes the data collected by the Frosmo Platform from customer websites, and where that data is stored in the visitor's browser and in the Frosmo back end.

For information about how Frosmo collects and stores data from its own websites and user interfaces, see Frosmo Privacy Policy.

Collecting data

The Frosmo JavaScript library collects usage data in the visitor's browser and sends the data to the Frosmo back end over an HTTPS connection. The library sends the data in the background so as not to interfere with the visitor's user experience. The Frosmo JavaScript library also stores selected data locally in the browser.

The data can be categorized into:

By default, the Frosmo Platform collects and processes only anonymous and pseudonymous information about visitors and their behavior on a website. The platform does not collect data that in itself enables the identification of an individual data subject.

The Frosmo Platform can collect additional information about visitors, including account data, such as email addresses and phone numbers. However, the processing of such data must always be determined by the customer and explicitly documented. Frosmo only collects account data for the purpose of transferring the data to the customer's back end systems or third-party systems controlled by the customer, such as customer relationship management (CRM) systems or marketing automation systems.

Modification performance data

The Frosmo Platform automatically tracks (counts) the following basic events for a modification:

The platform only counts one basic event of each type per modification per page load. That is, a modification can only get a single click, a single display, and a single true display per page load, regardless of how many times the visitor actually clicks or views the modification before reloading the page or navigating to another page.

In addition to the basic events, the Frosmo Platform also tracks (counts) the following performance-related events for a modification:

The Frosmo Platform does not automatically track conversions and custom events, so you need to implement their tracking separately. Your Frosmo team usually does this for you, based on your requirements and specifications.

The Frosmo Platform tracks basic events, conversions, and custom events separately for each variation of a modification.

Based on the basic event and conversion counts, the Frosmo Platform automatically calculates the following basic performance metrics for a modification:

For more information about modifications in general and modification statistics in particular, see Modifications and Modification statistics.

Product data

Product tracking is the process of automatically collecting product data from a website. Product tracking has to be manually set up for each site either by Frosmo in the custom code or by the customer through the data layer in the site code. The collected data is mainly used in product recommendations.

Product data can include several attributes, such as:

The Frosmo Platform can track product views and purchases separately for each visitor. Product data as such does not contain personal data.

Server logs

Server logs are files for recording events on a web server, namely information about incoming page requests. Website visitors do not have access to logs; the logs are normally only accessible to the webmaster. The data in the logs is only used for the technical monitoring of the platform, not for profiling, targeting visitors, or any commercial purposes.

The logs can be divided into the following types:

If a third-party cookie is used on a site, its content is also logged. For more information about cookies, see Cookies.

In addition, the server may store logs from applications handling requests for the web server. These logs may contain data stored in the Frosmo back end, but they do not contain any data that is not stored elsewhere in the Frosmo Platform.

The log data is used to create usage statistics. Before refining the data for statistics, any personal data, such as IP addresses, is removed.

By default, the logs are stored for six months, after which they are automatically removed.

Visitor data

The Frosmo Platform tracks the following data about a visitor on a website:

Storing data

For more information about what data is stored and where, see:

Data stored in the browser

In addition to sending data to the Frosmo back end, the Frosmo JavaScript library stores data in the browser's local storage and cookies.

None of the library's core features require the use of cookies, so storing data in cookies can be disabled, if necessary. Local storage, in turn, is a safe way to manage data, since web servers do not have access to it.

Local storage

Using local storage means that the data is stored in the visitor's browser.

Local storage is used for most of the data that is not sent to the Frosmo back end and also for some data that is sent to the back end. Depending on the website, the Frosmo JavaScript library can use either the site's default, origin-specific local storage or, if data needs to be shared between multiple origins, a cross-origin local storage implemented using an iframe, also known as a shared context, associated with the Frosmo domain. A common example of the latter is a site that uses both HTTP and HTTPS to deliver a service. This requires data to be shared between two origins. Using a shared context allows the origins to be treated as one and the same, which in turn allows the data to be stored only once and the visitor to be treated as a single user within the service.

The following table lists the data stored in local storage by the Frosmo Platform.

Table: Data stored in local storage

Data itemLocal storage keyDescriptionRetention period
Local Frosmo ID__frosmoeasy__uid

Used to identify the visitor (browser) on the Frosmo Platform in order to retrieve visitor-related data from the Frosmo back end. The ID is unique within a site.

The ID is generated from the browser's user agent string and does not contain any personal data that can be used as such to identify the visitor.

Indefinitely unless manually removed
Context__frosmoeasy__contextUsed by the Frosmo Platform for personalization. The context holds data for segments, page visit history, location, and other data gathered from visitor activity on the site. By default, the context does not contain any personal data that can be used as such to identify the visitor.Indefinitely unless manually removed

Cookies

A cookie is a small piece of data sent from a website and stored in the visitor's browser while the visitor is browsing. Cookies are used, for example, to store temporary information or to track the visitor's browsing behavior.

The following table lists the data stored in cookies by the Frosmo Platform. In addition, Frosmo can create custom cookies for specific situations and needs, such as campaigns, but these are not a part of the basic cookie package described in the table.

Table: Data stored in cookies

Data itemCookie nameDescriptionRetention period
First-party cookies
Keywordsfrosmo_keywords

Used by the Frosmo Platform to store the IDs of the target groups to which the visitor (browser) currently belongs.

This cookie is set only when the visitor belongs to one or more target groups. If the visitor is removed from all target groups, the cookie is deleted.

30 days
Quick contextfrosmo_quickContext

Data needed for modifications whose content is preloaded. The data includes, for example:

  • Local Frosmo ID
  • Segment data

This cookie is set only when the site uses modifications whose content is preloaded.

365 days
Frosmo offfrosmo-offUsed when the Frosmo Platform is disabled for the site on the visitor's browser.Session
Local Frosmo IDfrosmo_uid

Used to identify the visitor (browser) on the Frosmo Platform in order to retrieve visitor-related data from the Frosmo back end. The ID is unique within a site.

The ID is generated from the browser's user agent string and does not contain any personal data that can be used as such to identify the visitor.

This cookie is only used on Apple devices when the additional configuration option easy.config.contextApi is enabled.


1 year
Frosmo Previewfrosmo_preview_tool

Used by Frosmo Preview to check whether the visitor has the application open. If the visitor had the application open on the previous page or before a page reload, the application opens automatically after the current page loads.

This cookie is set only when the visitor, who is also a logged-in user of the Frosmo Control Panel, has Frosmo Preview open on the site.

Session
Third-party cookies
Global Frosmo IDid

Used to identify the visitor (browser) across different domains and websites.

The ID does not contain any personal data that can be used as such to identify the visitor.

31 years and 1 month

Data stored in the Frosmo back end

The Frosmo Platform stores its operational data – both the data that it collects from sites and the data that it generates from the collected data – in different databases in the Frosmo back end. In addition to main databases that are used across the platform, the platform also uses dedicated Redis databases (one per customer) for storing data related to custom features.

The Frosmo back end contains the following main databases:

API implementations

The Frosmo Platform can collect and store data through the following APIs: