BUMS
JournalHome
BUMS JOURNAL

Privacy notice for Journal likes

Last updated: 29 October 2026
This notice supplements the full BUMS privacy policy, currently available in Italian at bumsapp.com/privacy/.

What the likes feature processes

When you open a Journal page while likes are enabled, the site requests the article's public like count. A GET request does not create or renew a cookie or visitor identifier. If a valid bums_journal_visitor cookie already exists, the API reads it only to show whether this browser has liked the article.

For a like, the Journal database stores the article slug, a keyed hash derived from the cookie identifier, and the creation time. The record is pseudonymous and is not linked to a BUMS account. The public can see article like totals, not the stored visitor hash.

To limit abuse, the API receives a network address from Vercel and stores a keyed hash of it in the Journal rate-limit table; the Journal tables do not store the address in plain text. For write limits, the API also stores a keyed hash derived from the visitor identifier. Direct table access is denied to anonymous and authenticated roles; only the backend service can call the database functions. Vercel receives the network address as part of the request and may process technical data under its applicable terms.

The 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 your name, email address, or BUMS account credentials. The pseudonymous identifier is used to remember that like, allow a later unlike, and rate-limit write requests. For read rate limiting, the API uses a keyed hash of the network address supplied by Vercel, rather than the cookie identifier. For write rate limiting, the database function uses keyed hashes derived from both the network address and visitor identifier. Rate-limit entries become eligible for deletion after 24 hours and are deleted during a later API call; there is no scheduled cleanup, so they may remain longer. V14 tables do not record a page-by-page reading history: they store slugs for likes actually placed and rate-limit counters. The cookie is not used by the Journal implementation for analytics, profiling, advertising, or cross-site tracking. Hosting providers may process technical request metadata under their own notices.

Cookie controls

The cookie is marked Secure, HttpOnly, and SameSite=Lax, has no declared Domain attribute and is host-only. New cookies expire no later than 90 days after issue, a limit also enforced by the server. 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. Its functional purpose alone does not establish that it is legally exempt as strictly necessary; the controller must assess that classification and whether consent is required before public activation. You can remove it in your browser settings. Removing or letting it expire does not delete a like already stored; after the cookie is gone, the site cannot recognize or remove that browser's like. An unlike request without a cookie does not mint a new one.

Retention

A like has no automatic expiry in the current implementation. It remains until it is removed through the same browser's unlike control or the record is erased. Rate-limit records, including keyed network-address hashes used for GET, are deleted by the API when their last activity is older than 24 hours; this cleanup runs during later API calls, not on a separate schedule.

Supabase database backups follow the project's configured backup window. The project's Pro plan provides access to the latest seven daily backups according to Supabase's backup documentation. A backup window is not a guarantee of immediate deletion from every copy.

Your rights and contact

You can remove a like while the original browser cookie is available. For privacy requests or questions, contact i@bumsapp.com. Because Journal likes are not linked to BUMS accounts, identifying a past like may not be possible after its cookie has been removed or expired.

See also the Cookie Policy and the full BUMS Privacy Policy (Italian).

BUMS
© BUMS
Full Privacy Policy (Italian)Journal likes privacyCookie PolicyJournal