Last updated: April 17, 2026
When you create an account, we collect your email address for authentication. If you sign in with Google, we also import your Google profile photo as your avatar.
If you choose to set up a public profile, we store the information you provide: username, display name, bio, avatar, social media handles (Instagram, TikTok, YouTube), website URL, and tip platform details (Venmo, Cash App, or PayPal username).
Your custom cocktail recipes are stored in our database and are private by default. Only recipes you explicitly mark as public are visible to others. Menus you create are also private by default.
Your email is used solely for signing in and for occasional important updates about the app. These updates are infrequent — we don't spam. We will never sell, share, or rent your email address or any other personal information to third parties.
We use PostHog for anonymous product analytics — things like feature usage, page views, and search activity — to improve the app. No personally identifiable information is sent to PostHog.
We also log search queries that return no results so we can improve our recipe library. These are stored without any connection to your account.
If you create a public profile, your username, display name, bio, avatar, social links (Instagram, TikTok, YouTube, website), tip link, public recipes, and public menus are visible to anyone who visits your profile page. Subscriber counts for your recipes and menus are also visible. Everything else remains private.
If you follow another user, that relationship is stored privately — follower counts are not displayed on profiles. When you follow someone, their public recipes and menus are copied to your library and kept in sync. When they add or edit public content, you receive in-app notifications (after a brief delay to account for editing sessions).
Houses represent bars, restaurants, or cocktail programs. If you are assigned as an owner or manager of a House, we store your role and association. House profiles can be made public, which makes the House name, bio, logo, social links, custom URLs, and public recipes/menus visible to anyone.
If you are invited to a House as staff, we generate a tokenized invite link. The token itself is stored as a one-way hash — we never store the plaintext token. When the invite link is used, we log the IP address and user agent of the device that redeemed it, solely so House managers can monitor access. This data is visible only to the House owner and managers.
You can follow a House's public profile, which works the same as following a user — their public recipes appear in your library. If you are already a staff member of a House, your follow is preserved but dormant until you are no longer a member.
Your data is stored securely on Supabase (hosted on AWS). Authentication tokens are stored in your browser's local storage. Cocktail data, your library, and your preferences (like ingredient ordering) are cached locally for offline access and cleared when you sign out.
You can update or delete your profile information at any time through the app. You can unfollow any user or House at any time, which removes their synced content from your library. You can also delete your account entirely from within the app — this permanently removes your profile, recipes, menus, follows, notifications, subscriptions, and all associated data. Your username is held for 30 days before becoming available again. Note: if you are the sole owner of a House, you must transfer ownership or delete the House before deleting your account.
If you need help with account deletion, contact us at behind@speedpour.app.
Speed Pour does not use tracking cookies. We use browser local storage for authentication and offline caching only.
If we make meaningful changes to this policy, we'll note it in our release notes.
Questions? Reach out at behind@speedpour.app.