Last updated: October 27, 2026
Speed Pour is operated by Boyfriend Solutions LLC.
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.
Recipes also carry automatically-detected allergen tags, derived from your ingredient list (you can override them manually). These are stored as part of the recipe. Allergen detection is a convenience and may be incomplete — see our terms.
Your email is used for signing in and for occasional important updates about the app. These updates are infrequent, and we don't spam. We will never sell or rent your personal information. We share it only with the providers that run Speed Pour, each of which is named in this policy, and only so they can do their part.
We use PostHog for product analytics, covering things like feature usage, page views, and search activity. Events are tagged with your Speed Pour account id, so they are linked to your account rather than gathered anonymously. If you are signed out, a random id generated in your browser is used instead. Your email address, phone number, and the text of your searches are never 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.
Each public recipe also has its own shareable link (e.g. speedpour.app/your-username/recipe-name). Anyone with the link — or who saves or riffs the recipe — can view it, the same as visiting your public profile.
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. Anyone with an account can create one, and the person who creates a House becomes its owner. We store your role in every House you belong to, along with the association itself. 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.
A House manager can generate a six-digit Quick Code that gives a shared device read-only access to that House, with no account and no sign-in. It is built for a terminal behind the bar.
The six-digit code is stored in readable form, because a manager has to be able to see it and read it out. This is a deliberate difference from staff invite links, whose tokens are stored only as a one-way hash. A Quick Code does not expire on a timer: it works until a manager issues a new one, ends that device's session, or turns Quick Code off for the House.
When a device redeems a code, we store the user agent it reports (its browser and operating system) and the times it was first and last seen, so a manager can see which devices are on their House and cut one off. A device holds no profile, library, or preferences, because there is no account behind it.
We log the IP address of every code entry, whether it succeeds or fails, to stop someone guessing their way into a House. This happens whether or not you have an account. These records are kept for 30 days, then deleted automatically.
House subscriptions are billed through Stripe. Stripe collects and processes your card details directly. Speed Pour never sees, receives, or stores a card number.
For each House we store the Stripe customer and subscription identifiers, the subscription status, and the date the current billing period ends. We use these to decide whether a House is active and which billing controls to show you. Your billing name, address, and payment method are held by Stripe under its own privacy policy.
Billing changes and cancellation are handled in Stripe's billing portal, which you reach from the House screen.
Speed Pour lets you import recipes by snapping a photo of a menu, build sheet, or handwritten recipe, or by uploading a PDF — and managers can also upload spreadsheets. When you do this, we send the image or file you upload to Anthropic's Claude API to parse the contents into structured recipe data.
We use Anthropic's API (not the consumer Claude product). Per Anthropic's policies, API content is not used to train their models. We don't store the source image or file after parsing — only the resulting structured recipe data, which goes into your library as a normal recipe you can review, edit, or delete.
Don't upload anything you don't have the right to share — see our terms for the full rules.
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 support@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 support@speedpour.app.