The short version
We collect first-party visit statistics and technical request data to understand catalogue use, identify automated traffic and protect the site from abuse. These diagnostic records are not linked to your account. If you sign in with Telegram we also keep the fields Telegram hands us, your favourites and your reviews.
We run no third-party analytics counters or tracking ads, and we do not sell data.
What we keep when you sign in
Telegram hands us a set of fields at sign-in and we keep exactly those: the numeric Telegram ID, first and last name, username, a link to the avatar, interface language, whether the account is Telegram Premium, and the time of the last sign-in.
Attached to the account is what you do here: favourites, reviews and app submissions. Older ownership requests remain in the request history.
What we never hold
We hold no password: signing in goes through Telegram, and your Telegram password never reaches us.
We hold no phone number, no private messages, no contacts and no payment details. Placement is paid outside the site, in direct messages, and we take no card data. Traffic diagnostics do not store authentication tokens, session cookies, form contents or request bodies. We do not use GPS, canvas fingerprinting or other active fingerprinting techniques.
Clicks and logs
When you open an app through a link on the site we record the app, the link kind, the date and time, the page's language, the country, the referring domain, whether the request looks automated, and salted hashes of the IP address and browser string. Click records are not linked to your account.
Separately, public request diagnostics keep the IP address and full User-Agent browser string, a first-party visitor identifier when available, the path without query parameters, request method, response status and processing time. We also keep selected technical HTTP headers and connection information, including Cloudflare request identifiers, bot signals, passive TLS connection fingerprints and approximate country, city or network information when supplied. Referrers and origins are reduced to their domain. Private account, console and sign-in requests are excluded from these diagnostics.
Analytics
The site carries no Google Analytics, no Yandex Metrica and no other third-party counter. We count visits, app-page views and outgoing clicks on our own server. Public request diagnostics also cover catalogue pages, assets, robots.txt, sitemaps and public API requests.
When JavaScript runs, a visit can include ordinary browser properties: language preferences, platform, time zone, the automation indicator, cookie support, reported processor cores and device memory, touch support, screen and viewport dimensions, colour depth, pixel ratio, colour scheme, page visibility, navigation type and referring domain. These values help distinguish browser visits from automated requests; they are not linked to an account.
Who else sees this
We do not sell data and do not hand it to ad networks.
Data is processed on our own server, at our hosting provider and by Cloudflare, which handles requests before they reach our server. Telegram handles sign-in. We may disclose data on a lawful request from a public authority.
How long we keep it
Account data lives as long as the account does. Detailed traffic diagnostics, including IP addresses, User-Agent strings and browser properties, are removed from the working database by the daily cleanup once they are older than 30 days. Raw click records with salted hashes are removed after 90 days. Older catalogue statistics are kept as aggregates.
The visitor cookie lasts for up to one year. Daily visitor and app-page counts are stored separately from account data. Deleted records may remain in encrypted backups until those copies are removed by the scheduled backup rotation.
Your rights
You can ask for a copy of your data, for a correction, or for your account to be deleted along with your favourites and reviews. Write to us and we will do it within 30 days of receiving your message.
App pages stay: they are assembled from public data and are not your personal data.
Children
The site is not meant for children under 13 and we do not knowingly collect their data. If you believe a child has left data with us, write and we will remove it.
Changes
We may change this policy. The date of the last change is at the top of this page, and material changes are flagged on the site.
Getting in touch
[email protected]. Write in any of the site's languages.