cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Constant eBay GDPR notifications on my application?

Wondering if anyone else has experienced this or might know what's going on. My application is showing constant logs from eBay of MARKETPLACE_ACCOUNT_DELETION notifications with seemingly randomly generated eBay usernames, none of the users are in my database. AI is telling me its test data from eBay to make sure my app is GDPR compliant which makes sense, but doesn't explain the sheer volume. It is a 24/7 constant flow of notifications hitting my GDPR endpoint which is significantly running up my usage on my hosting platform. Is this normal?

Message 1 of 2
latest reply
1 REPLY 1

Constant eBay GDPR notifications on my application?

Yes, completely normal.

 

It is because when you connect your APP to ebays API's, ebay does not know what user account information your APP or Service has downloaded data from eBay. (well they do, but they dont remember it).

 

It makes sense if your APP is used by millions of people who all connect to eBay using your app. When one of those users deletes their account, then your APP gets a notification to delete their data from your APP.

 

If your APP has a single user, i.e you, then the millions of delete requests can be discarded as they're never going to have used your APP, so there is no data to delete.

 

Its a completely stupid and unscalable solution implemented by eBay. When someone deletes their eBay account, lets ping EVERY SINGLE DEVELOPER to tell them to delete that users data, on the slim chance that they used your APP.

 

My APP logs requests to MySQL, and my database is currently recording about 13,200 account deletion notifications per week. Records older than 1 week are deleted so I store the last 1 weeks of requests. I'm never going to need to action on any of them, as my APP only has one user, that's me.

 

If you're techincally minded, you may be able to offload the account closure endpoint to a lambda function at AWS and respond with the appropriate "Yes, ive seen this" code and just discard them (or log them if needed). The lambda costs shouldnt be huge, but needs some knowhow.

Message 2 of 2
latest reply