Hacker News Reader

Comment by mrunkel | Hacker News Reader

I don’t understand the issue. If you’re already using google pay, then google is a data processor for you and you should have already received consent.

This isn’t stripe doing this, rather it’s google doing it.

View on HN

> you should have already received consent

For payment processing. Not for tracking.

Google Analytics doesn't "track" users unless explicitly configured to do so. Google Pay actually needs PII, meanwhile the worst that Google Analytics collects (but doesn't share with site owners) is IP, which Google Pay probably also collects as part of KYC regulations.

IP is considered PII in certain circumstances.

Yes, it is, but my point is that Google Pay collects more PII, including IP, so what Google Analytics does is moot.

You’re right, but also wrong. Not all collection is equal. Placing your payment data in a database that is strictly for legal purposes is different than placing in a connected database built to track users around the web.

Privacy laws allow you to keep the data only for as long as legally necessary and required. Google Analytics may keep this data indefinitely.

This is exactly what GDPR is for, right? Arguing "you've already given some data to one bit of Google, so all bets are off and they can collect and store whatever they like" is the kind of logic we want to put a stop to.

I'm sure Google always anonoymises the IP now though? They drop the last octet.

> [...] the Italian [Data Protection Agency GPDP] reiterated that an IP address is personal data and would not be anonymised even if it were shortened – given Google’s capabilities to enrich such data through additional information it holds.

> [...] DSB issued a second decision, declaring the use of Google’s IP anonymisation a useless protection measure for data transfers between the EU and the United States.

https://noyb.eu/en/update-further-eu-dpa-orders-stop-google-...

Can we verify that?

Their servers still get your IP tho and by default nothing in USA is GDPR compatible because US government can enforce leaking any info they want from company

> For payment processing. Not for tracking.

Alas there are no payment processors that don't do tracking. As I understand it, VISA and Mastercard were some of the originators of this business model.

is this any different from if another payment provider runs analytics on its own site?

The issue is that GA is outlawed, or soon to be outlawed, in some places. Bundling GA into Google Pay + Stripe likely puts some companies at legal risk without them knowing it

Right? It's technically first-party to them.

Reply on news.ycombinator.com