Eduhouse cookies
COOKIEPOLICY PÅ EDUHOUSE OY:S WEBBPLATS EDUHOUSE.SE OCH APP.EDUHOUSE.SE
När gäller denna policy?
Denna cookiepolicy (nedan kallad "policy") beskriver hur Eduhouse AB (nedan kallat "Eduhouse", "vi", "oss" eller "vår") använder cookies på sin webbplats. Läs denna policy noggrant för att förstå hur cookies kan förbättra din upplevelse på vår webbplats och hur du kan hantera cookies på din enhet.
Vad är cookies?
En "cookie" är en liten textfil som lagras på en dator, surfplatta eller telefon, nedan kallad "enhet", när du besöker en webbplats. Cookies känner igen din enhet på webbplatsen och "kommer ihåg" dina tidigare besök för att förbättra användarupplevelsen. De flesta webbplatser, inklusive vår, använder cookies.
Du kan inte identifieras enbart med cookies, men tillsammans med annan information kan de kopplas till dig. I sådana fall kan cookies betraktas som personuppgifter. Vi försöker dock inte att identifiera dig genom cookies. Om vi gör det kommer vi att se till att cookieinformation behandlas som personuppgifter i enlighet med gällande dataskyddslagar och integritetspolicy (Eduhouse Dataskyddsbeskrivning)
Varför använder vi cookies?
Vi strävar efter att utveckla våra tjänster genom att analysera tjänsternas användning med hjälp av olika verktyg. I våra tjänster använder vi t.ex. Google Analytics för att mäta användningen av vår webbplats. Informationen som lagras i cookies som används av Googles verktyg (till exempel pseudonymiserade IP-adresser) vidarebefordras för lagring på Googles servrar runt om i världen. Därför kan sådana uppgifter behandlas på servrar i ett annat land än användarens hemland. Google använder informationen för att utvärdera användarens surfande på sidorna och för att sammanställa sammanfattande rapporter om webbplatsanvändning. Dessutom använder vi till exempel Hotjar-verktyget, vilket gör att vi till exempel kan bygga en så kallad "hotjar". Värmekartor som visar vilka sidelement användare klickar på, hur de rör sig på sidorna och hur långt de kommer i genomsnitt. Detta hjälper oss att lösa potentiella användbarhetsproblem. All data i Hotjar-verktyget är anonymiserad och kan inte kopplas till en individ.
Vilka cookies använder vi?
Vi använder följande cookies på vår webbplats:
Funktionella cookies
Funktionella cookies är nödvändiga för användningen av webbplatsen och dess funktioner. Cookies används till exempel för att komma ihåg inloggningsinformation och språkinställningar. Funktionella cookies kan också användas för att anpassa webbplatser.
Beteendemässiga cookies
Dessa cookies samlar in statistisk information om hur människor använder webbplatsen. De kan till exempel hjälpa oss att förstå hur användare använder vår webbplats och vilka som är de mest populära delarna av vår webbplats.
Vi samlar in information om webbplatsbesök med hjälp av följande verktyg från tredje part:
-
HubSpot – system för marknadsföringsautomation. Läs mer om HubSpots cookies: https://legal.hubspot.com/privacy-policy
-
Hotjar - verktyg för webbplatsanalys. Mer information om Hotjars cookies: Cookies på hotjar.com – Hotjar-dokumentation
-
Google Analytics analysverktyg. Läs mer om Googles cookies: Hur Google använder din information på partnerwebbplatser och appar.
-
Google AdWords onlineannonsering. Läs mer om Googles cookies: Vad är GDPR?
Andra cookies från tredje part
Våra tjänster kan använda så kallade .nets, Sociala plugins och inbäddat innehåll. Till exempel kan Youtube-videor visas i vissa av våra tjänster, men deras innehåll kommer direkt från den tjänsten eller en tjänst som ägs av den. Youtube kan samla in information om dig och spåra dina interaktioner med inbäddat innehåll som om du besökte dess webbplats direkt. Om du vill logga in på våra tjänster, till exempel med ditt Microsoft-användar-ID, kan du göra det. För att kunna använda externa inloggningsmekanismer måste du ändra cookies-inställningen för tjänsteleverantörer på din enhet och cookies-inställningen för tjänsteleverantörer. Cookies kan användas inte bara för inloggning utan också för andra ändamål.
Lagringstid för cookies
Lagringsperioden för cookies på din enhet är uppdelad i två grupper.
Cookies för sessioner
I allmänhet används sessionscookies tillfälligt för att komma ihåg inställningar som är relevanta för webbläsarsessionen. Dessa cookies ställs in för en session i taget och lagras tills webbläsaren stängs. Sessionscookies lagras inte på din enhets hårddisk.
Beständiga cookies
Beständiga cookies används för marknadsföringsändamål och för att få information om användningen av vår webbplats. Beständiga cookies lagras också på din hårddisk mellan surfningssessioner tills du tar bort dem eller den angivna lagringsperioden löper ut. Vi behåller beständig cookieinformation i upp till 2 år, exklusive HubSpot-cookien som behålls i högst 10 år.
Eduhouse.fi – webbplatscookies listade (3.3.2023)
COOKIE NAME |
PROVIDER |
CATEGORY |
EXPIRY |
DESCRIPTION |
IDE |
doubleclick.net |
advertisement |
389 days |
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite |
_fbp |
eduhouse.fi |
advertisement |
89 days |
Facebook analytics cookie |
_gcl_au |
eduhouse.fi |
advertisement |
89 days |
Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. |
_lfa |
eduhouse.fi |
advertisement |
399 days |
Leadfeeder cookie collects the behavioral data of all website visitors. This includes; pages viewed, visitor source and time spent on the site |
fr |
facebook.com |
advertisement |
89 days |
Contains a unique browser and user ID, used for targeted advertising. |
bscookie |
linkedin.com |
advertisement |
365 days |
Used by LinkedIn to track the use of embedded services. |
lidc |
linkedin.com |
advertisement |
1 days |
Used by the social networking service, LinkedIn, for tracking the use of embedded services. |
bcookie |
linkedin.com |
advertisement |
365 days |
Used by LinkedIn to track the use of embedded services. |
UserMatchHistory |
linkedin.com |
advertisement |
29 days |
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc. |
VISITOR_INFO1_LIVE |
youtube.com |
advertisement |
179 days |
Tries to estimate the users' bandwidth on pages with integrated YouTube videos. |
DEVICE_INFO |
youtube.com |
analytics |
179 days |
|
__hssc |
eduhouse.fi |
analytics |
29 minutes |
Analytics session cookie |
hubspotutk |
eduhouse.fi |
analytics |
179 days |
Contains visitor's identity |
__hstc |
eduhouse.fi |
analytics |
179 days |
Analytics tracking cookie |
_gat |
eduhouse.fi |
analytics |
59 seconds |
Used to monitor number of Google Analytics server requests when using Google Tag Manager |
__hssrc |
eduhouse.fi |
analytics |
session |
Used to determine if a session is a new session |
_gid |
eduhouse.fi |
analytics |
1439 minutes |
ID used to identify users for 24 hours after last activity |
_ga |
eduhouse.fi |
analytics |
399 days |
ID used to identify users |
test_cookie |
doubleclick.net |
functionality |
14 minutes |
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies. |
_hjIncludedInPageviewSample |
eduhouse.fi |
functionality |
2 minutes |
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. |
_hjFirstSeen |
eduhouse.fi |
functionality |
29 minutes |
The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. |
messagesUtk |
eduhouse.fi |
functionality |
179 days |
Remembers the identity of the visitor using the chat widget |
_hjAbsoluteSessionInProgress |
eduhouse.fi |
functionality |
29 minutes |
The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. |
li_gc |
linkedin.com |
functionality |
180 days |
Used to store guest consent to the use of cookies for non-essential purposes |
AnalyticsSyncHistory |
linkedin.com |
functionality |
29 days |
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries |
YSC |
youtube.com |
functionality |
session |
Registers a unique ID to keep statistics of what videos from YouTube the user has seen. |
_hjSession_ |
eduhouse.fi |
necessary |
29 minutes |
|
ln_or |
eduhouse.fi |
necessary |
1439 minutes |
|
_hjIncludedInSessionSample_ |
eduhouse.fi |
necessary |
1 minutes |
Start of an session |
_hjSessionUser_ |
eduhouse.fi |
necessary |
364 days |
Session user |
__hs_do_not_track |
eduhouse.fi |
necessary |
179 days |
Prevents the tracking code from sending any information to HubSpot |
_ga_351683869 |
eduhouse.fi |
necessary |
399 days |
Used to persist session state |
__cf_bm |
eduhouse.fi |
necessary |
29 minutes |
Cloud flare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. |
_GRECAPTCHA |
google.com |
necessary |
179 days |
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis. |
__cf_bm |
hubspot.com |
necessary |
29 minutes |
Cloud flare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. |
__cfruid |
vipunet.com |
necessary |
session |
Used by the content network, Cloudflare, to identify trusted web traffic. |
__cf_bm |
vipunet.com |
necessary |
29 minutes |
Cloud flare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. |
Du kan förhindra spårning genom att aktivera alternativet Spåra inte i din webbläsare eller neka ditt samtycke till användningen av cookies.
Chrome: Aktivera eller inaktivera "Spåra inte" - Dator - Google Chrome Hjälp
Firefox: Hur aktiverar jag funktionen Spåra inte? | Firefox Hjälp (mozilla.org)
Edge: Lär dig mer om spårningsskydd i Microsoft Edge - Microsoft Support
Vilka är mina alternativ för att hantera cookies på min enhet?
-
Blockera cookies: Du kan förhindra användningen av cookies genom att ändra dina webbläsarinställningar. Observera att blockering av användningen av cookies kan påverka funktionaliteten i våra tjänster.
-
Rensa cookies eller mobil-ID: Du kan rensa cookies eller din webbläsares lokala arkiv i dina webbläsarinställningar eller återställa ditt mobil-ID i dina enhetsinställningar. Genom att rensa dina cookies eller mobil-ID med jämna mellanrum kan du ändra identifieraren som kommer att bilda din profil. Att rensa cookies stoppar dock inte insamlingen av data helt, utan återställer snarare profilen baserat på tidigare beteendedata.
-
För att förhindra användning av Google Analytics: Du kan förhindra t.ex. användning av webbplatsdata av Google Analytics genom att installera ett webbläsartillägg som förhindrar användning av Google Analytics. Detta tillägg förhindrar att Google Analytics JavaScript körs på webbplatser (t.ex. ga.js, analytics.js och dc.js) från att dela webbplatsbesöksdata med Google Analytics.
Databehandling relaterad till mobila applikationer: Användaren har flera möjligheter att påverka data som samlas in av mobila applikationer. Ofta erbjuder mobilapplikationer möjligheten att kontrollera val när det gäller behandling av platsdata, meddelanden som skickas av appen och inriktning av reklam via appens inställningar. Förutom programmets inställningar kan användaren också påverka de data som samlas in av applikationerna från de allmänna inställningarna för den mobila enheten.
COOKIE NOTICE ON EDUHOUSE OY'S WEBSITE EDUHOUSE.SE AND APP.EDUHOUSE.SE
When does this Notice apply?
This Cookie Notice (hereinafter referred to as the "Notice") describes how Eduhouse Oy (hereinafter referred to as "Eduhouse", "we", "us" or "our") uses cookies on its website. Please read the Notice carefully to understand how cookies can improve your experience on our website and how you can manage cookies on your device.
What are cookies?
A "cookie" is a small text file that is stored on a computer, tablet or phone, hereinafter referred to as a "device", when visiting a website. Cookies recognize your device on the website and "remember" your previous visits to improve the user experience. Most websites, including ours, use cookies.
You cannot be identified by cookies alone, but together with other information, they can be linked to you. In such cases, cookies may be considered personal data. However, we do not try to identify you through cookies. If we do so, we will ensure that cookie information is treated as personal data in accordance with applicable data protection laws and privacy policy. (Eduhouse Privacy Policy)
Why do we use cookies?
We strive to develop our services by analyzing their use with the help of various tools. In our services, we use e.g., Google Analytics to measure the use of our website. The information stored in cookies used by Google's tools (for example, pseudonymised IP addresses) is forwarded for storage on Google's servers around the world. Therefore, such data may be processed on servers located in a country other than the user's country of residence. Google uses the information it receives to evaluate the user's browsing of the content of the pages and to compile summary reports on site usage. In addition, we use, for example, the Hotjar tool, which allows us, for example, to build a so-called "hotjar". Heatmaps that show which page elements users click on, how they move around the pages, and how far they are progressing on average. This helps us solve potential usability issues. All data in the Hotjar tool is anonymized and cannot be linked to an individual.
What cookies do we use?
We use the following cookies on our website:
Functional cookies
Functional cookies are necessary for the use of the website and its features. Cookies are used, for example, to remember login information and language preferences. Functional cookies can also be used to personalize websites.
Behavioral cookies
These cookies collect statistical information about how people use the website. For example, they can help us understand how users use our website and what are the most popular parts of our website.
We collect information about website visits using the following third-party tools:
HubSpot – marketing automation system. Learn more about HubSpot's cookies: https://legal.hubspot.com/privacy-policy
Hotjar - website analytics tool. More information about Hotjar's cookies: Cookies on hotjar.com – Hotjar Documentation
Google Analytics analytics tool. Learn more about Google's cookies: How Google uses your information on partner sites and apps.
Google AdWords online advertising. Learn more about Google's cookies: What is the GDPR?
Other third-party cookies
Our services may use so-called .nets. Social plugins and embedded content. For example, Youtube videos may appear in some of our services, but their content comes directly from that service, or a service owned by it. Youtube may collect information about you and track your interactions with embedded content as if you were visiting its site directly. In addition, if you want to sign into our services, for example, with your Microsoft user ID, please do so. service provider and share data based on the authorization you have given to Eduhouse. To use external login mechanisms, you need to do so. the setting of cookies by service providers on your terminal device, and the setting of cookies by service providers. Cookies may be used not only for logging in, but also for other purposes.
Storage period of cookies
The storage period of cookies on your device is divided into two groups.
Session cookies
In general, session cookies are temporarily used to remember settings relevant to the browsing session. These cookies are set for one session at a time and are stored until the browser is closed. Session cookies are not stored on your device's hard drive.
Persistent cookies
Persistent cookies are used for marketing purposes and to obtain information about the use of our website. Persistent cookies are also stored on your hard drive between browsing sessions until you delete them, or the specified retention period expires. We retain persistent cookie information for up to 2 years, excluding the HubSpot cookie, for a maximum of 10 years.
Eduhouse.fi – website cookies listed (3.3.2023)
COOKIE NAME |
PROVIDER |
CATEGORY |
EXPIRY |
DESCRIPTION |
IDE |
doubleclick.net |
advertisement |
389 days |
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite |
_fbp |
eduhouse.fi |
advertisement |
89 days |
Facebook analytics cookie |
_gcl_au |
eduhouse.fi |
advertisement |
89 days |
Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. |
_lfa |
eduhouse.fi |
advertisement |
399 days |
Leadfeeder cookie collects the behavioral data of all website visitors. This includes; pages viewed, visitor source and time spent on the site |
fr |
facebook.com |
advertisement |
89 days |
Contains a unique browser and user ID, used for targeted advertising. |
bscookie |
linkedin.com |
advertisement |
365 days |
Used by LinkedIn to track the use of embedded services. |
lidc |
linkedin.com |
advertisement |
1 days |
Used by the social networking service, LinkedIn, for tracking the use of embedded services. |
bcookie |
linkedin.com |
advertisement |
365 days |
Used by LinkedIn to track the use of embedded services. |
UserMatchHistory |
linkedin.com |
advertisement |
29 days |
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc. |
VISITOR_INFO1_LIVE |
youtube.com |
advertisement |
179 days |
Tries to estimate the users' bandwidth on pages with integrated YouTube videos. |
DEVICE_INFO |
youtube.com |
analytics |
179 days |
|
__hssc |
eduhouse.fi |
analytics |
29 minutes |
Analytics session cookie |
hubspotutk |
eduhouse.fi |
analytics |
179 days |
Contains visitor's identity |
__hstc |
eduhouse.fi |
analytics |
179 days |
Analytics tracking cookie |
_gat |
eduhouse.fi |
analytics |
59 seconds |
Used to monitor number of Google Analytics server requests when using Google Tag Manager |
__hssrc |
eduhouse.fi |
analytics |
session |
Used to determine if a session is a new session |
_gid |
eduhouse.fi |
analytics |
1439 minutes |
ID used to identify users for 24 hours after last activity |
_ga |
eduhouse.fi |
analytics |
399 days |
ID used to identify users |
test_cookie |
doubleclick.net |
functionality |
14 minutes |
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies. |
_hjIncludedInPageviewSample |
eduhouse.fi |
functionality |
2 minutes |
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. |
_hjFirstSeen |
eduhouse.fi |
functionality |
29 minutes |
The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. |
messagesUtk |
eduhouse.fi |
functionality |
179 days |
Remembers the identity of the visitor using the chat widget |
_hjAbsoluteSessionInProgress |
eduhouse.fi |
functionality |
29 minutes |
The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. |
li_gc |
linkedin.com |
functionality |
180 days |
Used to store guest consent to the use of cookies for non-essential purposes |
AnalyticsSyncHistory |
linkedin.com |
functionality |
29 days |
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries |
YSC |
youtube.com |
functionality |
session |
Registers a unique ID to keep statistics of what videos from YouTube the user has seen. |
_hjSession_ |
eduhouse.fi |
necessary |
29 minutes |
|
ln_or |
eduhouse.fi |
necessary |
1439 minutes |
|
_hjIncludedInSessionSample_ |
eduhouse.fi |
necessary |
1 minutes |
Start of an session |
_hjSessionUser_ |
eduhouse.fi |
necessary |
364 days |
Session user |
__hs_do_not_track |
eduhouse.fi |
necessary |
179 days |
Prevents the tracking code from sending any information to HubSpot |
_ga_351683869 |
eduhouse.fi |
necessary |
399 days |
Used to persist session state |
__cf_bm |
eduhouse.fi |
necessary |
29 minutes |
Cloud flare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. |
_GRECAPTCHA |
google.com |
necessary |
179 days |
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis. |
__cf_bm |
hubspot.com |
necessary |
29 minutes |
Cloud flare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. |
__cfruid |
vipunet.com |
necessary |
session |
Used by the content network, Cloudflare, to identify trusted web traffic. |
__cf_bm |
vipunet.com |
necessary |
29 minutes |
Cloud flare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. |
You can prevent tracking by enabling the Do Not Track option in your browser or denying your consent to the use of cookies.
Chrome: Turn "Do Not Track" on or off - Computer - Google Chrome Help
Firefox: How do I turn on the Do Not Track feature? | Firefox Help (mozilla.org)
Edge: Learn about tracking prevention in Microsoft Edge - Microsoft Support
What are my options for managing cookies on my device?
Blocking cookies: You can prevent the use of cookies by changing your browser settings. Please note that blocking the use of cookies may affect the functionality of our services.
Clearing cookies or mobile ID: You can clear cookies or your browser's local repository in your browser settings or reset your mobile ID in your device settings. By clearing your cookies or mobile ID at regular intervals, you can change the identifier that will form your profile. However, clearing cookies does not completely stop the collection of data, but rather resets the profile based on previous behavioral data.
To prevent the use of Google Analytics: You can prevent e.g. the use of site data by Google Analytics by installing a browser add-on that prevents the use of Google Analytics. This add-on prevents the Google Analytics JavaScript running on websites (e.g. ga.js, analytics.js and dc.js) from sharing site visit data with Google Analytics.
Data processing related to mobile applications: The user has several possibilities to influence the data collected by mobile applications. Often, mobile applications offer the ability to control choices regarding the processing of location data, notifications sent by the app, and the targeting of advertising through the app's settings. In addition to the settings of the application, the user can also influence the data collected by the applications from the general settings of the mobile device.