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.|
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.