EU Archives

Tech Optimizer

August 4, 2026

Automated PII redaction for Amazon RDS for PostgreSQL audit logs

The article discusses a serverless pipeline for creating an irreversibly redacted and queryable archive of Amazon RDS for PostgreSQL audit logs. It sanitizes sensitive information, such as Social Security numbers, credit card details, and email addresses, before storing the clean logs in Amazon S3, which can be queried using Amazon Athena. The deployment process is facilitated by a single AWS CloudFormation template. The challenge is that pgAudit logs sensitive data in cleartext to Amazon CloudWatch Logs, which poses compliance risks under regulations like GDPR and HIPAA. While CloudWatch Logs Data Protection offers reversible masking of PII, this is insufficient for compliance needs requiring permanent separation of PII from audit evidence. The proposed pipeline creates an irreversibly redacted copy stored in Amazon S3, ensuring original values cannot be restored. The deployment requires an active AWS account with specific permissions, AWS CLI v2, a compatible AWS region, and confirmation of service quotas. The CloudFormation template has four main parameters for deployment, including ProjectName, DBInstanceClass, DBAllocatedStorage, and EnvironmentType, with sensible defaults provided. Three deployment options are available: via the AWS console, AWS CLI, or a deploy script. After deployment, users can generate test data, trigger the redaction pipeline, and verify results in Athena. The process includes steps to create a PostgreSQL table, insert records with PII, run queries, and monitor the execution of the redaction pipeline. The article emphasizes that unredacted PII remains in the source CloudWatch Logs, recommending enabling CloudWatch Logs Data Protection for added security. To clean up resources and avoid charges, users must empty the S3 buckets and delete the stack. Cost considerations for the pipeline include infrastructure costs and the expense of achieving irreversibility.

AppWizard

August 2, 2026

Prolific Team Fortress 2 collector is selling his in-game case arsenal for an estimated $100,000 — 1.7 million items collected over 10 years are enough to fund a house purchase

Vincent Stech has collected over 1.7 million Team Fortress 2 cases across multiple Steam accounts, with an estimated value of 0,000. He began this collection around late 2017 and used automated methods to accumulate the cases while avoiding detection by Valve. Stech holds approximately 17% of all publicly known TF2 cases, making it challenging to sell them without disrupting the market. He has found a buyer for his entire collection, with the transaction in progress and expected to be completed by October. Stech plans to use the proceeds from the sale as a down payment on a house.

AppWizard

July 31, 2026

Russian Mobile Carriers Waive Data Fees for State-Backed Max Messenger

Major mobile carriers in Russia, including MTS, MegaFon, Beeline, and T2, have agreed to zero-rate data usage for the domestic Max messenger, effective August 1. This initiative aims to promote the state-approved platform and discourage the use of foreign messaging apps. Subscribers will have free access to voice calls, messaging, file transfers, and other services within the Max app. Since its launch in spring 2025, Max has been integrated into state digital services and mandated to be pre-installed on all smartphones sold in Russia, resulting in nearly 70 million daily active users. This announcement follows EU sanctions against VK, the app's developer, due to allegations of its connections with the Russian FSB and surveillance capabilities, leading to the removal of VK and Max from Apple and Google app stores.

AppWizard

July 31, 2026

Russian mobile carriers to make access to Kremlin-backed Max messenger free

Mobile carriers in Russia—MTS, Beeline, MegaFon, and T2—will no longer charge data fees for the Max messenger application, effective August 1. Users can utilize Max without using their mobile data allowances, even if their data packages are exhausted. This agreement, confirmed by the Digital Development Ministry and VK, the parent company of Max, allows for zero-rated traffic for the app when connected to the carrier's home network. However, the Max messenger was recently removed from the App Store due to international sanctions, and Google also removed it from its app store following EU sanctions on VK and its subsidiary.

AppWizard

July 30, 2026

Binance Android app removed from Google Play in Spain and Latvia over MiCA rules

Binance's Android app has been removed from Google Play in Spain and Latvia due to the lack of a Crypto-Asset Service Provider (CASP) authorization, which is required for crypto exchanges serving EU users. Binance withdrew its MiCA application in Greece before the July 1 deadline. The app is still available on Google Play in several other countries, including Poland, and can be downloaded from alternative Android stores.

AppWizard

July 24, 2026

EU hits Google with another $1B fine as Search and Play Store face fresh antitrust crackdown

The European Commission has fined Google €890 million under the Digital Markets Act, with €460 million for allegedly favoring its own services in search results and €430 million for restricting developers in the Google Play ecosystem. Google must revise its Search ranking algorithms and Play Store policies within 60 days to avoid further fines based on global revenue. The company is expected to appeal the decision and discuss compliance strategies with regulators.

AppWizard

July 23, 2026

Google Fined $1 Billion by EU Over Search, Android Practices

European Union regulators fined Google €890 million for unlawfully leveraging its dominance in search and Android to promote its own services. The European Commission found that Google violated the Digital Markets Act by prioritizing its offerings in search results and restricting Android app developers from directing users to alternative payment methods. Google has 60 days to comply with the ruling or face additional penalties of up to 5% of its global annual revenue. Since 2017, Google has faced fines exceeding €10 billion from EU regulators. The ruling reflects the EU's ongoing efforts to regulate Big Tech and ensure fair competition in digital markets.

AppWizard

July 23, 2026

EU hits Google with $1 billion fine over its Play app store and search

The European Union imposed a fine of 890 million euros on Google for violations of digital antitrust regulations, alleging that Google manipulated its Play platform and search engine to favor its own services over competitors. This action is part of the EU's broader efforts to regulate major technology firms and protect consumer interests. Google has faced previous legal challenges, including an unsuccessful appeal of a 4.3 billion euro antitrust fine related to its Android operating system. The EU has identified major tech companies as "gatekeepers" that must ensure fair competition. Google's President of Global Affairs criticized the fine, claiming it would harm European businesses and consumers.

AppWizard

July 22, 2026

Messenger Interoperability: Well-Intended, but Bad for Data Privacy

WhatsApp began supporting third-party messaging services in late 2025 in compliance with the EU's Digital Markets Act (DMA), which requires major tech companies to enable interoperability with alternative chat platforms. Threema has chosen not to implement interoperability with WhatsApp, citing concerns over user privacy and security, as differences in user identification methods could lead to compromises that weaken privacy protections. Threema believes that interoperability could reinforce WhatsApp's market dominance, reducing the incentive for users to adopt the Threema app. Additionally, Threema's business model relies on app sales for revenue, and a drop in downloads due to interoperability could threaten this model. Consequently, Threema has decided against pursuing interoperability with WhatsApp to maintain its commitment to privacy and security.

AppWizard

July 17, 2026

E.U. Orders Google to Open Android Mic, Camera and Screen to Rival AI Assistants

The European Commission has mandated that Google must provide equal access to rival AI assistants within its Android ecosystem, allowing them to use the same functionalities as Google's Gemini assistant. This includes access to the camera, microphone, and on-screen content, as well as background operation capabilities. Google is required to implement these changes in the upcoming Android 18 release by August 1, 2027. The directive includes two binding specifications under the Digital Markets Act, one of which requires Google to share anonymized search query, click, and ranking data with competing search engines and AI chatbots for a fee. The Android decision involves 11 operating system features, with five classified as restricted, requiring certification for third-party applications. These restricted features include access to on-device data shared by apps, context-aware intelligence, structured on-device integration, screen automation, and system integration. The remaining six features do not require certification, allowing broader access to ambient data, always-on hotword detection, long-press invocation, system-level on-device models, third-party model implementation, and background execution capabilities. Google must establish a Qualified AI Assistant Programme to facilitate access to gated features, allowing third-party Trusted Certification Authorities to certify assistants at no cost. The certification process must be fair and non-discriminatory, and users can consent to bypass the certification requirement for specific services and devices. By August 2027, both certified and user-approved uncertified assistants will be able to interact with applications on a virtual display. Google is also required to anonymize search data before sharing, ensuring user privacy and limiting data access to recipients who meet specific criteria. Kent Walker, Google's president of global affairs, expressed concerns about the security implications of granting external apps access to sensitive device permissions and criticized the anonymization methods for search data. The final measures reflect significant changes from earlier drafts, introducing more stringent requirements regarding data sharing and certification processes.