Disclaimer
How this site relates to retailers, how predictions work, and why rows can disagree with what ships.
Independence
Skip or Keep is a personal project I run on my own time, and I have no employment, partnership, or paid promotional relationship with any subscription box company, publisher, or author whose names or products show up in the catalogue. The pages here are meant to organise public information and record how I read it, and they should never be read as a statement issued by any of those organisations. If you notice language that could be taken to imply an official link where none exists, I would appreciate a short note so I can correct it, because keeping that boundary clear matters to me.
Predictions
Each book prediction is something I write after going through the same public sources anyone could open, mainly retailer sites and social posts that are already visible, along with whatever dates and artwork those pages attach to a given month. I do not start from a ranked digest of leaks or from community vote totals and then paste the winner into a box row, and if you sat down with the same links you might still end up with a different title in your notes because the clues really do leave room for more than one reading. What you read under predictions is therefore my own call, and I do not fill those fields by copying wholesale from someone else's running rumour list or account.
Accuracy
A prediction is an inference drawn before the full facts are public, which means it can diverge from what the retailer eventually confirms once marketing settles and the final title is announced, and when that divergence appears it reflects the limits of the evidence I had at the time or an error in how I weighed it, and it does not mean the site claims exhaustive coverage of every unofficial mention before confirmation. Until you see confirmation from the seller, you should assume every prediction here can be mistaken even when the reasoning is laid out carefully.
Catalogue data
Theme names, months, cover images, and similar catalogue fields are assembled through scraping and small maintenance scripts that pull from public pages and feeds, and those pipelines occasionally return stale rows, duplicated months, or garbled text when a layout changes upstream. When a line in the table looks wrong, the first explanation to check is usually an ingestion bug on my side rather than a silent policy change at the retailer, although I still try to refresh data when I learn that a source page has moved or been rewritten.