What are cookies?
Cookies are small text files stored on your phone, tablet or computer. They are created when you visit our website. We sends information to the browser which then creates a text file.
How we use cookies?
Cookies help make our website work and deliver services that the website visitor expects. We want our website to be user friendly as possible and cookies help us to achieve that goal. Without these cookies, you will not be able to use Jobs-in-Mombasa.
Which cookies we store:
Technical cookies:
•
PHPSESSID - Session Cookie
•
ID (anonymous User-ID ) - Stored Cookie - Expiration in days 30
•
PAGE (Page navigating) - Session Cookie
Personal data cookies:
•
NAME - User name - Stored Cookie - Expiration in days 30
•
PHONE - User phone number - Stored Cookie - Expiration in days 30
•
EMAIL - User email address - Stored Cookie - Expiration in days 30
•
LINKEDIN - User LinkedIn website url - Stored Cookie - Expiration in days 30
We are GDPR compliant
The "General Data Protection Regulation" (GDPR) of the European Union (EU) is a regulation that requires businesses to protect the personal data and privacy of citizens for transactions. Our website is completly EU GDPR compliant.
What we don't do with cookies:
We do not use cookies to pass it on to third parties. Only we can read this cookies that we have set. We don't track your personal activities. Cookies cannot run programs or deliver viruses to your device.
Google Fonts:
Our website use Google Fonts. Use of Google Fonts is unauthenticated. The Google Fonts API is designed to limit the collection, storage, and use of end-user data to what is needed to serve fonts efficiently. In order to serve fonts as quickly and efficiently as possible with the fewest requests, we cache all requests made to our servers so that your browser only contacts us when it needs to. Requests for CSS assets are cached for 1 day. This allows us to update a stylesheet to point to a new version of a font file when it’s updated. This ensures that all visitors to websites using fonts hosted by the Google Fonts API will see the latest fonts within 24 hours of their release. The result is that website visitors send very few requests to Google: we only see 1 CSS request per font family, per day, per browser. We do log records of the CSS and the font file requests, and access to this data is on a need-to-know basis and kept secure. We keep aggregated usage numbers to track how popular font families are, and we publish these aggregates in the Google Fonts Analytics site. From the Google web crawl, we detect which websites are using Google Fonts, and publish this in the Google Fonts BigQuery database.
