Support Central

woodsy

Hi,

I will share with the team for further consideration.

Regards

I am annoyed with google introducing this payment structure - it is a big potential problem for developers

I think all sites produced for clients will mean an individual maps account being set up by the client and the client then adding their own payment details - otherwise the developer could be exposed to future charges down the line (however long that may be)

Google does say a $200 free credit per month is added to an account but if a developer has made lots of sites and created many maps this may not be enough

How it will work with users who have decided to not use extensions and instead have embedded the map nobody seems to know - at least Google maps support didn't when I asked

So I think alternates to Google would be a good idea

Also consider GDPR! Openstreetmap is here a suitable alternative to googleMaps

With the maps2 extension I'm not how this impacts on GDPR - can you explain?
I appreciate Germany has many keen lawyers but I'm uncertain how this extension would involve GDPR

The extension doesn't have directions on it so it does not involve google knowing your location and the extension being on a website does not log any locations

But quite possible I may have missed something as GDPR is a huge area

Cheers
Paul

Hi Paul, If the extension doesn't have directions,...so there should be no proplem about that..

"GDPR is a huge area" ...thats true. Oh yes, and it's hardly possible to understand everything on the quick.

I read this here in a blog about GDPR:

"I regard the embedding of Google Maps in a website as questionable under data protection law, as a so-called NID cookie is stored on the user's computer:

According to Google's own information, this is not only used to save preferred settings for Google search (such as language and Google SafeSearch filters), but also to customize ads in Google products such as Google Search.

Additionally loaded by embedding Google Fonts and establishing various other connections to Google servers in the background, through which IP addresses and other data, such as browser and operating system, are transmitted to Google. However, this is to be expected in the case of a connection to a third party service.

However, Google still seems to be working on making Google Maps DSGVO-compliant"

Translated with www.DeepL.com/Translator

Anyway, I think that Openstreetmap is an important alternative.
Cheers Frank

Hi Frank,

Yes using an embedded map does seem to be a problem in regard to GDPR in some European countries and in particular Germany

I think the JBMaps2 extension will be fine.

Google fonts does log the IP for its own analytics which can be seen as problematic - in my country UK I don't anticipate a problem (despite Brexit we have implemented this law) as we are not as strict as Germany.

I'd suggest if worried using font packs and embedding the fonts that way using css rather than using the template google font options

But yes absolutely take your point in regard to openstreetmap

Cheers
Paul