Why there is no banner
The banners are a consequence of the cookies, not a requirement in themselves. What the law asks consent for is storage that is not necessary to provide what you asked for — measurement, profiling, advertising, anything that follows you between sites. Storage that is strictly necessary for a service you requested, such as keeping you signed in and protecting the form you are submitting, does not need it. This site has the second kind and none of the first, so there is nothing to ask you about and nothing to dismiss.
The two cookies
| Name | Set when | Lasts | What it does |
|---|---|---|---|
mopai_sid | You sign in or register | 30 days, or until you sign out | A random identifier for your session. It carries no information about you: the server matches it to a session record and that record names the account. Signing out deletes both the record and the cookie. |
mopai_csrf | You load a form while signed out — sign in, register | 24 hours | A random token, also placed in the form itself. The two are compared when you submit, which is what stops another site from making your browser submit a form here on your behalf. Signed-in members do not get this cookie: their token comes from the session record instead. |
Both are set with HttpOnly, so no script running on the page can read them; with SameSite=Lax, so they are not sent along with requests started by other sites; and with Secure whenever the connection is HTTPS, so they never travel in clear text. Neither is shared with anyone, and neither survives its expiry.
What is not here
- No analytics or measurement cookies, and no analytics service — the site does not know which pages you read.
- No advertising, retargeting or audience cookies.
- No social network buttons that load a script. The share links at the foot of a page are ordinary links: nothing is sent anywhere until you click one.
- No fingerprinting, and nothing kept in local storage or session storage — the site uses neither.
- No cookie behind the reader count in the footer. That works from a salted hash held in memory for fifteen minutes and written nowhere; see Privacy.
Content from elsewhere
Video embeds. Pages carrying footage — The Footage and the articles that discuss it — embed YouTube through youtube-nocookie.com, the form of the player that holds off on storage until the video is actually played. Every embed sits beside a plain link to the watch page, so blocking third-party frames costs you the inline player and nothing else. Once you press play you are dealing with YouTube, under Google's terms rather than this site's.
What members post. Posts in the community section may link images from other sites, or embed a YouTube or Vimeo video. Your browser fetches those from wherever they live when the post renders, so the third-party requests on a board page depend on what somebody else posted in it. Members' own uploads are served from this site.
Outbound links. Links to booksellers and to other archives are plain links. Nothing loads until you follow one, and then you are on their site under their policy. Bookseller links carry a parameter identifying this archive as the referrer, so the destination can see the visit came from here; nothing travels in the other direction.
Advertising. None is served. The reading list has places in its layout where an advertiser's own code could be dropped in, and they are empty — nothing is requested and nothing is set. If that ever changes, this page changes first.
Turning them off
Every browser can block or clear cookies, for all sites or for this one, in its privacy settings. Blocking them here does not affect reading: every page of the archive works exactly the same with cookies refused. What stops working is the community section, since staying signed in is the session cookie, and a form submitted without its token is rejected on purpose. Clearing the cookies signs you out, and the leftover session record on the server lapses on its own.
Last updated: 11 August 2026. See also Privacy. Questions and corrections: info@mopaiarchive.com.