ChillCheck

ChillCheck is a temperature and cooling log for small restaurant kitchens — the fridge, freezer and cooling records a health inspector asks for before anything else. **The problem it is actually solving** In most US counties, inspection results are public and the grade goes in the window, so a missing temperature log has a direct line to revenue. And almost every independent café and restaurant still keeps that log on a clipboard hanging by the walk-in. Nobody skips it because they are careless — they skip it because it is 2pm on a Saturday and nothing in the kitchen is asking them to. The gap is usually discovered when an inspector is already standing there. So the record has exactly one job: to exist. ChillCheck is built around that and not around a feature list. **What it does** - Register your units — walk-in, reach-in, freezer, hot holding — each with its own target range - Set the times each unit gets checked, and get a reminder at each one - Log a reading with the number pad and nothing else in the way - When a reading falls outside the range you set, record what you did about it, with an optional photo - Run a two-stage cooling timer: it works out both deadlines from your start time and warns you before each one - Fill in a day you missed, because a log with a hole in it is the normal case - Export the month as a PDF an inspector can read - °F or °C, and it works completely offline **Four decisions that shaped it** *Notifications are the product.* Reminders at the times you set, plus one catch-up at the end of the shift if something is still blank. There is a hard cap of four a day, written into the code. The moment people start swiping them away, this app is dead — so more reminders is the one feature request that will always be refused. *No account, no server, no cloud.* Everything lives in local SQLite on the phone. It works fully in airplane mode, because kitchens have terrible signal, and because the surest way not to leak a restaurant's data is never to receive it. No sign-up, no email, no login. Backup runs two ways: a snapshot that rides along with your iCloud or Android backup, and a file you save through the OS document picker, which is what moves a kitchen to a new phone or across platforms. Neither is behind the paywall — getting your own records off your own phone is not something to sell. *It never tells you food is safe.* It records what you measured, shows when a value falls outside the range you set, and prompts you to write down what you did about it. It does not certify compliance with anything, and it says so on the export and in the app. The built-in FDA Food Code numbers are shipped as editable defaults, not as requirements. *Late entries stay marked as late.* You can backfill a missed day — you have to be able to, or nobody uses it in a real kitchen — but the entry is stamped as entered late, and a correction leaves a timestamp, the way a paper log is corrected with a line and an initial rather than an eraser. A log that can be quietly rewritten is worth nothing to the person you are showing it to. **Try the month before you have one** On day one your calendar and your PDF are both empty, which is the exact thing you are deciding whether to pay for. So the app can load a sample month from a small café — out-of-range readings with their corrective actions, an entry filled in late, a slot nobody got to, two completed cooling lots — and remove it again in one tap. While it is loaded, every export is marked as sample data on the cover, in the header, in the footer and in the filename. **What is deliberately not in it** No staff management or shift scheduling. No inventory. No HACCP plan builder. No Bluetooth thermometer integration. No multi-location. No cloud sync or web dashboard. No AI. This is a single-location tool for one kind of kitchen, and it stays that way. **Pricing** Seven days of full access — the whole app, not a crippled version — then $24.99/month or $199/year. Prices come from the store, so they follow your region. Purchases are handled by Apple and Google through RevenueCat; the entitlement is cached, so a kitchen that loses signal does not lose the app it paid for. **Privacy** Your readings, notes, photos, corrective actions and cooling logs never leave the device. The only thing that does is the purchase receipt, which goes to RevenueCat and to Apple or Google, tied to an anonymous ID with no account behind it. There is no analytics SDK and no advertising identifier. **Availability** iOS and Android, in the United States, Canada, Australia and New Zealand. Built by one person, in Flutter. Feedback from anyone who has run a kitchen — or been inspected in one — is the thing I want most.