Data and privacy
2026-09-13
Publication status
This is a factual description of Mira’s current data handling, not a completed legal privacy policy. Hosting locations, legal grounds, regulatory notifications and international transfers are still being reviewed. The final policy will be published after that review.
Who operates Mira
Individual entrepreneur Sergey Andreevich Yazovskiy (ИП Язовский Сергей Андреевич), Russian Federation. Contact: yazovskiy@hotmail.com. Public name: Sergey Yazovskiy.
Your collection
As a guest, your collection and preferences stay in this browser’s local storage until you clear them. Older guest archives may also remain. After email sign-in, Mira stores your technical account ID, email, service dates, TMDB show and episode IDs, viewing progress, collection status and import results on its server. No name, avatar or public profile is requested.
Sign-in and protection
Sign-in links expire after 15 minutes and are consumed only when you confirm sign-in. Sessions expire after 30 days; the session cookie is HttpOnly. Token hashes are stored instead of the tokens. Keyed hashes of email and IP used for mail rate limiting expire after one hour. These hashes are pseudonymous, not anonymous. Expired records are cleaned every minute.
Suppliers and external requests
The VPS provider hosts the application, database and local backups. REG.RU handles outgoing sign-in email; your email provider receives it. TMDB receives catalogue search queries from Mira’s server. Posters are fetched through Mira, without passing your browser IP to TMDB. Search responses are cached in memory for up to five minutes; catalogue metadata is cached for up to a day. Cloudflare provides DNS, not application proxying in the current configuration. Privacy requests emailed to the contact above are processed in Microsoft’s Hotmail service. The operator confirmed that the VPS, database and local backups are in the Netherlands. SMTP placement and applicable localization and transfer arrangements are still under review.
Logs and statistics
Application access logs are disabled. Mira does not log emails, authentication tokens or message contents. Infrastructure providers can process technical data under their own terms. No advertising trackers or session recordings are installed. Optional browser telemetry is off by default and can be enabled or withdrawn in Your data. It sends only fixed event names, without cookies, visitor identifiers, titles or queries. Server statistics count requests, actual collection changes and accounts. A separate account activity record retains only the latest collection use, updated at most hourly and removed after 30 days. Technical minute aggregates are retained for seven days and daily totals for 400 days; aggregates contain no account IDs. The private dashboard is accessible only through SSH.
Export and deletion
Open Your data to export the guest collection or your account. Account export requires a sign-in within the last 15 minutes. Clearing browser data also removes archived Mira guest data and preferences, but does not delete the server account. Account deletion requires confirmation and a recent sign-in and revokes all sessions.
Backups and recovery
Daily SQLite backups are kept for up to seven days, at most seven copies, on the same disk as the service. They do not protect against disk loss. Deleted data can remain in backups until expiry. A separate journal retains only deleted technical account IDs for eight days so restoring a backup cannot reactivate deleted accounts. Restoration revokes all old sessions and sign-in links. Poster cache is capped at 256 MB and seven days.
Questions and requests
Email the operator to ask about access, correction or deletion of your data. We may need to verify that a request concerns your account. Do not send passwords or sign-in links. A request to this contact does not subscribe you to marketing.