Privacy
Private by design. Clear about the rest.
This notice explains the information HornySearch handles, why it is used, which services receive it, and how to ask about or remove it.
Effective September 1, 2026
Contact and privacy requests
HornySearch handles the information described in this notice. Send privacy questions or requests to [email protected]. We may ask for enough information to identify the relevant browser history, public URL, or source material before acting on a request.
Searches and browser history
Visitors do not create accounts. When you use Search, HornySearch stores the search wording, processing state, selected results, and a one-way digest tied to a random browser token. The raw token stays in an encrypted, HTTP-only, same-site cookie for up to 14 days and is not stored in the application database. Clearing that cookie starts a separate search history.
An administrator may deliberately turn a useful completed search into a public discovery page. A published page can include the search wording, a generated summary, and selected results, but it does not publish the browser token or its digest. Contact us before searching if the wording itself would identify you or another person.
Age assurance
Most eligible consumer pages use a first-party confirmation that you are 18 or older and old enough to view adult material where you live. That choice is stored in a browser-readable cookie for 30 days. In locations where an approved stronger check applies, the page instead loads AgeVerif, an independent age-assurance service. HornySearch trust and legal pages use neither gate. The method offered can depend on your location and AgeVerif’s configuration. Information you provide to AgeVerif is handled under AgeVerif’s privacy policy; HornySearch uses the resulting verification status or token to control access.
Product analytics
On eligible public pages, HornySearch uses PostHog to understand whether the product works. Raw search wording, captions, performer and Kink names, titles, record IDs, email addresses, and media are excluded from application-supplied analytics. Inputs and page text are masked in session replay; images, video, audio, iframes, and canvases are blocked. Captured same-site URLs are stripped of query strings and dynamic identifiers.
Analytics use a pseudonymous digest rather than your raw browser token. Product events are retained for at most 12 months and session replays for at most 30 days, or less if the service plan applies a shorter limit. Learn more in PostHog’s privacy policy.
Service delivery and security
Like most internet services, HornySearch and its infrastructure providers can process request details such as IP address, user agent, requested path, time, and security signals to deliver the site, prevent abuse, and diagnose failures. The service runs on AWS and uses Cloudflare for parts of its public delivery and security boundary.
Following a link or opening an embedded player also connects you to the original video platform. That platform receives information under its own privacy terms and may set its own cookies.
Your controls and requests
You can clear site data in your browser to remove the local visitor token. You can also ask us to explain, correct, restrict, or delete information connected to a search or public page. Whether a request applies, and what we must retain for security or legal reasons, depends on the circumstances and applicable law.
For material involving consent, identity, safety, or intimate privacy, use the content-removal process. For a copyright claim, use the copyright/DMCA process.
Changes to this notice
We will update the effective date when this notice materially changes. Continued use after an update means the revised notice applies to later use; rights that cannot be waived under applicable law remain unaffected.