Cookie policy
Apella (hereafter – Apella) uses cookies in order to improve the functionality of its official website www.apella.lv (hereafter – the site), enhance its user-friendliness and maintain efficiency of the user experience. By using the site you agree to the placement of cookies on your device.
What is a Cookie?
A cookie is a small data file stored on a user’s device in a process of browsing a particular website. Note that Apella gathers anonymous cookie data which is not intended to identify a user; therefore, the use of cookies does not imply processing of the personal data by Apella.
How do we Use Cookies?
Apella processes cookies for the following purposes:
- to remember the parts of site visited by the user to provide engaging content for the site visitors and further disclose issues that are topical for the users;
- to provide the smooth browsing experience for visitors by verifying and ensuring compatibility of the site with the device and browser version;
- to maintain the statistics on how often the users visit certain parts of the site, the data is implemented by developers of the site to tailor its usability and enhance the performance.
Apella is not going to use cookies for any purpose other than stated above.
What Types of Cookies are Used by Apella?
Regarding the lifespan, Apella uses the following cookies:
- Session cookies, or transient cookies, are erased as soon as the user shuts the browser down after accessing its content. The session cookies remember what the visitor has chosen on a previous page to avoid repeated input of information during the session. Apella uses session cookies in order to authenticate the user on the site, providing the browsing session to a site visitor.
- Permanent (persistent) cookies, are saved on the user’s end device to recognize his or her browser sessions and to know if there was any contact between the user’s device and us before, and to identify the most popular sections of the site to offer more efficient user experience and ensure the device compatibility. For this scope of services, the processor gathers such information as device brand (producer), its interface language, browser data and an operational system data.
Mandatory cookies
These cookies are necessary for the user to safely and freely browse the website, correctly interact with the functions of the website, acquire the information desired and submit applications. These cookies are also necessary for the user to save the choice related to the use of the website (language, consent to use cookies, etc.). Without these cookies the website cannot work fully, i.e. the content of the website may be displayed incorrectly for the user or the functions of the website may not work. They are automatically saved on the user’s device, which allows to view the website requested by the user. Cookies collect technical data about the visitor’s device, but they do not identify the user, nor do they collect and summarise the information. Necessary cookies are stored on the user’s device until the cookie fulfils its function, but no longer than two years.
| Cookie name | Default expiration time | Description |
|---|---|---|
| PHPSESSID | Session | Client's session identifier |
| favorite | 1 month | Used to distinguish client's favorites |
| rb_policy | 5 years | List of Сookies accepted by the user |
| navExtended | 1 month | Used to distinguish the state of left side navigation block |
Statistics cookies
Statistics cookies summarise the information concerning how the user interacts with the website, which sections and content are viewed most frequently. The information received is used by Apella only in the summarised anonymous form. The developers of the websites use these data to set up the convenience of use and increase the performance of the website. Statistics cookies collect technical data about the visitor’s device, but they do not identify the user. These cookies are saved on the user’s device only after the user has accepted them in the cookie settings of the website. The Internet website can work without statistics cookies and their use is not mandatory. They are stored on the user’s device for no longer than two years.
| Cookie | Further Information about Operation of Cookie by the Third Party | Browser Add-On to Prevent the Data to be Sent to Google |
|---|---|---|
| Google Analytics | Use of data Data privacy and security |
Addon installation for Google Analytics |
| Cookie name | Default expiration time | Description |
|---|---|---|
| _ga | 2 years | Used to distinguish users. |
| _gid | 24 hours | Used to distinguish users. |
| _ga_ |
2 years | Used to persist session state. |
| _gac_gb_ |
90 days | Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. |
| __utma | 2 years from set/update | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmt | 10 minutes | Used to throttle request rate. |
| __utmb | 30 mins from set/update | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmc | End of browser session | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. |
| __utmz | 6 months from set/update | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
| __utmv | 2 years from set/update | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. |
| Cookie | Further Information about Operation of Cookie by the Third Party |
|---|---|
| Facebook Pixel | https://www.facebook.com/policies/cookies/ |
| Cookie name | Default expiration time | Description |
|---|---|---|
| _fbp | 35 days | About this cookie: when the Facebook pixel is installed on a website, and the pixel uses first-party cookies, the pixel automatically saves a unique identifier to an _fbp cookie for the website domain if one does not already exist. The Facebook pixel is an analytics tool that allows measuring the effectiveness of Facebook advertising by understanding the actions people take on the website. It can be used to: Make sure ads are shown to the right people. The main purpose of this cookie: Marketing/Tracking (Marketing) |
| _fr | 3 months | About this cookie: enables ad delivery or retargeting. Facebook pixels. Facebook pixels are small pieces of software and are nearly invisible pixel-sized “dots” on our Website which create a link between your visit to our Website and Facebook. When the pixel loads, Facebook places a so-called “fr”-cookie on your computer, which helps Facebook to provide you with more personalized advertisements, but also to measure and improve advertisements. Please note that when the “fr”-cookie is placed, Facebook is able to follow your surfing behavior across other websites which have implemented a Facebook pixel or Facebook social plug-in. The main purpose of this cookie: Marketing/Tracking (Marketing) |
| Cookie | Further Information about Operation of Cookie by the Third Party |
|---|---|
| Yandex.Metrika | https://yandex.ru/support/metrica/general/cookie-usage.html |
| Cookie name | Default expiration time | Description |
|---|---|---|
| _ym_metrika_enabled | 60 minutes | Checks if other cookies metrics are set correctly |
| _ym_isad | 2 days | Used to determine if a visitor had ad blockers |
| _ym_uid | 1 year | Checks if other cookies metrics are set correctly |
| _ym_d | 1 year | Checks if other cookies metrics are set correctly |
| yabs-sid | During the visit | Checks if other cookies metrics are set correctly |
| _ym_debug | During the visit | Checks if other cookies metrics are set correctly |
| _ym_mp2_substs | During the visit | Checks if other cookies metrics are set correctly |
| _ym_visorc_* | 30 minutes | Checks if other cookies metrics are set correctly |
| _ym_hostIndex | 24 hours | Checks if other cookies metrics are set correctly |
| _ym_mp2_track | 30 days | Checks if other cookies metrics are set correctly |
| i | 1 year | Checks if other cookies metrics are set correctly |
| yandexuid | 1 year (in some countries the term may be longer) | Checks if other cookies metrics are set correctly |
| yuidss | 1 year (in some countries the term may be longer) | Checks if other cookies metrics are set correctly |
| ymex | 1 year | Checks if other cookies metrics are set correctly |
| usst | 1 year | Checks if other cookies metrics are set correctly |
How Can I Manage or Delete Cookies?
The user is able to either control or delete cookies according to own preferences, more details are available at https://www.aboutcookies.org/. Cookies can be deleted from the user’s device or browser settings may be adjusted in a way to prevent cookies from being stored.
Please ensure that your browser setting reflects whether you wish to be warned about and/or accept cookies where possible. Browser capabilities and instructions on how to use them are available in the manual or help file of your browser.
Please follow the instructions from the web browser developers directly, to configure your browser settings (Apella is not liable for the content of the external links): Internet Explorer, Chrome, Safari, Firefox.
Deactivation or ‘unticking’ of cookies might lead to the reduced availability of services and conveniences provided by the site.
Apella is entitled to unilaterally amend this cookie policy. Please, regularly check up-to-date edition of this policy.