Articles on: General questions (f.a.q.)

The use of cookies

This article lists the cookies Maglr sets in published projects, the third-party services that can add their own cookies to your publications, and the data Maglr uses in the dashboard and editor. For questions about Maglr's GDPR and privacy compliance, contact support@maglr.com.


Cookies and data in Maglr: overview


Maglr handles data in two places: the projects you publish, and the dashboard and editor you work in.


  • Published projects: Maglr itself sets only a few functional cookies, and the standard Maglr statistics are cookieless. Third-party cookies come from Google Analytics, Google Tag Manager, embedded videos or other embedded content you add, and from Google reCAPTCHA in the side menu forms. Forms collect what viewers fill in.
  • Dashboard and editor: Maglr stores your account details and uses a few services for chat, error tracking and user insights. The statistics you see in the dashboard about your viewers are anonymous.


Cookies set in published projects


Maglr sets the following functional cookies in the browser of viewers who open a published project. Each cookie except the session cookie appears only when the related feature is in use.


  • PHPSESSID: a temporary session cookie that is always set. It is removed when the viewer closes the browser.
  • MaglrCookieConsent: stores whether the viewer accepted (true) or rejected (false) cookies. It is only set when Activate cookie consent notification is switched on for the domain, and it is kept for one year.
  • hideNavigationTippy: set when the viewer closes the navigation help tip, so the tip isn't shown again. It is only set when Show navigation help tip is switched on in the navigation environment settings, and it is kept for one year.
  • hideRegisterTippy: set when the viewer closes the subscribe pop-up or clicks its button, so the pop-up isn't shown again. It is only set when Activate subscribe call-to-action is switched on in the navigation environment settings, and it is kept for one year.
  • submittedFormHash: set when the viewer submits a gated-content form, so the content stays unlocked. The full cookie name is submittedFormHash followed by the identifier of the gate. It is removed when the viewer closes the browser.


Viewers can remove any of these cookies themselves at any time through their browser settings.


Maglr statistics in published projects


Maglr statistics for published projects use Pirsch, a cookieless tracker. No cookies are set for Maglr statistics, and the statistics in your dashboard are anonymous. The statistics run when Activate standard Maglr statistics is switched on in the domain settings. If the cookie consent notification uses Strict mode or Manual mode, they only run after the viewer gives consent. Read more in How our native statistics work.


Third-party cookies in published projects


A published Maglr project can contain third-party cookies from the following services:


  • Google Analytics or Google Tag Manager: connected through the Google Analytics or GTM setting in the domain settings, under Statistics & integration. Google Analytics sets its own cookies, and any trackers you add through Google Tag Manager can set theirs.
  • Embedded YouTube and Vimeo videos: these video services set their own cookies when a video loads.
  • Google reCAPTCHA in the side menu forms: when the side menu shows the Contact form or the subscribe option, Maglr uses Google reCAPTCHA to block spam when a viewer submits one of these forms. reCAPTCHA sets Google cookies. When the cookie consent notification is switched on, reCAPTCHA only loads after the viewer gives consent.
  • Content you add with the Embed element: websites and tools you embed with embed code can set their own cookies. The Maglr cookie consent notification doesn't hold this content back, so check the cookies of each service you embed.


For Google Analytics, Google Tag Manager, YouTube and Vimeo videos and reCAPTCHA, the Consent mode of the Maglr cookie consent notification decides whether they run before a viewer gives consent. Trackers you add through Google Tag Manager only wait for consent if you set them up to do so. To set up the cookie consent notification and choose a consent mode, see Configure cookie consent.


Form responses in published projects


Forms in a published Maglr project collect what viewers fill in. Maglr sends each response to the email address or webhook you choose under Send response to in the form settings. Maglr doesn't keep a list of form responses or subscribers. When a response is sent by email (including the backup email Maglr sends if a webhook doesn't respond), that email, with the submitted details, is kept in Maglr's email log for up to one year and then deleted automatically.


Data used in the Maglr dashboard and editor


For you as a client, Maglr uses the following data and services:


  • We store your company details and invoice information.
  • We store your name and email address so you can log in.
  • We use Microsoft Clarity to gain insights into user behaviour.
  • We use Crisp for the chat in the dashboard. When you open the dashboard, Crisp receives your name, email address, company, profile picture and account details, so we know who you are when you start a conversation.
  • We keep your contact details and chat history in our CRM, Pipedrive.
  • We use Sentry to detect errors in the dashboard and the editor. When an error occurs, Sentry can record a replay of the session.


Maglr Data Privacy Policy


The Maglr Privacy Policy explains which data Maglr collects, how and why it is collected, how it is used, and who it is shared with. Read the Maglr Privacy Policy.


Frequently asked questions


Do Maglr statistics use cookies?


No. Maglr statistics for published projects use Pirsch, a cookieless tracker, so no cookies are set for them. The statistics you see in the dashboard about your viewers are anonymous.



The cookies Maglr itself sets in published projects are functional, and Maglr statistics are cookieless. Third-party cookies come from services such as Google Analytics, Google Tag Manager, embedded YouTube or Vimeo videos, other content you embed, and Google reCAPTCHA in the side menu's Contact and subscribe forms. If your publications use these services, you can switch on Activate cookie consent notification in the domain settings and choose a consent mode. See Configure cookie consent.


How long are Maglr cookies kept in published projects?


It depends on the cookie:


  • PHPSESSID and submittedFormHash: removed when the viewer closes the browser.
  • MaglrCookieConsent, hideNavigationTippy and hideRegisterTippy: kept for one year, unless the viewer removes them earlier.

Updated on: 20/10/2026