1. What Are Cookies and Storage Technologies?
Cookies are small text files stored on your device when you visit a website. They help the site remember information about your visit, such as your preferences or authentication state. Alongside HTTP cookies, web applications may use browser LocalStorage and SessionStorage for interface preferences. FDIE keeps session tokens in HttpOnly cookies, not in browser storage, so scripts running on the page cannot read them.
First-party cookies belong to the site you are visiting. Third-party cookies belong to another domain, such as an embedded service. A service provider may also set cookies on our domain. Section 5 describes these services.
2. Categories of Cookies We Use
Strictly necessary. Required for core site functionality: session management, security (CSRF protection), and user authentication. Blocking these cookies can prevent sign-in or security checks from working; your browser still controls whether to accept them.
Functional. On the FDIE platform, remembers interface preferences. The marketing site’s own code does not store interface preferences. Embedded booking and edge-security services are described separately below; their behavior is not established by the absence of a consent banner.
Analytics. We do not set analytics cookies on this site. We use Cloudflare Web Analytics, which counts page views with a cookieless script from cloudflareinsights.com and stores nothing in your browser. Section 3 lists the application’s first-party cookie and storage keys; third-party services and identity providers may use additional cookies as described in Section 5. If we introduce an analytics provider in the future, this section and the table below will be updated before any such cookie is set, and consent will be requested where required.
We do not use any cookie or storage mechanism on this site for advertising or cross-site ad retargeting.
3. Cookies & Storage Keys We Use
These keys are set by Magdox on the FDIE platform only. The storage type is shown below each name.
Scroll horizontally to see all columns.
| Name and storage | Purpose | Duration | Category |
|---|---|---|---|
__Host-fdie_sessionCookie | Maintains your signed-in session; HttpOnly and Secure | 30-minute inactivity timeout; refreshed during authenticated use | Strictly necessary |
csrf_tokenCookie | Cross-site request forgery protection | Up to 24 hours; renewed when the session changes | Strictly necessary |
fdie_sidebar_collapsedLocalStorage | Remembers whether navigation is collapsed | Until browser storage is cleared | Functional |
fdie_mfa_reminder_dismissed_…LocalStorage | Remembers dismissal of the MFA setup reminder for an account | Until browser storage is cleared | Functional |
fdie-selected-ticket-idSessionStorage | Opens the selected support ticket without putting its identifier in the address bar | Browser tab session | Functional |
Local development uses fdie_session instead of the production session-cookie name. Interface storage contains preferences or a ticket identifier, not authentication tokens. Browser storage does not grant access to a ticket; the server checks authorization.
The marketing website (fdie.dev) sets no cookies of its own and stores nothing in browser storage. Embedded services and Cloudflare security features may set cookies, including cookies on the website’s own domain; see Section 5.
4. Managing Your Cookie Preferences
The current marketing site does not provide a cookie-preference panel. You can block third-party storage through your browser or contact us by email instead of using the booking embed. Platform session and CSRF cookies support sign-in and security; blocking them can prevent those functions. Optional interface preferences can be cleared through browser storage settings.
You can also control cookies at the browser level, and most browsers let you block or delete cookies and site storage via their settings menu, though doing so may affect site functionality. Consult your browser’s help documentation (Chrome, Firefox, Safari, or Edge) for how to manage cookies at the browser level.
5. Third-Party Cookies & Embedded Content
Some pages embed third-party content that may set its own cookies. In particular, the scheduling calendar on our Demo page and the “Schedule a call” buttons across the site are powered by Zoho Bookings and load booking content from magdox.zohobookings.in. No Zoho script runs on our pages: the calendar is an embedded frame that loads only when you click a booking button or open the Demo page, so Zoho receives technical connection data from that point. Zoho may then use cookies or browser storage within that frame. Booked meetings are held on Zoom, which receives the details needed to run the meeting. An organization’s configured SSO provider may also use its own session cookies on its sign-in pages. We do not control what Zoho or Zoom do with this data within their own services. Review Zoho’s privacy policy and Zoom’s privacy statement directly for details.
Our Contact page and the newsletter signup in the site footer submit form data through a server-side relay we operate to Zoho CRM; your browser never connects to Zoho directly and Zoho sets no cookie through these forms. Newsletter contacts recorded in Zoho CRM are emailed through Zoho Campaigns; review Zoho’s privacy policy for details on how they handle submitted data. Subscriptions are invoiced directly by MAGDOX Private Limited, so no billing cookies are set through this site.
The marketing website is delivered through Cloudflare, which provides DNS, TLS and edge delivery, runs the relay described above, and provides the cookieless Web Analytics described in Section 2. Depending on enabled features, Cloudflare may set security cookies such as __cf_bm or cf_clearance, including without an interactive challenge. Such a cookie exists to distinguish a browser from automated traffic, is not used for tracking, and is disclosed in Cloudflare’s cookie documentation.
We do not deploy advertising or retargeting trackers. Third-party embedded services have their own policies and settings. Any optional storage requiring consent must be assessed and configured accordingly; a provider link does not itself obtain that consent.
6. Changes to This Policy
We may update this Cookie Policy as our use of cookies and storage technologies changes. The “Last updated” date at the top of this page reflects the most recent revision. See also our Privacy Policy.
7. Contact
Questions about this Cookie Policy can be sent to [email protected] or via our Contact page, or by post to:
MAGDOX Private Limited
St No. 8, Arabinda Nagar, Barbani, Bardhaman, Hindustan Cables, West Bengal 713335, India