Privacy Policy

Effective: March 6, 2026  ·  Last Updated: March 11, 2026

Pour ("we," "our," or "us"), operated by Party On NWA LLC, is a cocktail recipe and home bar management app for iPhone, iPad, Apple Watch, and as an App Clip. This policy explains what data we collect, how we use it, and your rights.

1. Data We Collect

1.1 Account Data (optional — only if you sign in)

No account is required to use Pour. All core features work without signing in. If you create an account or sign in with Apple or Google, we collect:

• Email address — used for authentication and transactional email (see Section 1.13)
• Display name — sourced from Apple or Google Sign-In on first login; used only within the app
• User ID — a unique identifier generated by Supabase, our authentication and database provider

1.2 Synced Bar & App Data (only if signed in)

If you sign in, the following data is synced to our cloud infrastructure (Supabase) to enable cross-device access and backup:

• Bottles in your bar (name, spirit type, quantity)
• Favorite recipes and shopping list items
• Drink journal entries (see Section 1.3 for full detail)
• Custom recipes you've created
• Recipe collections (Pour Lists)
• Chat conversation history (Pour IQ)
• Pour Sessions progress (steps completed, sessions finished)
• Taste graph data (see Section 1.8)
• Pour Passport badge progress and achievement history (see Section 1.7)
• Community Riffs you've submitted (public — see Section 1.4)
• Shared Bar state (Pour for Two — see Section 1.5)

All synced data is associated with your user ID and is not shared with advertisers or data brokers.

1.3 Drink Journal

When you log an entry in your Drink Journal, you may provide any or all of the following:

• Recipe name and date (automatically populated)
• Star rating (1–5)
• Mood (selected from preset options)
• Tasting notes (free-text)
• Spirit type and flavor tags (selected from preset options)
• Location text (optional; you type this yourself — your GPS location is never requested or stored by the Journal)
• Photo (optional; stored locally on your device only and never transmitted to any server or third party)

If you are signed in, all journal fields except photos are synced to Supabase. Journal photos remain on your device at all times.

1.4 Community Riffs (public)

Pour lets you submit "Riffs" — your personal variations on cocktail recipes. When you submit a Riff:

• The Riff content (your ingredient changes, notes, and recipe ID) and your display name (or "Anonymous" if none is set) are visible to all Pour users.
• Riffs are stored in Supabase and are subject to our Community Content Guidelines in the Terms of Service.
• You may delete your own Riffs at any time from within the app. Deletion removes them from Supabase within 30 days.

Do not include personal information in your Riff content that you do not want to be publicly visible.

1.5 Shared Bar / Pour for Two

The Shared Bar feature allows two users to voluntarily link their bar inventories. By accepting a Shared Bar invitation:

• Your bar inventory (bottle names and quantities) becomes visible to your linked partner.
• Your partner's bar inventory becomes visible to you.
• This sharing is explicit and consent-based — it requires one user to generate an invite code and the other to enter it. It does not happen automatically.
• You can unlink your Shared Bar at any time from My Bar → Shared Bar → Unlink. This immediately ends all shared visibility.

1.6 Bartender Mode (on-device)

Bartender Mode provides event planning, recipe scaling, cost calculations, and menu generation for hosting cocktail events. All Bartender Mode data is processed and stored entirely on your device using local SwiftData storage. No Bartender Mode data — events, guest counts, cost figures, menus — is transmitted to Supabase or any external server.

1.7 Pour Passport & Achievements

Pour Passport tracks your cocktail achievements, badges, and streak history. This data is:

• Computed on-device from your journal, session, and app activity.
• Stored locally in SwiftData on your device.
• If signed in, synced to Supabase as part of your account data (same as bar data in Section 1.2).
• Not shared with any third party other than Supabase for sync purposes.

1.8 Taste Intelligence (Taste Graph)

Pour builds a "taste graph" that tracks your spirit preferences based on your activity, including:

• Spirit affinity scores (e.g., Whiskey: 0.82, Gin: 0.61)
• Adventure Index (how broadly you explore different spirit categories)
• UserEvent history (swipes, favorites, journal logs, session completions — used to compute the above)
• Total events and last-activity date

All computation happens entirely on your device. If you are signed in, your taste graph data is synced to Supabase as part of your account data. Aggregate taste graph data (scores only — no personally identifiable information) may be used to improve personalized recommendations within the app. It is never shared with advertisers, data brokers, or any third party other than Supabase for sync.

1.9 Pour Vision (Camera)

When you use Pour Vision to scan a bottle:

• Live Scan (free): image processing occurs entirely on-device using Apple's Vision framework (OCR). No image or image data is transmitted.
• AI Photo Analysis (Pro): the photo is sent to our server (Supabase Edge Function) and then forwarded to Anthropic's Claude API for bottle identification. The image is not stored after the response is returned. The Edge Function processes the image in memory only.

1.10 Pour IQ (AI Chat)

When you use Pour IQ, the following is sent to Anthropic's Claude API via our Supabase Edge Function:

• Your chat message
• Optional context to personalize the response, which may include: your bar inventory (bottle names and spirit types), a summary of your taste graph, recent journal entry names, and session completion history

Chat history is stored locally on your device and, if signed in, synced to Supabase. Chat content is not used to train Anthropic's models, per our API agreement with Anthropic.

1.11 Video-to-Recipe Import (Pro)

When you use the Video-to-Recipe Import feature to extract a cocktail recipe from a video link (YouTube, TikTok, Instagram, or Facebook):

• Your video URL is sent to our server (Supabase Edge Function).
• Our server retrieves the publicly available transcript or text metadata from the video URL. We do not download, access, or store the actual video file — only the text that is already publicly accessible.
• The transcript text is forwarded to Anthropic's Claude API for recipe extraction. The text is not stored by Anthropic after processing, per our API agreement.
• If a recipe is successfully extracted and you choose to save it, the video URL, platform name, channel name, and video title are stored with the saved recipe — locally on your device and in Supabase if you are signed in.
• Recipe Import is limited to 5 imports per day for Pour Pro subscribers. Usage is tracked server-side per user account.

We do not affiliate with, receive compensation from, or store content from YouTube, TikTok, Instagram, or Facebook beyond the publicly available transcript text described above. The feature operates on text metadata only.

1.12 Monthly Recap (on-device)

At the start of each month, Pour generates a summary of your prior month's cocktail activity. This is computed locally from your existing journal and session data — no new data is collected or transmitted. If you save a recap, it is stored as a journal entry on your device (and synced to Supabase if signed in).

1.13 Push Notifications

If you grant notification permission, we collect and store the following data to deliver notifications:

• APNs device token — issued by Apple; stored in Supabase and shared with OneSignal (see below) solely for notification delivery.
• OneSignal Subscription ID — a device-level identifier assigned by OneSignal; stored in Supabase. This is not linked to your account identity.
• Notification preferences — your opt-in status for each notification type (Cocktail of the Week, Seasonal Specials, Monthly Recap). Stored in Supabase and synced to OneSignal as segmentation tags.

Push notifications are used only to deliver:

• Cocktail of the Week — a weekly hand-picked recipe spotlight (opt-in)
• Recipe unlock alerts — when adding a bottle unlocks new cocktails
• Seasonal Specials — timely cocktail recommendations (opt-in)
• Monthly Recap — a summary of your prior month's cocktail activity (Pro subscribers, opt-in)
• Trial expiring reminders — for Pour Pro free trial subscribers

OneSignal (onesignal.com) processes push notification delivery on our behalf. OneSignal receives your device token, OneSignal Subscription ID, and notification preference tags. OneSignal does not use this data for advertising or share it with third parties for marketing. See OneSignal's Privacy Policy.

Push tokens and preference data are not shared with advertisers or used for tracking. You can revoke notification permission at any time from iOS Settings or within Pour → Settings → Notifications.

1.14 Transactional Email

If you create an account with an email address, we may send the following transactional emails:

• Welcome email — sent when you create your account
• Trial expiring reminder — sent before your free trial ends
• Feedback responses — replies when you contact us via [email protected]

Transactional emails are sent via Resend (resend.com), a transactional email provider, from the hellopour.com domain. We do not send marketing or promotional emails, and we do not share your email address with third parties for marketing purposes. You can request opt-out from non-essential transactional emails by contacting [email protected].

1.15 Widgets & Siri Shortcuts (on-device)

Pour's home screen widgets and Siri Shortcuts access your bar and preference data stored in a shared App Group container on your device. This allows widgets to display your daily drink suggestion, bar statistics, recent journal entries, and other personalized content. No data is transmitted to any network when widgets refresh or when Siri Shortcuts run — all access is to on-device local storage only. Siri Shortcuts that open the app (e.g., "Open Pour Vision") do not transmit any data.

1.16 App Clips

If you access Pour via an App Clip (from a link at hellopour.com/recipe/* or hellopour.com/session/*):

• No account is created or required.
• No personal data is collected or stored.
• Recipe and session content is loaded from public static JSON files hosted on our server.
• If you install the full app after using an App Clip, your App Clip activity is not transferred to the full app.

1.17 Seasonal Content

Pour includes seasonally-relevant cocktail recommendations. Seasonal content is primarily bundled within the app. We may optionally deliver seasonal content overrides via a server response (Supabase Edge Function) to keep recommendations current. No user data is collected, sent, or used in the delivery of seasonal content — it is broadcast equally to all users. The seasonal content response contains recipe IDs and display metadata only.

1.18 Location

Location access is only requested when you tap "Find Nearby Stores" in My Bar → Shopping List. Your location is passed directly to the system map (Apple Maps) for store search and is never stored, logged, or transmitted by Pour. The Drink Journal's location text field is free-text entry only — your GPS location is never accessed for journal entries.

1.19 Anonymous Usage Data

The following data may be collected without an account and is not linked to your identity:

• Device ID — used for anonymous rate limiting (AI chat and swipe limits for non-account users). Not stored permanently beyond the rolling 24-hour window.
• Rate limit counters — stored temporarily (per session or rolling 24-hour window) to enforce free-tier usage limits.
• Anonymous recipe interaction events — aggregate counts used to identify trending recipes. No personal identifier is attached.

1.20 Pour Mix (AI Cocktail Creator — Pro)

Pour Mix is an AI-powered feature that generates custom cocktail recipes based on your text prompts (e.g., "something tropical with rum and mango"). When you use Pour Mix:

• Your prompt text is sent to our server (Supabase Edge Function) and then forwarded to Anthropic's Claude API for recipe generation.
• Optional context to improve the response may also be included: your bar inventory (bottle names and spirit types) and your taste preferences. This context is identical to what is sent for Pour IQ (see 1.10).
• Prompts are not stored after the response is returned. The Edge Function processes them in memory only.
• If you choose to save a generated recipe, it is stored locally on your device as a custom recipe and synced to Supabase if you are signed in. The saved recipe is indistinguishable from any other custom recipe in your account.
• AI-generated recipe content is not stored by Anthropic after the API response, per our API agreement.

Pour Mix is available to Pour Pro subscribers only.

1.21 Recipe Images (AI-Generated)

Pour includes high-quality cocktail images for recipes in the library. These images are AI-generated using Google's Imagen 4 model and are produced by us during app development — they are not photographs of actual drinks, and they are not generated in real time during app use.

• Recipe images are pre-generated static assets bundled with the app or served from our CDN. No user data is involved in their generation or delivery.
• Your device does not communicate with Google or any AI image service when displaying recipe images.
• Images are for illustrative purposes only and may not exactly represent a finished cocktail.

1.22 Flavor Map & Ingredient Profiles (On-Device)

The Flavor Map visually represents cocktail flavor relationships across categories such as citrusy, smoky, herbal, and sweet. Ingredient profiles provide tasting notes, origin information, and pairing data for spirits in your bar.

• All Flavor Map processing is on-device only. No data is transmitted to any server to compute or display flavor relationships.
• Ingredient profiles are bundled within the app as static reference data. They are not generated dynamically and do not require any data from your device to be sent externally.
• Neither feature collects, stores, or transmits any personal data.

2. How We Use Your Data

Purpose	Data Used
App functionality (recipes, What Can I Make, bar tracking)	Local bar data, taste graph
Cloud sync & backup across devices	Account + bar data (Supabase)
Personalized recommendations (New for You, Taste Journey)	Taste graph (on-device)
AI chat responses (Pour IQ)	Chat messages, bar & journal context (Anthropic)
AI bottle identification (Pour Vision Pro)	Camera photo (Anthropic, not stored)
Video-to-Recipe Import (Pour Pro)	Video URL + public transcript text (Anthropic, not stored); video metadata stored with saved recipe
Community Riffs display	Riff content, display name (Supabase, public)
Shared Bar visibility	Bar inventory (Supabase, shared with linked partner only)
Monthly Recap generation	Journal + session data (on-device only)
Pour Passport badge computation	Journal, session, achievement data (on-device + Supabase)
Widget & Siri content	Bar & taste data (on-device App Group only)
Seasonal recommendations	None (content is broadcast, no user data used)
Push notifications	APNs push token (Supabase)
Transactional email	Email address (Resend)
Pour Mix recipe generation (Pour Pro)	Prompt text + optional bar/taste context (Anthropic, not stored after response)
Recipe image display	No user data — pre-generated static assets
Flavor Map & ingredient profiles	No data transmitted — on-device only
Rate limiting (anonymous)	Device ID (temporary, not stored permanently)
Trending recipes	Anonymous interaction counts (no personal identifier)
Account authentication	Email, User ID (Supabase)

We do not use your data for advertising. We do not sell your data to third parties. We do not use your data to train AI models.

3. Third-Party Data Processors

Processor	Data Sent	Purpose
Supabase supabase.com	Email, User ID, bar data, journal entries (excl. photos), chat history, taste graph, push tokens, Riffs, Shared Bar state, achievements, session progress	Cloud PostgreSQL database, authentication, backup, Edge Functions (AI proxy)
Anthropic (Claude API) anthropic.com	Chat messages + optional bar/journal context; optional photo for Pour Vision Pro; video transcript text for Video-to-Recipe Import; prompt text + optional context for Pour Mix	AI chat responses (Pour IQ), bottle identification (Pour Vision Photo Analysis), recipe extraction (Video-to-Recipe Import), cocktail recipe generation (Pour Mix)
Google (Imagen 4) cloud.google.com	No user data — recipe images are pre-generated by us during development	AI generation of cocktail recipe images (offline, during app development only — not at runtime)
Resend resend.com	Email address, email content	Transactional email delivery (welcome, trial reminders, contact replies)
Apple (Sign in with Apple) apple.com	Name, email (first login only)	Authentication
Google (Google Sign-In) google.com	Name, email	Authentication
Apple Push Notification Service (APNs) apple.com	Push token, notification payload	Delivering push notifications to your device
OneSignal onesignal.com	APNs device token, OneSignal Subscription ID, notification preference tags	Push notification delivery and segmentation (Cocktail of the Week, Seasonal Specials, Monthly Recap)

No data is sent to advertising networks, analytics platforms, or data brokers.

4. Data Retention

• Account & synced data: retained until you delete your account. Account deletion from Settings → Account → Delete Account triggers deletion of all your data from Supabase (27+ tables) within 30 days.
• Local data (SwiftData): stored on your device until you delete the app or use Settings → Clear All Local Data.
• Journal photos: stored locally on your device. Deleted when you delete the journal entry or uninstall the app.
• Bartender Mode data: stored locally only. Cleared when you delete the app or use Clear All Local Data.
• Community Riffs: remain public until you delete them. Deletion removes them from Supabase within 30 days.
• Taste graph: deleted with your account (Supabase) or on app uninstall (device).
• Push tokens: deleted when you delete your account.
• Transactional email records: retained by Resend per their data retention policy. Your email address is not used for any purpose beyond delivering the transactional emails described above.
• Anonymous rate limit counters: session-based or rolling 24-hour window. Not persisted beyond that window.
• Chat messages (Anthropic): not retained by Anthropic after the API response is returned, per our API agreement.
• Pour Vision photos (Anthropic): not stored after the identification response is returned. Processed in memory only.
• Video transcripts (Anthropic via Video-to-Recipe Import): not retained by Anthropic after recipe extraction is complete. Not stored on our servers.
• Video metadata (URL, platform, channel, title): stored locally with the saved recipe if you choose to save it; synced to Supabase if signed in. Deleted when you delete the recipe or your account.
• Pour Mix prompts (Anthropic): not retained by Anthropic after the API response is returned, per our API agreement. Not stored on our servers.
• Pour Mix saved recipes: stored locally on your device as custom recipes; synced to Supabase if signed in. Deleted when you delete the recipe or your account.

5. Your Rights

• Access: View all your synced data within the app (My Bar, Journal, Pour Lists, etc.).
• Correction: Edit your bar inventory, journal entries, and profile data directly in the app.
• Deletion: Delete your account from Settings → Account → Delete Account. This triggers deletion of all server-side data. You can also delete individual items (journal entries, Riffs, bottles) at any time.
• Data export: Use Settings → Export My Data to download a JSON file of your bar data, journal, favorites, Pour Lists, and preferences.
• Data import: Use Settings → Import Data to restore from a previously exported JSON file.
• Opt out of sync: Sign out of your account. All data remains on-device only. The app is fully functional without an account.
• Notification opt-out: Disable notifications in iOS Settings or within Pour → Settings → Notifications.
• Shared Bar opt-out: Unlink your Shared Bar at any time from My Bar → Shared Bar → Unlink.
• Riff removal: Delete your Community Riffs at any time from within the app.
• Email opt-out: Contact [email protected] to opt out of non-essential transactional emails.

6. Children

Pour is rated 17+ on the App Store due to alcohol-related content. The in-app age gate requires users to confirm they are 21 years of age or older before accessing any content. Pour is intended for users aged 21 and older. We do not knowingly collect personal data from anyone under 21. If you believe a minor has provided us with personal data, contact us at [email protected] and we will delete it promptly.

7. Security

We take reasonable measures to protect your data. Supabase encrypts data in transit (TLS) and at rest. Row-Level Security (RLS) policies on Supabase ensure you can only access your own data. Authentication tokens are stored in the iOS Keychain. However, no method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

8. Changes to This Policy

We will update this policy when material changes occur — such as new data types, new third-party processors, or features that collect data differently. The "Last Updated" date at the top reflects the most recent revision. We will make reasonable efforts to notify you of significant changes through the app or by email. Continued use of the app after a policy update constitutes acceptance of the revised policy.

9. Contact

Questions about this Privacy Policy or your data?

• Email: [email protected]
• Entity: Party On NWA LLC
• Website: hellopour.com/privacy