Cookie policy
Short, because there is very little to report. Last updated {date}.
1. Nothing is loaded until you accept it
Gemifier's marketing website is a set of static pages. Two things on it set cookies. Google Analytics counts visits and shows which pages get read. Tawk.to provides the live chat window, so you can talk to us without sending an email. Neither is requested, and no cookie is set, until you press Accept on the banner.
If you press Reject, or simply ignore the banner, nothing is requested from either of them. The pages behave exactly the same, except that the chat window does not appear. The email addresses on the contact page reach the same people.
There is no advertising, remarketing or session-recording script on the site, and no cookie here carries your name, your email or anything else you have told us.
The legal basis for the analytics and live chat cookies is your consent, given through the banner. You can withdraw it at any time using Cookie settings in the footer of any page, and withdrawing is one click, exactly like giving it. Your theme preference and the record of your cookie choice need no consent, because they are strictly necessary to provide what you asked for, which is also why they cannot be switched off.
2. What is stored in your browser
Your light or dark theme preference is kept in local storage, not a cookie, so it is never attached to a request and never leaves your device. It exists so the site does not flash the wrong colour scheme when you come back. The analytics cookies are different: they hold a randomly generated identifier so that repeat visits are counted as one returning visitor rather than several new ones, and they are sent with the analytics requests described below.
| Name | Type | Purpose | Expiry |
|---|---|---|---|
gemifier-theme |
Local storage | Remembers whether you chose the light or dark theme. Strictly functional; not sent to any server. | Until you clear site data |
gemifier-consent |
Local storage | Remembers whether you accepted or rejected analytics, so you are asked once. Strictly functional; not sent to any server. | Until you clear site data |
__tawkuuid, TawkConnectionTime, twk_uuid_* |
Third-party cookies and local storage | Tawk.to live chat. Recognises you between pages and visits so a conversation is not lost when you navigate. Set only after you accept. These names are chosen by Tawk.to rather than by us, and it may set others; its privacy policy is the authoritative list. | Up to 6 months |
_ga |
First-party cookie | Google Analytics. Holds a randomly generated identifier so that repeat visits are counted as one visitor. | 2 years |
_ga_GC1D419HQN |
First-party cookie | Google Analytics. Keeps session state, so that one visit is not counted as several. | 2 years |
3. Third-party requests
The pages load two typefaces, Inter and JetBrains Mono, from Google Fonts
(fonts.googleapis.com and fonts.gstatic.com). Google does not set
cookies on these font requests, but it does receive your IP address and user agent as part of
serving the file, and that is a disclosure you are entitled to. If that transfer is not
acceptable in your context, the fonts can be self-hosted: download the WOFF2 files, place
them in assets/fonts/ and replace the stylesheet link with an
@font-face block. The site is designed to fall back to system fonts and remains
fully usable if the request is blocked.
The analytics script is loaded from www.googletagmanager.com and reports to
Google Analytics. What it sends is page-level: the page you are on, the page that referred
you, an approximate location worked out from your IP address, your device and browser, and
the identifier held in the cookies above. Google receives and stores that data on its own
infrastructure. Blocking the request changes nothing about how these pages render or behave.
The live chat window is served by Tawk.to, which loads from
embed.tawk.to and keeps an open connection so messages arrive as they are
typed. It receives your IP address, the pages you view while the widget is open, and
whatever you type into the chat. It is loaded only if you accept, and never before.
The contact form posts to formsubmit.co, a third-party relay that forwards
the message to us by email. It sets no cookie and the request is made only when you press
send, never on page load, which is why it is described here rather than in the table
above. What it receives is whatever you typed into the form, plus your IP address. It
keeps a copy for 30 days. If you would rather not involve it, the email addresses on the
contact page reach the same people directly.
4. If you sign in to the product
The Gemifier dashboard is a separate application from this website. Authenticating there involves storing a signed access token in your browser so you stay signed in between requests. That is strictly necessary for the service to function and is covered by the privacy policy rather than by this page.
5. Managing your choices
Both are off until you turn them on. The first time you arrive you are asked to choose, and the choice is remembered so you are not asked again. Reject all and Accept all are one click each and sit side by side. Preferences opens a third option: a switch for analytics and a separate switch for live chat, so you can allow one and refuse the other.
The Necessary row cannot be switched off, because there is nothing there to switch off: it covers your theme preference and this cookie choice, both kept in your browser and never sent anywhere. It sets no cookies.
To change your mind later, use Cookie settings in the footer of any page. It opens the same switches with your current answers filled in. If you turn something off that was on, the page reloads so that it actually stops running, rather than sitting behind a switch that says off.
Your answer is stored in your browser's local storage and nowhere else. We keep no server-side record of it. Clearing your site data therefore clears your choice and you will be asked again, and it also means we cannot produce evidence of what you chose or when.
You can also opt out without touching the banner. Google publishes a browser add-on that
turns Google Analytics off everywhere you browse, and most browsers and content blockers can
block the googletagmanager.com request on their own. Either way the pages keep
working exactly as they do now. Switching analytics off stops any further collection, but it
does not delete what Google has already collected, and we have no way to delete that on your
behalf: Google's own data controls are the route to it.
To clear what is already stored, clear site data for this domain in your browser settings. That removes the analytics cookies and the theme preference together, and the site will go back to following your operating system's light or dark setting. You can also block third-party requests in your browser or an extension, in which case the site renders with system fonts.
6. Changes
If we add anything that stores or transmits information about you, we will update this page and, where required, ask for your consent before it loads. Questions: business@gemifier.io.