Mimolet Dating App Review Highlights Privacy Protections, AI Moderation, and UX Trade-Offs in Detailed Analysis
Mimolet presents itself as a standard dating application featuring a vertical feed of user profiles. However, a closer examination after registration reveals a broader set of functionalities that extend well beyond simple swiping, including detailed profiles, full-featured chats, public groups, integrated voice and video calls, AI tools, and a dedicated moderation system.
Registration, Profiles, and Vertical Feed
Registration in Mimolet requires more steps than many competing dating apps. In addition to name, city, photos, and dating goals, users must specify height and select between three and eight interests from a list of approximately ninety options covering games, music, films, fashion, and walks. Optional fields include favorite artists, attitudes toward smoking and alcohol, subculture affiliation, and willingness to meet in person, which helps set clear expectations from the start.
The vertical feed displays profiles in a scrolling format similar to short videos, with each card occupying most of the screen. Key information such as city, height, dating goals, and interests appears directly beneath the main photo, eliminating the need to open a separate profile view before deciding to engage.
Filters, Appearance-Based Search, and Communication Tools
Most filters, including those for city, height, interests, dating goals, and subculture, remain available without a subscription. A weight filter exists but stands out as potentially unnecessary and intrusive. An appearance-based search feature allows users to upload a reference photo and receive up to ten matching profiles with similarity percentages, though the app could better clarify what happens to the uploaded image after the search completes.
Chats function like a full messenger with replies, reactions, editing, deletion by either party, voice messages, video circles, stickers, archiving, and pinned conversations. Three AI tools assist with message suggestions, grammar correction, and voice-to-text transcription with punctuation. Built-in calls use WebRTC and temporary identifiers so users can speak without exchanging phone numbers.
Groups, Events, and Social Features
Public groups organized by cities, interests, and subcultures enable conversations to begin around shared topics rather than requiring an initial match. Users are automatically added to relevant groups during profile setup but can leave permanently. Events listing allows users to mark attendance and join associated chats, while a voice roulette connects random participants and a connections feature displays confirmed friends and partners with mutual consent required.
AI Characters, Moderation, and Data Handling
Several AI characters, clearly marked with an AI badge, provide app support, conversational practice, or tarot readings. Complaints and blocking remain free, with photos reviewed by AI models before publication. Images are processed on the server to determine true format, resized, and stripped of EXIF metadata containing device details, timestamps, and location data. The main application, API, and database reside in a Russian server environment, while media files are stored in a Russian S3-compatible cloud.
Privacy Questions and Monetization
Two notable privacy gaps remain: the privacy policy lacks specific retention periods for photos, backups, moderation materials, and AI conversation history, and blocked users have no dedicated appeals form with case numbers or status tracking. Three subscription tiers—Plus, Premium, and Ultra—increase reaction limits, boost visibility, and unlock additional AI capabilities while core features stay free. Monetization also includes blurred incoming likes that require payment to view and an optional ten-point photo rating system.
According to the development team, the service has around 200,000 registrations and roughly 15,000 daily active users, with retention rates of 44.96% on day three, 34.69% on day seven, and 19.11% on day thirty.
Related articles
Chrome Adds On-Device Gemini Nano While Ask Gemini Sends Page Content to Google Cloud
Google has introduced an 'AI on device' toggle in Chrome settings that enables local execution of the Gemini Nano model directly on the user's computer. Several gigabytes of Gemini Nano weights are now stored in the browser profile directory and can run on CPU or GPU for tasks such as initial analysis of suspicious pages. Despite the local model being present, the user-facing 'Ask Gemini' feature does not use it and instead routes page content, URLs, and up to ten additional tabs to Google's cloud infrastructure. The company uses two distinct systems under the Gemini name: the cloud-based Ask Gemini / Gemini in Chrome service and the on-device Gemini Nano accessed only through internal APIs or by websites and extensions. When Enhanced Protection is enabled, results from the local Safe Browsing analysis may still be transmitted to Google Safe Browsing servers. The naming and interface choices have created confusion, as users cannot directly invoke the downloaded Gemini Nano model for tasks like summarizing open pages.
Yandex Details Alice Voice Assistant Audio Buffering and Data Handling in Android Apps
Yandex has issued a detailed technical response to an analysis of its Android applications that raised concerns over potential collection of audio, contacts, bank card data, and other sensitive information. The company acknowledged the existence of a cyclic audio buffer that retains approximately 1.5 seconds of sound before an activation phrase and 0.5 seconds after it, with some pre-command audio possibly transmitted to servers for speech recognition quality checks. Yandex clarified that the Alice assistant only listens locally for the wake word when the app is open and does not continuously record conversations. Access to contacts was explained as necessary for voice commands such as calling entries from the address book, with the full book sent on first sync and only changes thereafter, without hashing to support accurate speech processing. The firm rejected claims of reading messaging app conversations and stated that bank card details are routed directly to an isolated PCI DSS-compliant environment rather than standard application servers.
One Request, Five Observers: What Websites, Providers, DNS and VPNs Learn When Loading a Page
The article breaks down exactly what each participant in a typical web request can observe when a user visits a page over HTTPS. It examines the roles of the browser, DNS resolver, ISP, VPN service and the destination site itself, showing that each sees different pieces of metadata or content. HTTPS protects the page body and parameters from network observers, while Encrypted Client Hello and secure DNS further limit visibility of domain names. VPNs replace the user's home IP address with the VPN exit node but introduce a new trusted party that sees all traffic metadata. Browser fingerprinting, cookies and account logins often allow sites to re-identify users even after an IP change. The piece stresses that privacy tools must be chosen according to the specific threat model rather than relying on any single mechanism.
Windscribe Releases Open-Source PowerShell Script to Remove Microsoft's Persistent Global Device Identifier from Windows
Windscribe has published an open-source PowerShell script called deGDID that removes Microsoft's Global Device Identifier (GDID) from Windows systems and prevents the creation of new identifiers. The persistent tracker survives IP address changes and operates below the VPN layer, allowing Microsoft to maintain device tracking even when users employ privacy tools. The script was developed after the FBI used GDID to identify a suspected hacker, raising concerns about undisclosed device fingerprinting. deGDID modifies registry access control lists and blocks the DeviceAdd interface to stop Windows from regenerating the identifiers after reboots or server contacts. While effective at disabling the tracking mechanism, the tool can break authentication to login.live.com and disrupt certain Microsoft cloud services. It is intended only for unmanaged consumer devices and will not run on domain-joined or corporate-managed systems. The project is described as experimental and cannot delete identifiers already transmitted to Microsoft servers.