Jump to content

Why prestashop is asking for so much of personal data on installation, even DB password?


Saahib

Recommended Posts

Hi,

After seeing so much of praise, I decided to give prestashop a try for my new project. To try it, I first went to install on my test local machine on windows running custom stack of apache/php7.1/mysql5.6 .

I encountered error during installation where it is not moving ahead and creating default db records (that's not for this topic, still have added screenshot below)

presta-blank.thumb.jpg.9db750dfe414a699f7a567faefad395a.jpg

Well, in order to troubleshoot, I happen to delete all files and extracted new files, but to my surprise installer started from where I left last, even though its again fresh installation. It means, prestashop is storing installation information on their server.

To bigger surprise, there was my password also stored with them.

I then headed to their privacy page, which says :

https://www.prestashop.com/en/personal-data-protection-policy-prestashop-download

presta-data-storage.jpg.6fd5e566cac7c9f91981868016bb3553.jpg

 

It says that you collect "database name, prefix , db identifier and Database" info from "Prestashop solution installer form".

Why on this earth you need to store each installations database and its password ?
What kind of policy is that ?

Please explain ?

Link to comment
Share on other sites

1. I discovered that there is no choice to opt-out for sharing personal data when you install PS.

2. If you decide to continue, PS is asking to save everything ie. DB, DB name, DB pass, DB server address and what not.

Do they really need to know all this, it feels as if you use PS then PS guys own you. 

 

Link to comment
Share on other sites

If I don't remember wrongly, Prestashop is open source..

5 minutes are enough to verify in the source code that no db data is sent to Prestashop
(it would have been crazy otherwise, I guess 🤣).

AJAX API calls made by the installer only send data relating to the ISO code / country of installation.

I'm pretty sure that when OP relaunched the installation,
a browser cookie was found which led the install script to an advanced installation step.

It is a very common scenario that has happened to me several times too.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...