Version 2.0. This version takes effect on 27 October 2026. It replaces the previous version from this date.
This page explains what cookies Margifi uses, why, and how you can control them. There are three categories: strictly necessary cookies that keep the platform running; analytics cookies (Google Analytics 4, PostHog and Microsoft Clarity) that help us improve the website and product; and marketing measurement cookies (Meta Pixel) on the margifi.com website that tell us which of our ads bring visitors and sign-ups. Where the law requires it, we ask for your consent before setting cookies that are not strictly necessary.
Questions about this policy? Email admin@margifi.com
1. What are cookies?
Cookies are small text files placed on your computer, mobile device, or browser by a website or web application when you visit it. Cookies are widely used to make websites work effectively, to improve user experience, and to provide reporting information to website operators.
Margifi also uses similar technologies including:
- Local storage: browser-based storage used to retain session preferences and dashboard configuration settings between visits.
- Session storage: temporary, in-session storage cleared when the browser tab is closed, used for navigation state.
- Pixel trackers / event scripts: JavaScript event collection used by PostHog in the Dashboard, and by Microsoft Clarity and the Meta Pixel on the margifi.com website.
The term "cookies" in this policy refers collectively to cookies, local storage, session storage, and event-tracking scripts unless otherwise specified.
2. Categories of cookies we use
Margifi uses three categories of cookies.
Category 1: Strictly necessary
These cookies are essential to the operation of the Margifi Dashboard and cannot be disabled. Without them, the Service cannot function. They do not collect information for marketing or tracking purposes.
You cannot opt out of strictly necessary cookies. Disabling these cookies via your browser settings will prevent you from logging in or using the Margifi Dashboard.
| Cookie name | Purpose | Duration | Set by |
|---|---|---|---|
sb-<project-ref>-auth-token | Supabase Auth session token. Holds the signed access and refresh tokens that identify the authenticated user and keep them logged in across page loads. <project-ref> is the identifier of Margifi's Supabase project. | Up to 1 year, refreshed on use; deleted on logout | Supabase (app.margifi.com) |
sb-<project-ref>-auth-token.0, sb-<project-ref>-auth-token.1 | Continuation chunks of the session token above. Browsers cap the size of a single cookie, so a longer token is split across numbered parts. Same purpose and lifetime as the token itself. | Up to 1 year, refreshed on use; deleted on logout | Supabase (app.margifi.com) |
sb-<project-ref>-auth-token-code-verifier | Short-lived PKCE verifier written while a sign-in, Google sign-in, or password-reset flow is in progress. It is required to complete the exchange securely and is cleared as soon as the flow finishes. | Minutes; cleared when sign-in completes | Supabase (app.margifi.com) |
Category 2: Analytics
These cookies are used to understand how people use the Margifi website and Dashboard so that Margifi can improve them. We use the data for our own analysis, not for advertising.
You may opt out of analytics cookies. See Section 4 for how.
| Cookie name | Purpose | Duration | Set by |
|---|---|---|---|
ph_[token]_posthog | PostHog analytics identity cookie. Assigns an identifier, linked to your Margifi user account once you sign in, to track a user's sessions and feature interactions across visits to the Dashboard, enabling Margifi to understand which features are used, where users drop off, and how navigation flows. | 1 year | PostHog (app.margifi.com) |
_ga | Google Analytics 4 identity cookie set on the margifi.com marketing website. Assigns a randomly generated identifier so that repeat visits can be counted as one visitor rather than several, and so Margifi can see which pages and traffic sources bring people to the site. | 2 years | Google Analytics (margifi.com) |
_ga_K7YWLNXMWH | Google Analytics 4 property-specific cookie. Holds the session state for Margifi's individual Analytics property: session start, session count, and engagement timing on the marketing website. | 2 years | Google Analytics (margifi.com) |
_clck | Microsoft Clarity identity cookie set on the margifi.com website. Holds a random visitor identifier so Clarity can group page views from the same browser. | 1 year | Microsoft Clarity (margifi.com) |
_clsk | Microsoft Clarity session cookie. Links the pages viewed in one visit into a single session recording. | 1 day | Microsoft Clarity (margifi.com) |
mf_cc | Holds your two-letter country code on our ad landing pages, so visits from Meta's ad-review systems outside India can be left out of our Google Analytics reports. It holds no identifier. | 1 day | Margifi (margifi.com) |
Cookieless measurement: Margifi also uses Vercel Analytics and Vercel Speed Insights to measure page views and loading performance. Neither sets a cookie, and neither stores an identifier in your browser, so there is nothing to opt out of and nothing to delete.
Session recordings: PostHog may also capture session recordings (screen replays of user interactions within the Dashboard) to assist Margifi in identifying usability issues. Session recordings mask typed input by default and are not shared with third parties. Recorded sessions do not capture passwords, payment information, or API credentials.
Microsoft Clarity: on the margifi.com website (not inside the Dashboard), Microsoft Clarity records heatmaps and session recordings of how visitors scroll, click and move through our pages. We use them to find confusing or broken pages. By default, Clarity masks text typed into form fields. Microsoft may also set its own cookies on the clarity.ms domain.
Category 3: Marketing measurement
These cookies are set by the Meta Pixel on the margifi.com website only, never inside the Dashboard. They let us measure whether people who see or click our ads on Meta (Facebook and Instagram) visit the site or sign up, and help Meta show our ads to relevant businesses.
You may opt out of marketing cookies. See Section 4 for how.
| Cookie name | Purpose | Duration | Set by |
|---|---|---|---|
_fbp | Meta Pixel browser identifier. Lets Meta match visits and sign-ups on margifi.com to our ads. | 90 days | Meta Pixel (margifi.com) |
_fbc | Set only when you arrive from a Meta ad link. Stores the ad click identifier so the visit can be credited to that ad. | 90 days | Meta Pixel (margifi.com) |
Conversions API: when you submit a sign-up or lead form on margifi.com, our server also sends Meta a "Lead" event through Meta's Conversions API. It includes your email address (and phone number for trial sign-ups) as one-way SHA-256 hashes, never in plain text, plus your IP address, browser user agent and the _fbp / _fbc values above. Meta uses the same event ID to avoid counting the browser and server copies twice.
3. Cookies we do not use
Margifi does not use:
- Advertising cookies inside the Dashboard: the Meta Pixel runs on the margifi.com website only.
- Other ad network pixels: no LinkedIn Insight Tag, TikTok Pixel, or equivalent.
- Selling data: we do not sell cookie data or share it with data brokers.
- Affiliate tracking cookies.
4. Consent and how to control cookies
Consent
Strictly necessary cookies are set without consent, because the Service cannot work without them. Where the law requires it, we ask for your consent before setting analytics and marketing cookies, using a cookie banner on margifi.com. You can change or withdraw your consent at any time, as easily as you gave it, and the methods below always work too. Withdrawing consent does not affect processing that happened before you withdrew it.
4.1 Browser settings
You can control and delete cookies through your browser settings. Most modern browsers allow you to:
- View cookies currently stored and delete individual cookies
- Block all cookies from specific websites
- Block all third-party cookies
- Set preferences to be notified when a cookie is set
Instructions for common browsers:
- Google Chrome: Settings › Privacy and security › Cookies and other site data
- Mozilla Firefox: Settings › Privacy & Security › Cookies and Site Data
- Safari (macOS): Preferences › Privacy › Manage Website Data
- Microsoft Edge: Settings › Cookies and site permissions › Cookies and site data
- Safari (iOS): Settings › Safari › Privacy & Security
Please note: disabling strictly necessary cookies (Category 1) will prevent you from accessing the Margifi Dashboard.
4.2 Opting out of PostHog analytics
If you wish to opt out of PostHog analytics tracking while continuing to use the Margifi Dashboard, here is what you can do:
- a) Email request: contact Margifi at admin@margifi.com and request that your user account be excluded from analytics tracking. Margifi will apply the PostHog opt-out flag to your user profile within 5 business days.
- b) Do Not Track browser signal: Margifi's analytics do not currently respond to the DNT signal; please use option (a) or (c) to opt out.
- c) PostHog's own opt-out mechanism: PostHog provides an opt-out at posthog.com/privacy.
4.3 Opting out of Google Analytics
Google Analytics runs on the margifi.com marketing website only, never inside the Dashboard. To opt out across every site that uses it, install Google's official browser add-on at tools.google.com/dlpage/gaoptout. Blocking the _ga cookies in your browser settings, as described in 4.1, has the same effect and does not affect your ability to use the Dashboard.
4.4 Opting out of Microsoft Clarity
Clarity runs on the margifi.com website only. Blocking the _clck and _clsk cookies, or cookies from clarity.ms, in your browser settings stops Clarity from linking your visits. See Microsoft's privacy statement at privacy.microsoft.com/privacystatement.
4.5 Opting out of the Meta Pixel
Block the _fbp and _fbc cookies in your browser settings, or manage ad preferences in your Facebook or Instagram account settings. To stop our server sending a Conversions API event about a form you submitted, email admin@margifi.com.
5. Third-party tools
The following third-party services set cookies or equivalent tracking technologies on the Margifi Platform. Each has its own privacy policy governing how it uses data. Every provider that processes data for us is listed on our Sub-processors page.
| Third party | Category | Privacy policy |
|---|---|---|
| Supabase | Strictly Necessary | supabase.com/privacy |
| PostHog | Analytics | posthog.com/privacy |
| Google Analytics | Analytics | policies.google.com/privacy |
| Microsoft Clarity | Analytics | privacy.microsoft.com/privacystatement |
| Meta (Meta Pixel and Conversions API) | Marketing measurement | facebook.com/privacy/policy |
6. Changes to this policy
6.1 Margifi may update this Cookie Policy from time to time to reflect changes in the cookies we use, changes in applicable law, or changes in our product. When material changes are made, Margifi will notify users by email and a notice on the Dashboard at least 14 days before they take effect.
6.2 The version, last-updated date and effective date at the top of this policy show when it was last revised.
6.3 The most current version of this Cookie Policy is always available at:
https://margifi.com/cookie-policy
7. Contact
Email: admin@margifi.com
Address: Margifi Private Limited, 230, Ayodhyapuram Residency, Nr Valak Patiya, Valak, Surat City, PO: Sarthana, Dist: Surat, Gujarat 395006, India
Questions about this policy? Contact us at admin@margifi.com · Privacy Policy · Terms of Service
Version history
- Version 2.0, 27 October 2026 (effective 27 October 2026): added Microsoft Clarity (heatmaps and session recordings on margifi.com), the Meta Pixel and Conversions API Lead events (new marketing measurement category), and the
mf_cccookie; added how consent works; updated the list of cookies we do not use. - Previous version, 25 July 2026.