GDPR and Maglr
At Maglr, we are always focused on complying with GDPR legislation. Things could change a bit when you are making adjustments to the dashboard settings, add external embeds or use third-party tools like Google Tag Manager.
We do not store any personal data from viewers. A publication in Maglr is just like a static HTML website. Viewers can click through the page without being tracked on a personal level.
By default Google Analytics is set as 'anonymous'. This means that certain data is captured and sent to Google, but without any relations to a user or computer (IP address). For example, the last few figures of an IP address are left out and marketing cookies & services are disabled.
Disabling this 'anonymous' option is possible, but keep in mind that you need to set a cookie consent for this.
Note: when adding extra third party tools or activating the Google Analytics without the anonymous mode, keep in mind to add a Cookie Consent popup. This can be done manually through Google Tag Manager.
In case Google Analytics is not an option, we offer our native analytics. This privacy friendly solution does not make use of cookies. Data is measured and stored anonymous at server in Germany (EU). For more details about these stats check our docs.
Just like any other website, Maglr uses cookies. These cookies are not used to store personal data. We use these cookies for functional parts inside a publication. For instance: to remember that a viewer has already seen a specific notification. Click here to read more.
When an e-mail form is used inside a publication, it will directly generate an e-mail and send it to the Maglr customer. We are not storing any of these details on our servers.
For the subscription form, the same rules as the e-mail form apply. New subscriptions are sent by default through e-mail. We are not saving any of these details on our server. It is possible to connect your form and its subscribers to Zapier. In this situation, you are able to forward details directly to MailChimp. In this scenario, data is stored at MailChimp and nothing is kept with us.
For web-notifications, we are only saving an anonoymous (hashed) key, which is linked to a specific webbrowser (in combination with a domain) by Google. Any notification you send out is communicated via this key, sending it to the specific browser/domain corresponding with it. In this case only the anonymous key is stored on our servers, making it impossible for us to know who/what is connected to it.
When using an Enterprise Single Sign-On connection we do have access to a personal profile of the user. These details are on a session-based level. We are not storing any of these personal data points in our database. We are only storing a unique userID for login purposes.
By default, Youtube videos are loaded from a no-cookie source. As long a video has not started, no cookies will be saved on your computer. When activating a strict cookie consent Youtube videos will only be loaded after consent. When a visitor would reject a resend and plays a video, the consent is first needed before loading the video.
When using URL parameters to personalise publications, you are sending private details to our server (depending on the contents of course). We do not store these details. Content from the URL parameters will be merged instantly when opening the page.
For Maglr users with access to the Maglr dashboard, in contrast to publication visitors, we do save personal data. These users need to login & authenticate, but also need to be helped via live chat sessions.
For dashboard users :
We store basic user credentials
We store basic company details with license & payment info
We use Pipedrive & Crisp for chat & CRM
We (sometimes) use Microsoft Clarity to better understand user behaviour on our website
We use Sentry for error tracking
When using our additional personalisation module inside Maglr, different rules apply. In this situation, we do store personal data on our servers. Data filled in by a sales rep is stored in our database and is used to create a personal presentation. For the use of this module, a data agreement needs to be set-up between Maglr and the customer.
With this module we save:
Name and e-mail address of customer receiving the personalised publication
Tracked through Pirsch with a unique userID
Saving additional data set-up by the dashboard user
The above details are not available through the dashboard, after sending a personalised publication, the e-mail address is semi masked for the dashboard user itself. This module is really used as a one-time option to send out a presentation.
Visitors inside a publication
Personal data
We do not store any personal data from viewers. A publication in Maglr is just like a static HTML website. Viewers can click through the page without being tracked on a personal level.
Google Analytics (when activated)
By default Google Analytics is set as 'anonymous'. This means that certain data is captured and sent to Google, but without any relations to a user or computer (IP address). For example, the last few figures of an IP address are left out and marketing cookies & services are disabled.
Disabling this 'anonymous' option is possible, but keep in mind that you need to set a cookie consent for this.
Note: when adding extra third party tools or activating the Google Analytics without the anonymous mode, keep in mind to add a Cookie Consent popup. This can be done manually through Google Tag Manager.
Maglr analytics
In case Google Analytics is not an option, we offer our native analytics. This privacy friendly solution does not make use of cookies. Data is measured and stored anonymous at server in Germany (EU). For more details about these stats check our docs.
Functional cookies
Just like any other website, Maglr uses cookies. These cookies are not used to store personal data. We use these cookies for functional parts inside a publication. For instance: to remember that a viewer has already seen a specific notification. Click here to read more.
E-mail forms
When an e-mail form is used inside a publication, it will directly generate an e-mail and send it to the Maglr customer. We are not storing any of these details on our servers.
Subscription forms
For the subscription form, the same rules as the e-mail form apply. New subscriptions are sent by default through e-mail. We are not saving any of these details on our server. It is possible to connect your form and its subscribers to Zapier. In this situation, you are able to forward details directly to MailChimp. In this scenario, data is stored at MailChimp and nothing is kept with us.
Subscription (web)notifications
For web-notifications, we are only saving an anonoymous (hashed) key, which is linked to a specific webbrowser (in combination with a domain) by Google. Any notification you send out is communicated via this key, sending it to the specific browser/domain corresponding with it. In this case only the anonymous key is stored on our servers, making it impossible for us to know who/what is connected to it.
Enterprise SSO
When using an Enterprise Single Sign-On connection we do have access to a personal profile of the user. These details are on a session-based level. We are not storing any of these personal data points in our database. We are only storing a unique userID for login purposes.
Youtube video
By default, Youtube videos are loaded from a no-cookie source. As long a video has not started, no cookies will be saved on your computer. When activating a strict cookie consent Youtube videos will only be loaded after consent. When a visitor would reject a resend and plays a video, the consent is first needed before loading the video.
Personalisation tags
When using URL parameters to personalise publications, you are sending private details to our server (depending on the contents of course). We do not store these details. Content from the URL parameters will be merged instantly when opening the page.
Customers working inside the Maglr dashboard
For Maglr users with access to the Maglr dashboard, in contrast to publication visitors, we do save personal data. These users need to login & authenticate, but also need to be helped via live chat sessions.
For dashboard users :
We store basic user credentials
We store basic company details with license & payment info
We use Pipedrive & Crisp for chat & CRM
We (sometimes) use Microsoft Clarity to better understand user behaviour on our website
We use Sentry for error tracking
Additional personalisation module inside the dashboard
When using our additional personalisation module inside Maglr, different rules apply. In this situation, we do store personal data on our servers. Data filled in by a sales rep is stored in our database and is used to create a personal presentation. For the use of this module, a data agreement needs to be set-up between Maglr and the customer.
With this module we save:
Name and e-mail address of customer receiving the personalised publication
Tracked through Pirsch with a unique userID
Saving additional data set-up by the dashboard user
The above details are not available through the dashboard, after sending a personalised publication, the e-mail address is semi masked for the dashboard user itself. This module is really used as a one-time option to send out a presentation.
Updated on: 28/03/2024