Journal functional cookie
When Journal likes are active, opening the article list or an article automatically requests public like counts. A GET request does not create or renew a cookie or visitor identifier. It uses a keyed hash of the network address for read rate limiting. Write rate limits use keyed hashes of both the network address and the pseudonymous visitor identifier. The V14 tables store these hashes, not the plain network address or cookie value; direct table access is denied to anonymous and authenticated roles, and only the backend service can call the database functions. Entries are deleted when their last update is older than 24 hours and a later API call runs; there is no scheduled cleanup job, so they may remain longer if no later request arrives. If a valid cookie already exists, GET only reads it to show whether this browser has liked the article.
The bums_journal_visitor cookie is created only after the server accepts an explicit like request, if the browser does not already have a valid cookie. It contains a random identifier and signature, not a name, email address, or BUMS account credential. It is marked Secure, HttpOnly, and SameSite=Lax, has no declared Domain attribute and is host-only. New cookies have a maximum lifetime of 90 days, also enforced by the server; the browser may delete one earlier. Cookies issued before this update remain compatible, provided the signing secret is unchanged, so existing likes can still be removed. Their original browser expiry may be up to 365 days, and the legacy format does not let the server verify its issue date. The server uses a keyed hash of the pseudonymous identifier to associate likes with later unlikes and to rate-limit writes; that hash is not used for analytics, profiling, advertising, or services outside the Journal. V14 tables do not store page-by-page reading history. The cookie is not used for analytics, profiling, advertising, or cross-site tracking. Hosting providers may process technical request metadata under their own notices.
This functional purpose alone does not determine whether the cookie legally qualifies as strictly necessary or whether consent is required. The controller must assess whether it is strictly necessary for the information-society service explicitly requested and confirm the classification before public activation.
You can delete the cookie through browser settings. Deleting or expiring it does not automatically delete a like record; without the cookie the site may no longer identify or remove that browser's like. An unlike request without a cookie does not create a new one.
Hosting and analytics
The site may also use technologies strictly necessary to operate or secure its hosting infrastructure. This policy does not declare analytics or advertising tools active. If non-essential tracking tools are introduced, the policy and any required controls will be updated before activation.
More information
For details about the data and retention associated with Journal likes, see the Journal likes privacy notice. For questions, contact i@bumsapp.com.