is there a possibility to use leaflet.js in a gdpr compliant way? the reason is, all/most api calls to map servers which leaflet.js does, creates 3rd party cookies. these cookies are not alloed by the gdpr law before the visitor makes an opt in decission to use the maps api (osm, gmaps,...). so my question is, does leaflet.js has a kind of property or way to prevent these api calls until a specific event (for instance an opt-in by user) gets triggered by js? for instance similar to google analytics approach with ga-disable-UA-XXXXXX-X?
Asked
Active
Viewed 699 times
4
-
Use your own tile server. – IvanSanchez Apr 16 '20 at 12:50
-
using an on tile server is not possible in this scenario. – matthias Apr 16 '20 at 12:53
-
Then this is a question about tile/geocoding services, and not about Leaflet itself. – IvanSanchez Apr 16 '20 at 13:02
-
yes in some case. tile/geoconding should be prevented until the user made an opt-in. should i change anything in my text/headline? – matthias Apr 16 '20 at 13:06
-
The obvious answer is gonna be "don't add any tilelayers to the map before some event happens", which falls on your part. Perhaps you might want to put examples of the tile/geocoding services you're worried about, and focus on that. – IvanSanchez Apr 16 '20 at 14:08
-
Could you already find a solution for this? Maybe something like embetty could be used to wrap leaflet: https://github.com/heiseonline/embetty/issues/403 – Stefan Jun 22 '22 at 10:43
-
Another library that might be helpful: https://github.com/orestbida/iframemanager https://github.com/orestbida/iframemanager/issues/19 – Stefan Jun 22 '22 at 10:57
-
yes i solved it, as @IvanSanchez mentioned – matthias Nov 29 '22 at 12:21