Pages

This document describes where and how the Frosmo Platform stores its operational data: data collected from websites, data generated based on the collected data, configuration data managed in the Frosmo Control Panel, and any other data required to operate the platform.

If you're looking for:

Data stored in the Frosmo back end

The Frosmo Platform stores its operational 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:

  • Master

    The Master database stores all the operational data that is displayed or managed in the Frosmo Control Panel. The data can be broadly grouped into:

    • Company settings (including target groups)
    • Site-specific data
    • User account settings

    The site-specific data includes:

    • Analytics data (reports)
    • Configuration data, for example:

      • Conversion definitions
      • Modifications
      • Placements
      • Recommendation configurations and recommendation data
      • Segments and segment groups
      • Triggers
    • Usage data collected from sites:

      • Modification performance data (events and metrics)
      • Product data
      • Visitor data

    The data in the Master database is stored for the duration of the customer's subscription agreement. The data is removed manually.

  • Elasticsearch

    The Elasticsearch database stores error data from across the Frosmo Platform, from both the front end and the back end. The error data is used for monitoring and debugging purposes. The database uses the server access logs as its source, so it can contain the same data as the access logs. In addition, for sites that use the data layer, the database can contain personal data retrieved from the data layer.

    The data in the Elasticsearch database is stored for 31 days, after which it is automatically removed.

  • Reporting

    The Reporting database stores aggregate data required to generate analytics reports, such as conversion reports, modification reports, and segment reports, and to display advanced tracking statistics. The data is parsed from other sources, so the database does not contain any data that is not stored elsewhere in the Frosmo Platform. If not combined with other data, the data in the Reporting database cannot be used to identify a data subject.

    The data in the Reporting database is stored for the duration of the customer's subscription agreement. The data is removed manually.

  • Requests

    The Requests database stores information about Message API calls that return modification content for display. The purpose of the database is to keep a record of what content has been returned to which visitor on which site. However, the database does not track whether the content is actually displayed. The Message API also uses this data to decide what content to return to a particular visitor, or whether to return any content.

    The data retention period depends on the modification. If the modification hasn't been updated or displayed for 90 days, its request data is automatically removed.

Data stored in the visitor's 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

Additional data stored through APIs

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

  • Custom APIs

    A custom API is a customer-specific API created for a specialized purpose that cannot be realized using standard Frosmo Platform features. A custom API can in principle collect and store any data from a site.

  • Context API

    The Context API stores and retrieves visitor context data to and from Frosmo servers. The API uses a Redis database on the regional platform server that services a site.

    The Context API is mainly used for storing context data on Apple devices. By default, the Frosmo JavaScript library stores a visitor's context in the browser's local storage. However, if you need to support shared context in the Safari browser on Apple devices, the library must access the context from a Frosmo server instead, which is where the API comes in. (Safari does not accept cookies or local storage data from websites the visitor has not visited, which is what the shared context basically is.)