Your bar, on your device.
Updated November 12, 2026. This page describes the current development version of Pour, this website, and its browser demo. It will be updated before features that change data handling are released.
The current iPhone app
Pour stores recipes, ingredient lists, inventory, shopping lists, favorites, venue names and check-in state, and preferences locally. Venue check-in is a label you select in the app; it does not use your location. The current code does not include an account service, advertising SDK, analytics SDK, or a network service for uploading this data.
When you use the Share action, recipe text goes to the app or person you select in the iOS share sheet. That destination handles the shared text under its own privacy practices.
Offline Bar Assistant
The Bar Assistant uses rules to answer supported questions from recipes and inventory on your device. Questions and replies stay in the app’s memory while the assistant is open; they are not uploaded, saved to the recipe database, or sent to an AI provider. It does not record your voice or search the web.
Purchases in development
The current project includes purchase, restore, and subscription-entitlement flows using Apple’s StoreKit. The shared development scheme uses a local StoreKit test configuration; these simulated purchases do not charge you. Live App Store products and a public subscription are not available yet.
When live purchases are enabled, Apple will process payments under its own privacy practices. Pour’s StoreKit implementation reads product and verified transaction information to determine access; it does not receive card details or upload recipes, inventory, or shopping lists. The free tools keep working offline with no subscription.
Backups and removal
Local storage does not mean a separate backup. Device backups may include app data, depending on your Apple settings. The current app does not provide cloud sync or a complete export-and-restore feature. Removing the app removes its local data; copies in device backups and anything you shared elsewhere are managed separately.
Permissions and future features
Barcode scanning uses the camera only to read a barcode on this device. Pour does not store camera images and does not send them anywhere. The barcode and the bottle name you confirm stay with the rest of your local inventory. You can enter a barcode or ingredient manually if camera access is unavailable.
Voice search, cloud sync, online AI services, and team features are planned. The current app does not implement microphone or speech recording. Before features with new data handling ship, this page and the relevant permission explanations will describe their data use.
This website
This site serves its own images, styles, and scripts through Cloudflare Pages. It does not add analytics, advertising, signup forms, or cookies. Cloudflare handles normal requests and may process technical information such as IP addresses and request logs to operate the service. See Cloudflare’s privacy policy for its practices.
Browser demo storage and clipboard
The browser demo saves your selected ingredients, shopping list, servings, measurement unit, and selected recipe in this browser’s local storage. This data stays in the browser; the demo does not upload it or sync it with the iPhone app. If browser storage is unavailable, changes last only for the current tab session.
Use “Reset demo” and confirm to clear the saved demo state and restore the starter ingredients. You can also remove the site’s data in your browser settings. When you choose “Copy recipe,” the demo writes the displayed recipe text to your clipboard. If clipboard access is blocked, it offers text you can select and copy yourself.
Links to GitHub and other destinations leave this website. Those services handle your visit under their own policies.
Questions or a security concern?
For general questions, open a GitHub issue. Do not include personal information, credentials, or vulnerability details in a public issue. Use the repository's private vulnerability reporting option when it is available. The support page uses this same path.