Formal Complaint Regarding Unjustified Warning and Account Name Handling

Hello. I am submitting an official complaint regarding the warning issued to me in the game Skate related to the automatically imported nickname "crystalmeth" which I did not choose, did not confirm, and had no ability to modify. I emphasize that this nickname is not my EA account name and was inserted into the game from Steam without my consent, without confirmation, and without any in-game mechanism to change it. My EA account contains a completely compliant nickname that adheres to EA’s rules. Therefore the warning was issued not due to my own actions, but due to a technical defect in the game Skate for which EA as the provider of the digital service is responsible. This situation constitutes a breach of digital content quality standards and fundamental principles of fair and responsible service provision. The game uses data from an external platform (Steam) without user confirmation and disregards the primary EA profile information, which is a functional defect incompatible with digital goods quality requirements including international norms such as the Digital Services Act and Consumer Rights Regulations. The developer failed to ensure correct integration and functional reliability of the nickname display system. Shifting the consequences of technical faults onto the user violates the principle of due care and responsibility. Because Skate lacks any mechanism to edit or change the displayed nickname, the user is deprived of the ability to comply with EA’s own rules, which renders the warning legally and logically unsound. Requiring the user to change their nickname on Steam, a third-party platform outside EA’s ecosystem, exceeds the legitimate scope of user responsibility. Issuing a warning based on data the user did not select, cannot control, and cannot modify constitutes a potential case of improper digital service practice. The game includes a feature allowing users to hide other players’ nicknames. However, even when I enable this setting, meaning I cannot see other players’ names, my nickname remains fully visible to them. This is an inconsistent and illogical implementation of a privacy-related function. If I am prevented from viewing other players’ names, then by the same design principle my name should not be visible to other players either. The current implementation violates basic symmetry of privacy settings and creates an unreasonable situation where the user cannot protect their display name despite activating a feature intended to control name visibility. The game does not provide a proper or reliable solo-play mode that would allow the user to isolate their gameplay and avoid online exposure. As a result, even if a player wishes to avoid interacting with others or prevent their nickname from being displayed, the game design does not provide any technical means to do so. Because the game forces online visibility and does not offer a legitimate solo option, users cannot control when and how their nickname is shown to others. Issuing a warning under these conditions is unjustified because the user has no technical way to restrict visibility or to comply with EA’s rules. I request immediate removal of the warning as it was issued due to defective product functionality, not user misconduct. I request an official explanation why the game does not use the EA account nickname when accounts are linked, why the game lacks functionality to change or confirm the displayed nickname, and when EA intends to fix the faulty Steam–EA integration logic. I request clear instructions on how to change the nickname specifically for Skate without altering the Steam nickname, as the current implementation makes compliance with EA policies technically impossible. If a justified and timely resolution is not provided, I reserve the right to escalate the matter to regulators overseeing digital service quality and safety, consumer protection authorities, and agencies handling cases of digital content non-compliance. This situation may fall under issues related to defective functionality, misleading integration, and preventing the user from complying with policy requirements due to technical limitations of the product. I await an official and substantive response. Thank you.