Privacy policy
Last updated
This page describes what this site stores, where it lives, how long it stays and why. It is written from the code, not around it: the retention periods below are the numbers our scheduled cleanup jobs enforce.
Who runs this site
Hornygram is the operator of this catalogue and, for the purposes of data protection law, the controller of the personal data described on this page. Any question, complaint, copyright notice or data request goes to support@hornygram.com, which is a real mailbox read by a person. The site itself sends no email.
This policy covers this website only. Telegram, and the bots and channels we link to, are run by others under their own privacy policies; what you do there is outside this policy and outside our control.
There are no visitor accounts
You cannot register here, and nothing on the site asks for your name, email address or phone number. Voting, saving favourites and confirming your age all work without an account, which is why none exists.
The single exception is the submission form: if you offer a bot or a channel for listing, you type in a Telegram username so we can reply, and that is stored with the submission. When we write to you there, the conversation goes through Telegram under its own policy.
What stays on your device
| What | Where | Why | How long |
|---|---|---|---|
| Age confirmation | localStorage | so the 18+ notice is shown once | until you clear your browser |
| Favourites | localStorage | the list of listings you saved | until you clear your browser |
| Favourites counted | localStorage | so the favourites you already had are counted once, not on every visit | until you clear your browser |
| Recent searches | localStorage | your last 5 searches, to offer them again in the search box; the list stays in your browser and you can remove it there | until you clear them or your browser |
| Viewed listings | localStorage | the last 500 listings you opened and when, to mark them as viewed and to list them under Recently opened on the Favorites page; you can remove one or all of them there | until you clear them or your browser |
| Vote prompt | localStorage | so "Did you like it?" is asked once per listing and not too often: the last 500 listings it asked about, how many times this session and whether you asked not to be asked again | until you clear your browser |
| Listings already counted today | localStorage | which listings and in which section of the site were already counted as shown today, so the same listing is not counted again; it is not sent to us | until the next day |
| Listing opened from a Sponsored card | localStorage | the listing number, the section and the time, so opening that listing and going to Telegram from its page are counted for the Sponsored placement; only the section is sent to us, not this record | 30 minutes |
| Header layout | localStorage | which of the two versions of the site header your browser was given, so it stays the same between visits | until you clear your browser |
| Listing just opened | sessionStorage | its number, name and logo, to ask about it when you come back from Telegram | until you come back or close the tab |
| voter_id | signed httpOnly cookie | one vote per browser | 12 months |
| Cookie choice | localStorage | remembers your analytics choice | 12 months |
| Unfinished submission form | localStorage | so a reload does not lose what you typed | until sent or cleared |
| draft_token | signed httpOnly cookie | finds your unfinished submission on the server | 30 days |
| Activity mark | sessionStorage | that this tab has seen a tap, scroll, mouse movement or key press, so the check is not repeated on every page | until you close the tab |
| Loaded list | sessionStorage | the public cards you loaded with Show more and how far you scrolled, so the Back button returns you to the same place | until you close the tab; ignored after an hour |
| Country check | sessionStorage | whether to show the cookie bar | until you close the tab |
| Analytics cookies | cookie | in the EEA, the UK and Switzerland only if you accept them; elsewhere until you turn them off | per the analytics provider |
Your list of favourites stays in your browser: we keep no copy of the list. When you save or remove a listing, the site counts it — that listing gets one more save, or one fewer, in an hourly total — without recording who you are. Once, on your first visit after this count appeared, the listings already in your favourites are counted the same way. Each save or removal also reaches our anonymous statistics as a separate event; see Analytics below.
Your list of opened listings stays in your browser too: we keep no copy of the list. Opening a listing page or following a listing to Telegram is still a request to our site, and our anonymous statistics count it; see Analytics below. To draw the cards on the Favorites page, your browser asks our server for them by listing number. The answer is not cached, and nothing about that request is kept apart from the web server logs described below.
What is stored on our servers
| What | Data | Why | How long |
|---|---|---|---|
| A vote | listing id, voter_id, salted hash of your IP, hash of your browser string | one vote per browser, no second vote for the same listing from the same IP and browser string within 24 hours, and the order of the catalogue | kept — votes are the ordering of the catalogue |
| A click on an outgoing link | listing id, time, salted hashes, referring page on this site and the section of it, type of device (phone, tablet or computer), country | traffic statistics and abuse analysis | raw rows 30 days, then daily totals only |
| A listing shown on screen | listing, day, section of the site and type of device (phone, tablet or computer), as numbers added to daily totals; the same for opening its screenshots and its page; not who saw it and not your browser string | to see which listings people see and which of them they open | daily totals are kept |
| Repeat-count limit for listings shown | salted hashes of your IP and of your IP with your browser string, held in memory | so that a script cannot inflate how often a listing was shown | 2 days |
| A view of a blog article | article and day, as a number added to a daily total | the view count under articles | daily totals are kept |
| Repeat-view limit | salted hashes of your IP and of your IP with your browser string, held in memory | so that reloading an article counts at most 3 times a day | 2 days |
| A saved favourite | listing and hour, as a number added to an hourly total | how many people keep a listing in favourites | hourly totals are kept |
| Repeat-save limit | salted hashes of your IP and of your IP with your browser string, with the last thing you did on that listing, held in memory | so that pressing Save twice counts once | 2 days |
| A search | the search text in lower case, the day, how many times it was searched or picked from the suggestions, how many listings it found and how many of those searches were followed by opening a listing from the results; not which listing | to see what people look for and what the catalogue is missing, and to suggest common searches in the search box | 90 days |
| Repeat-search limit | salted hashes of your IP and its network, of your IP with your browser string, and of your IP with the search text, held in memory | so that reloading a results page counts once a day, a search that led to a listing counts once, and repeated taps on Top picks are capped | 2 days |
| A tap on Top picks | the day, as a number added to a daily total; not which listing and not who tapped | to see whether the listings suggested in the search box are used | 90 days |
| Anti-abuse checks | results of checking visits and votes against fake votes and automated traffic | to keep the order of the catalogue honest; a person makes every decision | links to a particular visit or vote 30 days, anonymous results are kept |
| A visit path | a summary of one finished visit in the anonymous statistics below: the types of pages in the order they were opened (such as the home page, a category or a listing page), which listing, category or article each was, whether a page was opened by a link, the back button or a reload, and through which marked link or menu item, seconds from the start of the visit; which listings were opened in Telegram and from which part of the page, how long the visitor stayed in Telegram before coming back; votes, saves and taps on the invitation to our Telegram channel; whether a search found nothing, one to five, or six or more listings (never the search text); whether the submission form moved on to the choice of plan; whether the age confirmation was shown, accepted or declined; where the visit came from (such as a search engine, another website or our Telegram channel), type of device, country and browser language. No session identifier, IP address or its hash, browser string, page address, search text or vote record, and nothing that names a person | to see how people move through the site and where they leave it | 400 days |
| A report | reason, comment, salted hash of your IP | moderation | 12 months |
| A submission | what you typed in the form, payment data, refund address, salted hashes | publishing the listing, replying to you and refunding you | as long as payment records require |
| An unfinished submission | the fields you filled in, salted hash of your IP | restoring the form and contacting you about it | 30 days after the last change |
| A return from payment | the submission number and the time you first came back from the payment page to your status page; nothing about you or your browser | to see whether people who pay make it back to the site | as long as the submission is kept |
| Web server logs | IP address, browser string, requested address | diagnostics and security | 14 days |
Search queries are stored anonymously: only the text of the search, the day and four totals, with no IP address, no hash of it, no browser string and nothing else that links a search to you. Text that looks like an email address, a phone or card number, or a link with parameters is not stored at all. A search can appear as a suggestion in the search box only as a short phrase in English letters that many searches repeated on different days and that finds listings in the catalogue; nothing shows who searched for it. All other searches are not published anywhere on the site, and all of them are deleted after 90 days. Like any other page, a results page also passes through the web server logs listed above, with its address and for their own period.
Beyond these periods, a record may be kept longer only where the law requires it or where it is needed for a specific complaint, dispute or investigation of abuse that is already under way, and only for as long as that lasts.
Why we are allowed to use it
| Purpose | Legal basis |
|---|---|
| Showing the catalogue, counting votes, favourites, views and clicks, preventing fake votes and automated traffic, web server logs and security | our legitimate interest in running a fair, working and safe catalogue; the data is minimised and hashed so that it does not identify you |
| Things stored only in your browser to make the site work (age confirmation, vote and favourites lists, cookie choice, the voter_id cookie) | strictly necessary for the service you ask for |
| Third-party analytics cookies | your consent in the EEA, the UK and Switzerland; elsewhere our legitimate interest, and you can opt out at any time |
| Handling a submission, a payment and a refund | performing the agreement you enter into when you submit, and the steps before it |
| Keeping payment and refund records | legal obligations, and our legitimate interest in being able to settle disputes |
| Reports, takedown notices and requests from authorities | legal obligations, and our legitimate interest in keeping unlawful material off the site |
Where we rely on legitimate interest, you can object, and we will stop unless we have a compelling reason, such as preventing abuse, that outweighs your interest.
IP addresses
No application record stores your IP address in readable form. Votes, clicks, reports and submissions store a salted hash: the address itself is not kept, the salt is kept secret, and we use the hash only to match it against itself — to refuse a second vote for the same listing from the same address and browser, and for abuse analysis.
There is exactly one exception, and it is better named than promised away: web server logs contain IP addresses in the clear, because every web server works that way and because an incident cannot be investigated without them. Those logs are deleted after 14 days. Saying "we never see your IP" would be untrue — your hosting provider, our network provider and these logs all see it.
Who else receives data
| Who | What they see | Why it is unavoidable |
|---|---|---|
| Our hosting provider | everything stored on the server | the site has to run somewhere |
| Our network and firewall provider | IP addresses and request headers for pages, anti-bot challenge data | filtering abuse and protecting voting |
| Our payment provider | the payment details of a submitter | accepting payment for a listing |
| Our media host | IP address when an image loads | serving images |
| Our error monitoring service | technical reports about errors on our server, which can include the address of the page that failed | finding and fixing faults |
| Analytics | see the next section | measuring traffic |
| Courts, police and other authorities | only what a valid legal request we receive covers | when the law requires us to answer it |
Nothing is sold, and nothing is shared for cross-context behavioural advertising. If the site ever changes hands, the data described here would pass to the new operator under this same policy.
Some of these providers process data outside your country, including in the United States. Where data protection law requires it, such transfers rely on the safeguards those providers offer, such as standard contractual clauses or an adequacy decision.
Analytics
The primary counter is self-hosted on this site: it sets no cookies and hands no data to a third party. It counts page views (with the list options in the address — page number, sort order, period, category and price filter — and utm campaign tags, but no other part of the address, and with whether the page was opened by a link, the browser’s back or forward button, or a reload), where visitors arrived from, which listings were on screen for at least a second and whether their screenshots were opened (as daily totals per listing, section of the site and type of device, without a session identifier), which listings they open in Telegram, from which part of the page (such as a category list, the listing page or Alternatives) and at which place in the list, and how soon they come back, that a search was made and whether it found nothing, one to five, or six or more listings (never the search text), that the submission form moved on to the choice of plan, which they save or vote for, how the "Did you like it?" prompt was answered, taps on the invitation to our Telegram channel, taps on the main menu and which version of the menu was on screen, taps on buttons and links in sections of the site (such as "See all", a category or a question in a review, recorded under a fixed name of the button and the page or part of the page it leads to, never anything you type), whether the age confirmation was accepted or declined and how long it was on screen, which choice was made in the cookie notice, and nothing that identifies a person. Opening, saving, voting and answers to the "Did you like it?" prompt are recorded with the name of the listing. These events and taps are grouped under an anonymous session identifier, so we can see what happened within a session, not who did it.
To tell people from automated visitors, the counter also learns whether a page saw a real action — a tap, scroll, mouse movement or key press — and a few summary numbers about it, such as how straight the mouse path was and how long it took. For a key press it learns only the kind of key — navigation, a character or a shortcut — never which one. It never receives the positions of your pointer, what you type or anything that identifies you.
To protect the order of the catalogue from fake votes and automated traffic, we also analyse these counter records together with the vote and click records above. No vote is removed automatically, and the link between the results and a particular visit or vote is deleted after 30 days.
Each finished visit is also summarised as a visit path: the types of pages in the order they were opened and which listing, category or article each was, how each page was reached (a link, the back button or a reload, and which marked link or menu item), seconds from the start, which listings were opened in Telegram and from which part of the page, how long the visitor stayed in Telegram, votes, saves and taps on the invitation to our channel, the found-nothing, one-to-five or six-or-more result of a search, whether the submission form reached the choice of plan, the answer to the age confirmation, where the visit came from, type of device, country and browser language. A visit path has no session identifier, IP address or its hash, browser string, page address, search text or vote record, and nothing that names a person; it is kept for 400 days.
Third-party analytics (Google Analytics), when enabled, sets cookies. If you visit from the European Union, the European Economic Area, the United Kingdom or Switzerland, it loads only after you accept analytics cookies in the cookie bar; decline and it never loads. Everywhere else it loads by default, and you can turn it off at any time.
To change your choice, use Cookie settings at the bottom of any page. Turning analytics off stops it immediately and removes its cookies; the site itself works exactly the same either way.
Your browser learns which country you are in from our network provider, based on your IP address, only to decide whether to ask. The answer stays in your browser for the current tab; this check sends nothing to us. With a VPN, the country is that of the VPN server.
Private submission status pages are excluded from analytics entirely, and they are sent with a policy that stops the address leaking to the next site you visit: the address contains your private token. When you come back to that page from the payment page, it tells our own server once that you returned (see "A return from payment" above); nothing about it goes to analytics.
No automated decisions about you
Nothing on this site makes a decision about you by automated means alone. Anti-abuse checks only flag visits and votes for a person to look at; a person decides whether a vote is removed, and whether a submission or listing is accepted, refused or taken down.
Security
Access to the server and the admin panel is limited to the people who run the site. Addresses are stored as salted hashes, cookies are signed and unreadable to scripts, and connections are encrypted. No system is perfectly secure, so we keep only what is listed here and for no longer than listed: the safest data is the data we do not have.
Adults only
This site is intended only for adults and is not directed at anyone under 18. We do not knowingly collect data from minors. If we learn that a submission or a message came from someone under 18, we delete it and do not deal with that person.
Your rights
Depending on where you live, you may have the right to ask what data we hold about you, to have it corrected or deleted, to restrict or object to its use, to receive a copy of it, and to withdraw consent you gave, without affecting what was done before. Write to support@hornygram.com; we answer within one month. To make sure we hand data only to the person it belongs to, we may ask you to show that a submission is yours, for example from the Telegram account named in it.
What can genuinely be deleted: a submission with your contact details and refund address, an unfinished submission, a report you sent. Payment records we are required to keep are kept for that period and then deleted.
A vote cannot be deleted on request, and we would rather say so than pretend otherwise: it is tied to a browser identifier, not to a person, so there is nothing to match your request against.
You can also complain to the data protection authority where you live or work. We would appreciate the chance to fix the problem first.
Changes
When this policy changes, the date at the top of the page changes with it. The date reflects the last change to the text, not the last time the page was rebuilt.