ViralWorld

Privacy

This describes what ViralWorld (viralworld.app) actually does, which is very little. Everything below is a statement about how this site is built, not a policy describing what it intends to do one day.

There is no account, and nothing to sign in to

ViralWorld has no accounts, no registration, no login, and no profiles. It accepts no uploads and hosts no comment section — reading this site requires giving it nothing, and there is no way to give it anything.

This site sets no cookies

ViralWorld sets no cookies, and nothing here tracks you between visits or between sites.

The platforms do, once you allow their pictures. Asking Wikimedia or YouTube for an image is a request to them, and a request to them can come back with cookies of their own on their own domain — Wikimedia's, for instance, includes one that is unique to your browser. That is the consequence the picture question is asking you about, it happens on their domain rather than this one, and saying no means it never happens at all.

Your browser stores two things for this site, and each only once you have answered the question it belongs to. One is whether you want to see pictures and video from the platforms things were originally posted to. The other is whether you allow anonymous measurement. Both are a single yes or no, both stay on your device, neither is sent anywhere, and you can change either at any time — see below.

If you allow measurement, one more value exists while you are here: a random identifier for this browser tab, held in the tab's own storage. It is generated on your device, it is not derived from anything about you, it is discarded when the tab closes, and it is thrown away immediately if you change your mind. It is what lets us count a visit as one visit rather than as eight unrelated events, and it is not a profile.

What you searched for is not stored. A search is answered from the catalogue and the query is not retained, associated with anything, or written to any record.

Analytics

Only if you say yes. ViralWorld uses HEKNO Analytics, which is run by the same people who run this site rather than by an advertising company. Nothing is measured until you allow it, and saying yes to pictures does not say yes to this — they are separate questions with separate answers.

What is measured, when you allow it: which pages are opened, which Moments are watched, whether a player actually loaded or the platform refused it, whether you moved on to the next thing, what was shared, and whether a search found anything. Each event carries the public slug of the record and a few bounded labels — the format, the collection, the surface it came from.

What you searched for is never sent. Not to us and not to anyone. The measurement records that a search happened and roughly how many results it found; the words you typed cannot be represented in the format these events use, so there is no path by which they could travel even by mistake.

There are no accounts, no profiles, no advertising identifiers, no fingerprinting and no tracking between sites. Your IP address is not collected by the receiving service. You can turn measurement off at any time, below, and nothing further is sent.

Google Analytics is not in use on this site. It is intended as a second, parallel destination for the same consented events, sent from our server rather than by a tag in your browser, and it is not running: the credential it needs has not been configured. If that changes, this page changes with it.

Change your mind

Both answers are yours to change, and neither affects the other.

Embedded players, which are the exception

This is the one place where another company can receive data about you, so it is worth being exact.

Some Moments can be played inline. Nothing is loaded from the source platform when the page opens — the player is built only when you press play, and until you do, no request has been made to anyone but this site. Everything else links out rather than embedding, so visiting a page and following a link to the source are separate acts with different consequences.

The same applies to the pictures on cards and headers. Where a platform publishes a preview frame for something ViralWorld is allowed to embed, that picture is loaded from the platform rather than copied here — so it is the same disclosure as pressing play, and it is covered by the same single answer. Say no, and you see ViralWorld's own artwork instead and no platform is contacted at all.

When you do press play, the video is requested from the platform that hosts it, and from that moment your browser is talking to them directly. What they receive — your IP address, your user agent, whatever their own cookies and terms provide for — is governed by their privacy policy, not this one. YouTube embeds are requested from youtube-nocookie.com, the privacy-reduced host, which limits but does not eliminate this.

Changing your mind

Whatever you answered, you can change it here. Turning it off removes the stored preference and the page goes back to showing ViralWorld's own artwork.

What the server keeps

ViralWorld does not keep an access log of who read what. When a page fails to render, the failure is recorded so it can be fixed — the path and the error, not the reader.

Personal information in the archive itself

The harder privacy question here is not about visitors. Viral media frequently contains identifiable people, often people who never chose to be famous and sometimes people who were children when it happened.

That is treated as a live obligation rather than a disclaimer: records are reviewed before publication, and a private person, a location, or an identification that should not be here is something a person will act on. If that is you, or someone you know, report it — privacy reports are treated as urgent.