repdb.io

Policy

Privacy

The whole list, not a summary that leaves room for a vendor later. Last updated 2026-10-18.

The site collects one thing of its own: a first-party page-view beacon that records the path, the seconds a page stayed open, how far it was scrolled, and a random identifier kept in the reader's own browser. That identifier is hashed before storage and no IP address is written to the analytics table. There are no third-party scripts on any page, no advertising or analytics vendor, no tracking cookies, and nothing is sold or shared. An email address sent through a form is used to reply and is not published. Removal can be requested through the complaints page.

What is actually collected when I read a page?

A page view with the path, how long the page stayed open, how far it was scrolled, and a random identifier your browser keeps in its own localStorage. The identifier is hashed before it is stored, and no IP address is written to the analytics table. The site runs no third-party scripts, so no advertising or social widget receives anything.

Why is dwell time and scroll depth recorded at all?

To know which pages are read and which are skipped, and to be able to say so honestly instead of guessing. The counts published on the site are aggregates built from those rows; no individual reader is described anywhere.

Do you use cookies?

No tracking cookies. One random key is kept in localStorage under the name repdb.refsearch.rpid so that a return visit is not counted as a first visit. Clearing site data removes it, and the site keeps working the same way without it.

Is anything sold or shared?

No. There is no advertising network, no data broker, no analytics vendor and nothing to sell. Server-level logs exist at the hosting provider for security and abuse handling, on that provider terms, and are not exported.

Is my email address published?

No. An address sent through the submissions or complaints form is used to reply and to keep the correspondence together, and it is not shown on any page. If a complaint becomes a published dispute, the complainant is described by role, not by identity, unless they ask otherwise.

How long is any of it kept?

Page-view rows are kept while they are useful as an aggregate. Correspondence is kept while a dispute or a submission is open, and for as long as the published record of it exists. There is no long-term profile of a reader to keep, because no reader is identified beyond a random key in their own browser.

How do I get data about me removed?

Ask through the complaints page. A visitor identifier can be erased on request if it can be identified; correspondence is kept while a dispute is open and for as long as the record of it exists, then removed. Nothing published about a business is removed on request alone, which is a separate rule set out on the corrections page.

What about the hosting provider?

Pages are served by a third-party edge network, which keeps its own request logs for security and abuse handling under its terms. Those logs are not exported into this site's analytics table and are not combined with the beacon.

Children and other jurisdictions

The site is written for adults dealing with a trade in replica goods and is not directed at children. It makes no claim to have solved every jurisdiction's formalities; the honest position is that the list above is what the site does, and it applies to every reader the same way.

Related pages: Terms of use · Complaints and corrections · About · Authorship and tools