Cookies and other similar tracking technologies are small text files or code placed on your device (e.g. computer, smartphone or other electronic device) when you use our website or app or view a message. Cookies allow a website or app to recognise a particular device.
For example, we may monitor how many times you visit our website or use our app, which pages you go to, traffic data, location data and the originating domain name of your internet service provider. This information helps us to build a profile of our users. Some of this data will be aggregated or statistical, which means that we will not be able to identify you individually.
You can set your browser not to accept cookies and the websites below tell you how to remove cookies from your browser. However, some of our website features may not function as a result.
The cookies we place on your device fall into the following categories:
At Fika Community Limited we set and use some cookies ourselves but only on our site. We refer to these as first party cookies. When cookies are served by another domain or by one of our service providers we refer to them as third party cookies. Please see what cookies and other similar tracking technologies we use below:
First Party Cookies
|_net||fika.community||While the session is active||Sessions are stored per-user in memory on the server. Sessions use a cookie (session key) to tie the user to the session. This means no "sensitive" data is stored in the cookie on the users’ machine.|
|Sends anonymous aggregate reports about your site usage to Fika.|
|Cookie Consent||fika.community||1 year||This cookie is used for getting your consent to cookies.|
Third Party Cookies and other tracking technology
|The Website is hosted on Netlify||They are a supplier who is used but the only purpose is that they host the website. Log file hosted by them.|
We use CONSENT (gstatic.com) cookies - expires in 9 years.
|Google Analytics for Firebase||Google Analytics for Firebase uses device identifiers to collect and store information such as number of sessions per user, session duration, operating system, device models, geography, first launches, and app updates.|
|Google AdSense||Google AdSense uses what is called a DoubleClick Cookie. We use this to help us to track the effectiveness of our marketing campaigns. It enables Google to serve our adverts on other sites based on your browsing history on our page and engagement with our adverts.|
|Google Tag Manager||Google Tag Manager allows us to manage and deploy marketing tags (snippets of code or tracking pixels) on our website (or mobile app). These tags enable us to optimise our website experience and marketing campaigns by understanding how users interact with different elements of our website (or mobile app).|
|SendinBlue||We use SendinBlue cookies to store your contact details for our mailing lists and to send marketing emails.|
This cookie is used when a user subscribes to a newsletter mailing list and expires in 5 years.
|Facebook Conversion Tracking Pixel||A tracking technology that allows us to follow the actions of users after they are redirected to our website or apps by interacting (viewing or clicking) on an advertisement within Facebook.|
|Firebase Cloud Messaging||The Fika app uses Firebase Cloud Messaging to send messages to its users. To do so, it sends a previously generated anonymous device ID (token) to Google so that we can identify app users and send messages to them. Information on the functionality of Cloud Messaging is available under https://firebase.google.com/products/cloud-messaging/|
|Firebase Authentication||Firebase Authentication allows us to authenticate users to the Fika app. Every time a user signs in, the user credentials are sent to the Firebase Authentication backend and exchanged for a Firebase ID token (a JWT) and refresh token. Firebase ID tokens are short lived and last for an hour; the refresh token can be used to retrieve new ID tokens.|
|Firebase Crash Reporting||Crash Reporting creates detailed reports of the errors in the Fika app. We use the platform to track app crashes as they occur and prevent future ones. Errors are grouped into issues based on having similar stack traces, and triaged by the severity of impact on users. We do not collect any personally identifiable information (such as names, email addresses, or phone numbers) with Crash Reporting.|
|__hs_do_not_track||This cookie can be set to prevent the tracking code from sending any information to HubSpot. It contains the string "yes". It expires in 13 months.|
|__hs_initial_opt_in||This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. It contains the string "yes" or "no". It expires in seven days.|
|__hs_cookie_cat_pref||This cookie is used to record the categories a visitor consented to. It contains data on the consented categories. It expires in 13 months.|
|hs_ab_test||This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. It contains the id of the A/B test page and the id of the variation that was chosen for the visitor. It expires at the end of the session.|
|<id>_key||When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. The cookie name is unique for each password-protected page. It contains an encrypted version of the password so future visits to the page will not require the password again. It expires in 14 days.|
|hs-messages-is-open||This cookie is used to determine and save whether the chat widget is open for future visits. It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity. If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes. It contains a boolean value of True if present. It expires in 30 minutes.|
|hs-messages-hide-welcome-message||This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed. It contains a boolean value of True or False. It expires in one day.|
|__hsmem||This cookie is set when visitors log in to a HubSpot-hosted site. It contains encrypted data that identifies the membership user when they are currently logged in. It expires in one year.|
|hs-membership-csrf||This cookie is used to ensure that content membership logins cannot be forged. It contains a random string of letters and numbers used to verify that a membership login is authentic. It expires at the end of the session.|
|hs_langswitcher_choice||This cookie is used to save the visitor’s selected language choice when viewing pages in multiple languages. It gets set when an end user selects a language from the language switcher and is used as a language preference to redirect them to sites in their chosen language in the future, if they are available. It contains a colon delimited string with the ISO639 language code choice on the left and the top level private domain it applies to on the right. An example will be "EN-US:hubspot.com". It expires in two years.|
|__cfruid||This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. Learn more about Cloudflare cookies. It expires at the end of the session.|
|__hstc||The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). It expires in 13 months.|
|hubspotutk||This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor. It expires in 13 months.|
|__hssc||This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. It expires in 30 minutes.|
|__hssrc||Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value "1" when present. It expires at the end of the session.|
We will ask for your permission (consent) to place cookies or other similar technologies on your device, except where these are essential for us to provide you with a service that you have requested (e.g. to enable you to log in to our app).
If you do not want to accept cookies, you can change your browser settings so that cookies are not accepted. If you do this, please be aware that you may lose some of the functionality of our website or app.
To find out more about cookies, including how to see which cookies have been set and how to manage and delete them, you can visit the third party website: www.allaboutcookies.org
You can manage how our app accesses the services or information on your device by using the privacy settings on your device, such as turning off push notification and location services.