Hi @frenkie19
The first plugin version took inspiration from the Stripe and Paypal plugins’ code. Stripe sends all this info, and more (detailed info about what the user purchased) to its own backend.
We had a dashboard in the works and it seemed like we might want to display order IDs, client name and related info about the client in our merchant dashboard so we decided to at least keep that that info.
We do not collect any information about what was purchased.
I will raise this topic of privacy concerns internally to see if we can limit this for btc2btc or offer the option in the plugin settings (so that the merchant can choose how useful or complete the info in the merchant dashboard is).
There is strictly no other use made of that data (internally, and certainly not shared with 3rd parties).
Regards,
TripleA Team
Apologies @frenkie19 , did not address the “moneyoverip” mention. It was the name we used for early versions of our server. Different domain name, same infrastructure.
So no 3rd party involved or privacy risk.
Regards,
TripleA Team
thanks for answer
moneyoverip api is fine,as its used to generate qr code and verify transaction,but i would really like to get rid of that part of sending customer details because i will have to declare it in privacy policy to not get penalised by some institution at some point.
also is public key being sent to your api after activating it in backend?
can you put some code here or details how to stop sending this data?
Hi @frenkie19 ,
The public key is sent once to our API, for account activation. We generate an API ID which is used thereafter. No user will ever see your public key in any connections on the front-end.
The public key is used internally by TripleA to monitor incoming payments.
Please reach out to [email protected] and mention your username (frenkie19) so that we can show you how to adjust the code.
(As the code is open-source and you clearly had a look, you may also just experiment and comment out some parts.)
Regards,
TripleA Team
