Cookie Policy
This Cookie Policy explains what cookies and similar technologies GitMir uses on gitmir.com and inside the GitMir platform, why we use them, and how you can control them.
1. What Cookies Are
Cookies are small text files stored on your device when you visit a website. They allow the site to remember your actions and preferences over time (such as sign-in state) and to understand how the site is used.
Similar technologies — including local storage, session storage, and pixels — are also covered by this policy.
2. Cookies We Use
Strictly necessary — required to operate the Service: authentication session (e.g. crm_session for admin access), CSRF tokens, load-balancing identifiers. Without these the site cannot function correctly.
Functional — remember your preferences such as the last selected tab in a feature comparison or whether you have dismissed a banner.
Analytics — help us understand how the site is used so we can improve it. Our site analytics are first-party and stay with GitMir: the pages you open, how long each is read, how far it is scrolled, which parts of it were on screen and what you click. Without your consent nothing is stored on your device for this, and a visit cannot be linked to your visits on other days. If you choose "Accept all", a random identifier is kept in local storage (gm-vid) so your visits can be recognised across days. The same identifier is also kept in a first-party cookie of the same name, so that when we compare two versions of a page you see the same version on every visit; without your consent the cookie is not set, and everyone sees the standard version. If you send us a form, the visits made from that browser are linked to your enquiry. If you then open a GitMir account from a link on this site, a pseudonymous key made from that identifier travels with the link, so the visits made before you signed up are linked to your account.
Payment processing — Stripe sets its own cookies when you reach the checkout page. These are governed by Stripe's privacy and cookie policies.
3. Third-Party Services
Fonts are served from gitmir.com itself: loading them sends no request to a third party and sets no cookies.
Stripe Checkout is loaded only when you proceed to payment. It uses cookies to detect fraud and to maintain your checkout session.
4. Managing Cookies
Most browsers let you view, manage, and delete cookies through their settings. Disabling strictly-necessary cookies will break sign-in and other core flows; disabling analytics cookies will not affect your ability to use the Service.
For mobile devices, you can also reset advertising identifiers through your operating-system settings.
5. Do Not Track
There is currently no industry-wide standard for responding to Do Not Track (DNT) browser signals. We honour DNT and Global Privacy Control: when either signal is present, no analytics identifier is stored on your device, even if you chose "Accept all".
6. Changes to This Policy
We may update this Cookie Policy from time to time. The “Last updated” date at the top reflects the latest revision. We will notify you of material changes through a notice on the site.