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.
Visitors inside a publication
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.
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.
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 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.
Cookie consent: 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.
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 Google Analytics to track all events inside the dashboard (not anonymously)
- We use FreshSales for chat & CRM
- We (sometimes) use Hotjar to understand user behaviour
- 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 Google Analytics 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.