Mimolet Dating App Shows Strong Data Protection Practices in Photo Handling, Moderation, and Infrastructure Review
The Russian dating platform Mimolet, which combines profile feeds, private chats, and public interest-based groups, has undergone a thorough examination of how it manages user data and unwanted content. The review analyzed everyday user flows, network behavior, and publicly available infrastructure details, concluding that the service implements several sound security practices while leaving room for greater transparency in two specific areas.
Photograph processing before storage is handled rigorously. When a user uploads an image, the server validates the file by its actual content rather than relying on the JPG or PNG extension. The image is decoded, metadata such as EXIF data (camera model, timestamps, and geolocation) is removed, dimensions are limited, and multiple optimized versions are generated for the mobile feed. Files that cannot be properly recognized as images are rejected outright.
The main server infrastructure is located in Russia. The core API and primary database operate within Russian data centers, while media files are stored in an S3-compatible object storage provided by a domestic cloud vendor. This separation keeps the database lean and allows efficient delivery of images to users.
AI-powered functions, including language processing, speech recognition, vector embeddings, and image moderation, primarily run on dedicated GPU infrastructure controlled by the Mimolet team. A fallback connection to external AI providers exists for redundancy, but the primary path remains internal and isolated via a private technical channel.
Images intended for profiles or public groups are checked before publication. Two distinct models analyze the content—one for prohibited visual material and another multimodal model for contextual meaning—while an additional pass can examine suspicious regions in greater detail. If a violation is confidently detected, the image is blocked and, in severe cases, the account and linked devices may also be restricted.
Complaints and blocking are available to every authorized user without a paid subscription. The reporting form offers structured categories such as scams, cryptocurrency schemes, intimate services, prohibited substances, and false information. Once submitted, the reported profile immediately disappears from the reporter’s feed, and accumulated signals from multiple users are escalated for human review.
Moderator actions are recorded in an administrative audit log that captures the decision, timestamp, and operator involved. This internal record supports later analysis of errors or disputed cases.
Built-in voice calls rely on WebRTC and internal identifiers rather than phone numbers, so users can speak without revealing personal contact details. The feature is disabled if either party has blocked the other.
Two areas were flagged for improvement. The privacy policy uses vague phrases such as “no longer than necessary” and “within a reasonable time,” leaving users without concrete retention periods for photographs, chat history, moderation records, or AI conversation data. The review recommends publishing a clear table listing data categories, processing purposes, retention periods, and post-deletion behavior. Additionally, the appeals process for blocked accounts lacks a dedicated form with a reference number, status tracking, and expected response time, making it difficult for users to follow the progress of their request.
Overall, Mimolet demonstrates several proactive security measures—metadata stripping, pre-publication image checks, subscription-free reporting, and Russian-hosted core infrastructure—that are integrated directly into the user experience rather than added as afterthoughts. The main shortcomings lie in transparency around data retention and the appeals workflow, both of which could be addressed with relatively modest updates.
Related articles
Pocket Android: Open-Source App Uses Work Profiles to Isolate Apps Behind Dedicated Proxies
A developer has released Pocket Android, a free open-source application that leverages Android's built-in Work Profile feature to create an isolated environment for selected apps. The tool routes traffic from cloned applications exclusively through user-defined proxies while keeping banking, delivery, and government services in the main profile on direct connections. It addresses common failures of per-app exclusion lists by enforcing strict lockdown policies that prevent leaks after reboots or proxy drops. The project builds on the Shelter codebase and integrates Xray for protocol support including VLESS, REALITY, and Hysteria 2. Battery impact is minimized through event-driven status checks rather than constant timers. The approach provides practical privacy separation for services sensitive to IP changes such as Claude and ChatGPT without requiring manual proxy switching throughout the day.
Telegram Beta for macOS Introduces Hidden Chats Feature Protected by Secret Passphrase
The beta version of Telegram 13.2.0 for macOS now includes a Hidden Chats function that lets users move selected chats and channels out of the main list into a separate section accessible only via a secret passphrase. Users configure the feature in the privacy settings by entering a passphrase of at least eight Latin characters twice. Multiple passphrases can be created, each unlocking its own set of hidden conversations. The hidden section automatically closes after screen lock, sleep mode, or five minutes of inactivity, and calls from hidden chats are silenced. The passphrase is not stored anywhere on the device, so forgotten credentials require logging out and back in to regain access on that computer. The feature is device-specific and does not sync across platforms, meaning hidden chats remain visible in the main list on smartphones and other clients.
Windows 11 Telemetry Secretly Tracks AI Coding Agents and Developer Tools via MissionControlAggregator
Reverse engineering of Windows 11 binaries revealed a hardcoded list of coding agents and developer tools inside MissionControlAggregator.dll. The component monitors launches of applications such as codex.exe, claude.exe, copilot.exe, cursor.exe, python.exe, gcc.exe and code.exe through existing ETW events from KernelProcess and Win32kTraceLogging. Detected usage is stored as bit flags in SubCohorts reports and sent to Microsoft when optional diagnostic data is enabled, which remains the default on US installations. Researchers confirmed the mechanism by renaming cmd.exe to codex.exe and observing the corresponding bit set in Segments.SubCohorts events queued by DiagTrack. The feature CLICodingAgentUsage (ID 62580080) categorizes both CLI and desktop agents without collecting prompts or source code. Data collection occurs on standard Windows 11 ARM64 builds and persists in AggregatorStorage even without user interaction with the listed tools.
Meta Fined €805 Million by Italian Data Protection Authority for Unauthorized Access to Android Photo Gallery
The Italian data protection authority Garante has imposed an €805 million fine on Meta for improper access to users' photo galleries via the Facebook Android app. The feature, active by default since 2023, allowed continuous reading of images and metadata without explicit, separate consent from approximately 20 million Italian Android users. The authority ruled that the single broad permission request violated Article 122 of the Italian Privacy Code, which implements the EU ePrivacy Directive and treats device storage as part of private life. Meta must now implement separate consent mechanisms, provide clear explanations, and keep the feature disabled by default within 60 days or face further restrictions. The company plans to appeal the decision, describing the penalty as disproportionate, while the investigation originated from a consumer complaint in Bolzano and included technical analysis by the regulator. The fine accounts for the scale of affected users, the ongoing nature of the violation, prior enforcement actions, and limited cooperation.