Penny’s Big Breakaway

Penny’s Big Breakaway

View Stats:
snackerfork Feb 23, 2024 @ 1:01pm
5
Clarification on telemetry/data harvesting behaviors
In another thread about the game’s privacy policies, there’ve been a number of claims that Penny’s Big Breakaway has multiple EULAs because it's collecting data, and that it's collecting data from places that it shouldn’t like emulator folders and OneDrive folders.

After researching myself by forcing the game to crash (this is pretty easy to do by rapidly swapping resolutions, especially by using both a keyboard and a controller simultaneously), discussing this further with other people on Discord servers I’m in, and checking Process Monitor while the game is running, I feel fairly confident in saying that the claims about this game collecting data are partially true, but are unlikely to be malicious.

I can say for sure that the game is reading files and folders that it shouldn’t. When I ran Process Monitor without crashing the game, I didn’t see anything out of the ordinary. But when I crashed the game, Process Monitor reported that it was doing a bizarre CreateFile operation on a public folder in my NAS, and a person on a server I’m in saw my crash dump had the names of text files in my Documents folder and even a part of my non-steam email address. Which is definitely alarming!

Without developer tools, it’s not really possible to do anything but conjecture (and the person I spoke with acknowledged they’re not an expert), but my suspicion and theirs is that the game was left configured for development and debugging, so debugging functionality that scanned the entire filesystem wasn’t turned off. Here’s what they said:

“ok yea after looking at that: just conjecture on my part but i think this is just a crashdump configured for a dev environment and not an end user one?? i dont think its malicious but i def dont think it should be snooping for some of this info lol

mostly its just weird pointers to text files and dll's”

This is also supported by the crash dump having a “Jenkins_remote” environment path, specifically pointing to: C:\Jenkins_remote\workspace\Project Yo\ProjectYo Steam\EXE\ProjectYo Steam.pdb. Jenkins is automation software used by software developers for purposes such as debugging and analysis.

This is still speculation until the developers release any statement, but it seems more likely to me that the game is collecting more data than it should by mistake instead of for malicious purposes, and that the EULA is boilerplate publisher legalese that exists to legally protect the publisher from these scenarios rather than forcing you to “consent” to data harvesting.
Last edited by snackerfork; Feb 23, 2024 @ 1:06pm
< >
Showing 1-15 of 25 comments
favtabby Feb 23, 2024 @ 1:31pm 
there's also not really reason to believe that the publisher or developer is collecting the data, it's just being collected in the crashdump file which afaik only the user has access to. I don't think there's much to worry about here unless you post the crashdump online.

also I think it's likely that all the EULAs at the start of the game are just a requirement from the publisher end to cover all of their bases, it isn't necessarily a sign that the game is actually collecting and sending your personal data. pretty sure that if it did it would have to ask for your permission and let you opt out cause of GDPR.
Last edited by favtabby; Feb 23, 2024 @ 1:39pm
snackerfork Feb 23, 2024 @ 2:03pm 
Yeah, that's my feeling as well, and this is a good example of why they have those. If they didn't have all that legalese you have to agree to, someone could arguably attempt to sue if they could claim that the accidental data collection caused them damages (especially if it was automatically sent to the developer as part of debugging.)

Which doesn't actually justify EULAs, which are questionably enforceable regardless, but that would be the publisher's perspective on it.
Last edited by snackerfork; Feb 23, 2024 @ 2:04pm
SneakyBeat Feb 23, 2024 @ 2:06pm 
Guess I'll avoid my refund request for now. Still not playing further until some bugs get squashed.
eispfogel Feb 23, 2024 @ 8:47pm 
I also don't think they are malicious and that the collection is like you said - some misconfigured log collection. But still...after so many disclaimers when starting the game...i had a bad feeling :/

We will see what happens. Meanwhile...i will play this on other Platforms(i wish it would also be on PS4..)
Fubuki Feb 24, 2024 @ 6:23am 
It's one thing when a game grabs data secretly without your knowledge, but the very first EULA that pops up specifically states it WILL grab any data on you it can find and sell it to third parties. Not something I'm willing to support.
snackerfork Feb 24, 2024 @ 12:45pm 
Originally posted by Fubuki:
It's one thing when a game grabs data secretly without your knowledge, but the very first EULA that pops up specifically states it WILL grab any data on you it can find and sell it to third parties. Not something I'm willing to support.

As others have discussed that would be a gigantic violation of the GDPR and would get them fined millions. Haven't you noticed that every website you use requires you to explicitly consent to cookies and offers an option to disable "non necessary" cookies? That's GDPR.

GDPR is even stricter about children (defined as those 16 or under) and this game is both available to and marketed to much younger children. The EULA exists to, VERY questionably considering it is unclear as to if they are legally enforceable, protect them from being sued in case this collected debug data *was* sent out accidentally.

But there is zero chance that this is happening intentionally, for reasons stated above (the data isn't collected at runtime and is attached to a vestigial debug software environment path so it is unlikely to be automatically transmitted) and increasing EU privacy regulation such as GDPR.
Last edited by snackerfork; Feb 24, 2024 @ 12:58pm
snackerfork Feb 24, 2024 @ 1:25pm 
GDPR Article 7, Recital 32:

"1. Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject’s agreement to the processing of personal data relating to him or her, such as by a written statement, including by electronic means, or an oral statement.

2. This could include ticking a box when visiting an internet website, choosing technical settings for information society services or another statement or conduct which clearly indicates in this context the data subject’s acceptance of the proposed processing of his or her personal data.

3. Silence, pre-ticked boxes or inactivity should not therefore constitute consent.

4. Consent should cover all processing activities carried out for the same purpose or purposes.

5. When the processing has multiple purposes, consent should be given for all of them.

6. If the data subject’s consent is to be given following a request by electronic means, the request must be clear, concise and not unnecessarily disruptive to the use of the service for which it is provided."

The in game privacy policy (which is what data is covered by, NOT the EULA which defers to the privacy policy) would certainly fail 3 because this is a "pre-checked box" with no option to continue without accepting. It would likely fail 5 because there is only one "accept" box, and 1 because it is not informed or unambigous (due to 5).

Recital 42:

"5. Consent should not be regarded as freely given if the data subject has no genuine or free choice or is unable to refuse or withdraw consent without detriment."

There is no available option to refuse consent or an ability to withdraw in game. An email doesn't count, it has to be accessible.

Article 8:

"1. Where point (a) of Article 6(1) applies, in relation to the offer of information society services directly to a child, the processing of the personal data of a child shall be lawful where the child is at least 16 years old. 2. Where the child is below the age of 16 years, such processing shall be lawful only if and to the extent that consent is given or authorised by the holder of parental responsibility over the child."

Point A of Article 6 states data processing is lawful if "the data subject has given consent to the processing of his or her personal data for one or more specific purpose." This game is marketed towards and available to children and makes no effort to seek authorization from a parent or guardian.

This is all to say that while 2K could be selling your data, they'd also be putting themselves in legal hot water. Privacy online is a nightmare but there's no *more* rational reason to be concerned about the EULA and privacy policy in this game than, say, your usage of Steam, your web browser, Youtube, or your phone.
Last edited by snackerfork; Feb 24, 2024 @ 1:27pm
valcan_s Feb 24, 2024 @ 3:15pm 
Don't you think the developer, community manager or even publisher should of said something by now? I love to support indie shops, early access and anyone that needs help but this is really disappointed that we have had no communication on the matter.

Having said that I have over a 1000 games in my library and there is no other game that has this many EULA and they don't keep on popping up each time you play let alone do anything this game is doing with your files. On the indie side I can easily say the majority don't even have a EULA, so this is a really odd situation and we should be concerned.

I really hope the devs don't know about this and it was part of the deal cause that is a really sh-ity way to begin there portfolio post Sonic Mania.

Still holding on before I refund it but I won't play it till someone clarifies the matter. The clock is ticking till I reach the 13 day mark.

Will see hey.
snackerfork Feb 24, 2024 @ 4:18pm 
I agree it's concerning but I genuinely think the best approach for your concerns is to email or contact the developers. I'm not sure they're reading the Steam forums currently which is part of why I'm kind of playing armchair community manager here...

The devs almost lost their livelihoods due to Sega which is why I care this much. Please give them a fair shake when Take Two is the cause and this seems to be accidental and not malicious.
favtabby Feb 24, 2024 @ 4:53pm 
While the developer Evening Star is indie, the publisher of this is the furthest thing you could get from indie. Private Division is a branch of Take Two, the parent company of 2K and Rockstar. And they're the reason that the EULAs are included. Penny's Big Breakaway is far from the only game that makes you agree and scroll through a bunch of legal text, mainly cause the legal departments of big companies like Take Two tend to want to cover as many bases as possible even when it isn't necessary.

And the EULAs for this game aren't actually for the ways in which the game may collect data, but rather for the ways in which Take Two may collect data. And that includes things like logging into Take Two's website, their website using cookies to collect data, any information you might send when talking to customer support etc. The terms of service in the game do specifically explain that they are including stuff like that.

Basically, the terms of service aren't for the game Penny's Big Breakaway, they're for using any Take Two product, and it's covering the bases for any way shape or form Take Two might collect data in or outside this specific product. It's Take Two's terms of service, not Penny's Big Breakaway's terms of service, after all.

By the way, they did do the work to make the game comply to GDPR rules. The game's time attack mode collects your Steam name and stage time to post it online, and the game asks you to let it post that information online before it does it. And you can then still toggle it on/off in the game's options.
Last edited by favtabby; Feb 24, 2024 @ 5:00pm
snackerfork Feb 24, 2024 @ 5:34pm 
Also worth mentioning a game like this generally can't survive without a publisher. Indie games that are successful without publishers are a *huge* exception. Games are expensive and difficult to make and have very long development times and the people who make them have livelihoods all the while.

Please try to be sympathetic to the developers when their contract puts Take-Two's EULAs and privacy policy out of their hands.
Last edited by snackerfork; Feb 24, 2024 @ 5:35pm
Fubuki Feb 25, 2024 @ 6:49am 
Originally posted by snackerfork:
Please try to be sympathetic to the developers when their contract puts Take-Two's EULAs and privacy policy out of their hands.
I'll be more sympathetic when they actually comment on it, I'm not going to just blindly trust Take-Two to do the right thing without any confirmation, especially when we know the game is already scraping your filesystem and ram (for debugging purposes?).

That said, I really want to support Evening Star, they have shown they can make some really amazing and unique games and are just extremely talented at what they do. I'll be keeping an eye out for a statement as to what exactly is going on, but until then I can't support this.
L.Brown Feb 25, 2024 @ 1:49pm 
Thanks for bringing this to my attention, because of that unfortunately the game has become a nogo for me...
Hunter Bridges (ES)  [developer] Feb 26, 2024 @ 10:34pm 
2
Hi everybody, thank you for your patience.

My name's Hunter Bridges, I'm the Game Director of Penny's Big Breakaway. I also served as the Technical Director. I work with my colleague Christian to build the engine of the game, and also guide our engineers in building out the rest of the game logic. I have a clear idea of what code is contained within the application.

There have been several concerns expressed here. There are also concerns expressed within Steam reviews. Thanks for your patience. This week we are going to be taking the time to respond to various concerns from the community.

(Also apologies if I don't have the developer badge yet on my Steam profile. We were working to get that set up today and I'm not sure if it went through. I'm also on Twitter as @HunterBridges)

OK so first, let's talk about the EULA and other Legal Agreements you have to agree to on first boot.

Since our game was published by Private Division, who is indeed part of Take 2 Interactive, we are obligated to abide by the same requirements as all of Take 2's titles and use their standard agreement language. We are required to have the EULA, Privacy Policy, Terms of Service, and a Photosensitivity Warning.

You can find the verbatim text for the agreements on Take 2's website, and you'll find it's the same as the text in the game:

https://www.take2games.com/eula/en-US
https://www.take2games.com/privacy/en-US
https://www.take2games.com/legal/en-US
https://www.take2games.com/photosensitivity/en-US

So those agreements are what they are. If you have specific issues or questions regarding the language, I suggest you contact them. Evening Star has no control over the contents of these agreements.

There are also users who are reporting having to accept the legal terms on every boot. If that's happening to you, that's a bug, so please provide us more info if you're hitting it.

Next, let's discuss telemetry gathering and concerns of data scraping.

We do not have any data telemetry instrumentation in the game. If any title collects player telemetry, it must comply with GDPR data warehousing regulations.

We use platform services for features like cloud saves, leaderboards, achievements, rich presence, etc. Each version of the game (Steam, Switch, PS5, Xbox) uses service back-ends provided by each platform. Evening Star does not store this data ourselves.

If a user were to run a packet sniffer on the application, the results should line up with what I'm saying here.

OP mentioned having a Crash Dump being created in a NAS folder when the game crashed. The Crash Dump handler is actually open source third party code. Here links to two places in the code that tap the file system:

https://github.com/beefytech/Beef/blob/master/BeefySysLib/platform/win/CrashCatcher.cpp#L579
https://github.com/beefytech/Beef/blob/master/BeefySysLib/platform/win/CrashCatcher.cpp#L1224

We write our game logic in a new programming language called Beef[www.beeflang.org].

The Windows platform runtime adapter for Beef provides this Crash Catcher which attaches to a SIGABRT and lets the user save out a mini crash dump. It's handy for debugging purposes; we have this so players can send us crash dumps if they run into crashes or critical issues.

The behavior of the Crash Catcher assumes your default path to be a local directory. It is possible that if a file was saved on the NAS before the crash event, the previous file path could have carried over and the crash dump was saved to the NAS path.

Also, the CrashCatcher module is a tool to help us address bugs, but it is not necessary. If the community overwhelmingly opposes its inclusion, we are happy to remove it.

I know there is a lot of concern around data privacy. We treat player privacy seriously. We are also very aware of the responsibilities for parties who harvest and warehouse data. We don't collect telemetry, we don't want to harvest your data.

I hope this explanation clarifies a few things, and also confirms our intent regarding data.

Thanks also to everybody for supporting Evening Star and enjoying the game.
ChickenShred Feb 27, 2024 @ 3:52am 
Originally posted by Hunter Bridges (ES):
Hi everybody, thank you for your patience.

My name's Hunter Bridges, I'm the Game Director of Penny's Big Breakaway. I also served as the Technical Director. I work with my colleague Christian to build the engine of the game, and also guide our engineers in building out the rest of the game logic. I have a clear idea of what code is contained within the application.

There have been several concerns expressed here. There are also concerns expressed within Steam reviews. Thanks for your patience. This week we are going to be taking the time to respond to various concerns from the community.

(Also apologies if I don't have the developer badge yet on my Steam profile. We were working to get that set up today and I'm not sure if it went through. I'm also on Twitter as @HunterBridges)

OK so first, let's talk about the EULA and other Legal Agreements you have to agree to on first boot.

Since our game was published by Private Division, who is indeed part of Take 2 Interactive, we are obligated to abide by the same requirements as all of Take 2's titles and use their standard agreement language. We are required to have the EULA, Privacy Policy, Terms of Service, and a Photosensitivity Warning.

You can find the verbatim text for the agreements on Take 2's website, and you'll find it's the same as the text in the game:

https://www.take2games.com/eula/en-US
https://www.take2games.com/privacy/en-US
https://www.take2games.com/legal/en-US
https://www.take2games.com/photosensitivity/en-US

So those agreements are what they are. If you have specific issues or questions regarding the language, I suggest you contact them. Evening Star has no control over the contents of these agreements.

There are also users who are reporting having to accept the legal terms on every boot. If that's happening to you, that's a bug, so please provide us more info if you're hitting it.

Next, let's discuss telemetry gathering and concerns of data scraping.

We do not have any data telemetry instrumentation in the game. If any title collects player telemetry, it must comply with GDPR data warehousing regulations.

We use platform services for features like cloud saves, leaderboards, achievements, rich presence, etc. Each version of the game (Steam, Switch, PS5, Xbox) uses service back-ends provided by each platform. Evening Star does not store this data ourselves.

If a user were to run a packet sniffer on the application, the results should line up with what I'm saying here.

OP mentioned having a Crash Dump being created in a NAS folder when the game crashed. The Crash Dump handler is actually open source third party code. Here links to two places in the code that tap the file system:

https://github.com/beefytech/Beef/blob/master/BeefySysLib/platform/win/CrashCatcher.cpp#L579
https://github.com/beefytech/Beef/blob/master/BeefySysLib/platform/win/CrashCatcher.cpp#L1224

We write our game logic in a new programming language called Beef[www.beeflang.org].

The Windows platform runtime adapter for Beef provides this Crash Catcher which attaches to a SIGABRT and lets the user save out a mini crash dump. It's handy for debugging purposes; we have this so players can send us crash dumps if they run into crashes or critical issues.

The behavior of the Crash Catcher assumes your default path to be a local directory. It is possible that if a file was saved on the NAS before the crash event, the previous file path could have carried over and the crash dump was saved to the NAS path.

Also, the CrashCatcher module is a tool to help us address bugs, but it is not necessary. If the community overwhelmingly opposes its inclusion, we are happy to remove it.

I know there is a lot of concern around data privacy. We treat player privacy seriously. We are also very aware of the responsibilities for parties who harvest and warehouse data. We don't collect telemetry, we don't want to harvest your data.

I hope this explanation clarifies a few things, and also confirms our intent regarding data.

Thanks also to everybody for supporting Evening Star and enjoying the game.

So to be clear, the only software in the game that is collecting data is Crash Catcher/Beef right?
< >
Showing 1-15 of 25 comments
Per page: 1530 50