Privacy, plainly
You can browse Ripened without an account. The site has no third-party advertising or advertising tracker. It does use first-party storage and optional Google sign-in for product features.
On this device
Your likes, lists, filters, theme and taste settings are stored in browser local storage. Clearing site data removes that local copy. A random device identifier supports community recommendations and first-party product measurement.
Community recommendations and measurement
Community sharing is on by default and can be turned off in Settings. While on, Ripened sends the random device identifier, title interactions and compact product events to its own backend. It does not attach your Google name or email to those rows. Turning it off stops future sharing and requests deletion of that device identifier’s contributed taste and event rows; Settings confirms whether the request succeeded.
Google sign-in and synced profiles
Google sign-in is optional. When used, Ripened verifies Google’s ID token and stores a time-limited session plus your Google subject identifier, name, email and picture. The subject identifier keys your synced profile so your lists and taste can follow you across devices. Signing out clears the session from this device and asks the backend to revoke it; it does not delete your synced profile.
Groups and public links
A group link is intentionally readable by anyone who has it. It can show the group name, shared titles, member display names and member-selected Ripened avatars or canon picks. Public responses do not include member email addresses, Google subject identifiers or Google profile pictures. Signed-in group members receive the identifiers needed for membership controls.
Release reminders and infrastructure
If you request a one-time release reminder, Ripened stores the email address, title and target date until the message is sent or the record expires; sent rows are deleted. Cloudflare processes request IP addresses to deliver and protect the service, including coarse country lookup and rate limiting. Cover images load from catalog providers’ image networks. Google Fonts and the Google sign-in library may receive a request when the site loads; catalog search, import and account verification requests happen when those features are used.