Privacy Policy

1. Who we are and what this notice covers

Ovenbell is operated by Wild West Labs LLC. This notice explains how we handle information when you use the new Ovenbell website and seller app, visit a seller's storefront, place or manage an order, contact a seller, or use our public resources. Contact support@ovenbell.com with privacy questions or requests.

Sellers use Ovenbell to run their own businesses. A seller receives information about its customers and orders and is responsible for how it uses that information outside Ovenbell. Contact the seller about its own records and practices. This notice does not replace notices provided by payment services, sign-in providers, or the separately hosted legacy Peppery label-maker service.

2. Information you and sellers provide

Account and shop information can include your name, email, phone number, profile image, sign-in identifiers, shop name, location, pickup or delivery instructions, business settings, product listings, prices, ingredients, allergen information, photos and other content you provide. Sign-in is handled by Clerk. If you choose Google sign-in, we receive basic identity information such as your name, email address and profile image, as permitted by that sign-in flow.

Order and customer records can include names, contact details, requested products, custom-order answers, reference images, event or pickup dates, delivery addresses, quantities, order notes, messages, payment status, refunds and activity history. Sellers may also enter information received outside Ovenbell. Only provide information you are entitled to share, and avoid including unnecessary sensitive information in notes, images or AI imports.

We also keep communication preferences and consent records, support correspondence, and information submitted to receive guides, label resources or news. A reference to an allergy in an order can reveal sensitive information; share only what the seller needs and contact the seller directly about food-safety questions.

Our hosting, authentication and delivery providers may record IP addresses, browser and device information, access times, security events and delivery results. Ovenbell's operational records and logs can include account identifiers and message or order details. Resource requests and new shops can also record how the visitor reached Ovenbell (see section 7), and resource requests record the selected state, download and signup activity.

3. Payments

Stripe processes card payments and connected-account setup. Card details entered in Stripe's payment fields go to Stripe. Ovenbell stores payment references, amounts, currencies, status and refund information needed to manage orders; it does not store full card numbers or card security codes in its order records.

In the native iPhone and Android apps, subscriptions to Ovenbell are processed by Apple or Google through RevenueCat. RevenueCat receives an account identifier, purchase and subscription records, entitlement status and device or app information needed to provide purchases and restore access. Apple and Google handle the store payment details under their own policies. These subscriptions are separate from customers paying a seller for physical goods.

A seller can offer direct methods such as cash, Venmo, Zelle or Cash App. The seller's payment instructions may appear on private order pages and in emails. Those payments are made outside Ovenbell's card checkout, and the seller records whether payment was received. The relevant payment service handles the information you provide directly to it.

• Stripe Privacy Policy
• RevenueCat Privacy Policy

4. How we use information

We use information to provide sign-in and shop tools; display storefronts; process and organize orders, deposits and balances; support pickup and delivery; deliver requested resources and service messages; save drafts and preferences; provide support; and maintain payment and operational records.

We also use service and activity information to diagnose problems, protect accounts, prevent misuse, understand use of public resources, and meet applicable legal obligations. Marketing subscriptions are separate from the information needed to fulfill an order.

5. AI-assisted imports

When a seller asks Ovenbell to turn submitted text or images into a draft, we send that material and relevant context, such as product names, the shop's timezone and dates, to OpenRouter and the model provider that processes the request. Image links and filenames can be included. Ovenbell stores the submitted material and the resulting draft so the seller can review and edit it.

We also send shop and product names and descriptions, which are public on storefronts, to Anthropic to check listings for prohibited items. For Where to post, we send the public details of Facebook groups found near a shop, such as their names, member counts, locations, descriptions and posting rules, and any group rules a seller pastes, to Anthropic to sort the groups and summarize their rules. To write a seller's post for a group or for Nextdoor, we send Anthropic the shop's name, the seller's first name, the drop or products with their prices, pickup days, times and places and order deadlines as the storefront shows them, the neighborhood or town (never the street address), the shop's link and that group's rules.

AI providers have their own retention and data-use policies. We do not promise that every provider deletes inputs immediately or excludes every input from training. Do not submit passwords, payment credentials, identity documents or unnecessary customer information. Sellers can enter details manually instead of using AI. AI suggestions require seller review before they become published products or confirmed business actions.

• OpenRouter Privacy Policy
• OpenRouter provider data policies

6. Who receives information

The seller associated with an order receives the information needed to manage it. People the seller authorizes, including helpers using shared access links, may see customer and order details and perform permitted shop operations. Public shop content and an address configured for public display can be viewed by visitors and search engines.

Private order, quote, preference and helper links can grant access without a separate account. Treat them as private: someone you forward a link to may be able to view information or take actions through it. Sharing an order link is different from sharing the public storefront link.

We use service providers for hosting and storage (including Vercel and Convex), authentication (Clerk and your chosen sign-in provider), card payments (Stripe), app subscriptions (Apple, Google and RevenueCat), email delivery (Resend), text message delivery (Twilio), analytics (Google Analytics and PostHog), mobile install attribution (AppsFlyer), maps (the US Census Bureau and OpenStreetMap), local group search (Apify), and AI processing (OpenRouter, Anthropic and model providers). Firebase and browser or device push services process device tokens and notification delivery when push is enabled. These providers receive information needed for their roles; some, including payment and identity providers, also process information under their own notices.

If a seller uses Where to post, we send the shop's pickup address to the US Census Bureau's geocoder and, when the Census Bureau doesn't recognize it, to OpenStreetMap's Nominatim service; a shop with only a town sends just the town's name. Those services then receive the address's map point and points around it, not the address itself, to name the neighborhood and the towns nearby. We keep the neighborhood and town names with the shop, not the map point. To find local Facebook groups, we send only town and neighborhood names to Apify, which searches the web and Facebook's public search; no seller or customer information goes to Apify. Posts a seller copies from Ovenbell name the neighborhood or town, never the street address.

We may disclose information when required by law, to respond to valid legal requests, to protect rights and safety, to investigate misuse, or as part of a business transfer subject to applicable privacy requirements. We do not operate a marketplace selling customer contact lists.

Mobile numbers and text consent are not shared with third parties or affiliates for their marketing or promotional purposes. Service providers that deliver our texts, such as Twilio, receive your number only to deliver them. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

7. Cookies, device storage, analytics and attribution

Ovenbell and its service providers use cookies and similar technology for sign-in, security and service operation. Your browser can also store carts, drafts, saved checklists, cached pages, offline shop records and actions waiting to synchronize. People with access to your device may be able to access that stored information. Use a trusted device, sign out when finished, and use browser controls to clear site data when needed. Clearing data may remove unsynchronized work.

Our public marketing and guide pages use Google Analytics to measure visits and resource interactions. Product analytics use PostHog on the website and in the native apps. PostHog receives a limited set of page and feature events, account or pseudonymous device identifiers, platform, app version and browser/device information. We use this to understand use of Ovenbell and improve it. Our PostHog integration does not record sessions or automatically capture form contents and clicks. Private buyer, order, quote, helper, checkout and sign-in routes are excluded from our PostHog events; tracked pages use fixed route labels, and raw URLs, query strings, fragments and full referrer addresses are removed from those events. On our public marketing and guide pages, events can include the campaign tags of the link you followed (utm_source, utm_medium, utm_campaign, utm_content and utm_term) and the domain of the website that referred you.

To learn which channels bring new sellers to Ovenbell, our public marketing and guide pages set two first-party cookies, ob_ft and ob_lt, that last up to 90 days. They record your first visit and your latest visit that came from a campaign link or another website: the campaign tags, the referring website's domain (never the full address), an advertising click identifier when the link carried one (for example from Google, Microsoft, Facebook, Pinterest or TikTok), the Ovenbell page you arrived on and the time. When you create a shop or request a label kit, this information is stored with that record, and a summary without click identifiers is sent to PostHog. We use it to measure our own marketing. We do not set these cookies on sellers' storefronts or private links, and we do not send this information to advertising platforms. Ad measurement for ChatGPT, Google and Meta, described next, is separate. You can clear or block these cookies in your browser; Ovenbell works without them.

To measure our ads in ChatGPT, our server reports new Ovenbell seller shops created on our website to OpenAI through its Conversions API, unless you have opted out. When you arrive on our website from a ChatGPT ad, the link carries an OpenAI click reference, which we keep for up to 30 days in a first-party cookie, ob_oppref. The signup report contains a random event identifier, the time of the signup, our website address, your shop's country, state and city, a SHA-256 hash of your account email address (never the address itself) and the click reference when you have one. When the shop later starts a subscription, a second report adds the plan and its price. OpenAI uses these reports to credit our ads and improve their delivery, under its own terms. They do not include your name, phone number, shop contents, customer orders or payment details. We do not load OpenAI's browser pixel. Signups in our native apps are not reported, and nothing is recorded on sellers' storefronts or private buyer links.

To measure our Google ads, our server reports new Ovenbell seller shops created on our website to Google through its Data Manager API, unless you have opted out. When you arrive on our website from a Google ad, the link carries a Google click identifier (gclid, gbraid or wbraid), which we keep for up to 90 days in a first-party cookie, ob_gclick. The signup report contains a random event identifier, the time of the signup, a SHA-256 hash of your account email address (never the address itself) and the click identifier when you have one. Later reports follow the first time your shop is published, starts a subscription and makes its first payment; each carries the same email hash and click identifier, and the subscription and payment reports add the plan price. Google uses these reports to credit our ads and improve their delivery, under its own terms. They do not include your name, phone number, location, shop contents, customer orders or payment details. We do not load Google's advertising conversion tag. Signups in our native apps are not reported, and nothing is recorded on sellers' storefronts or private buyer links.

To measure our ads on Facebook and Instagram, we use Meta's pixel and Meta's Conversions API, from Meta Platforms, Inc., unless you have opted out. The pixel is a script from Meta that loads only on ovenbell.com's public pages, our sign-up page and the step where you create your shop, for visitors who have not opted out. It sets two first-party cookies: _fbp, an identifier for your browser, and, after you arrive from a Meta ad, _fbc, which holds the Meta click identifier (fbclid). It sends Meta a page view for each public page and the sign-up page you visit, a "sign-up page reached" event when you open the sign-up page and, when you create your shop, a signup event, together with what your browser sends any website it loads content from: your IP address, your browser's user agent (the description of your browser and device), the page address and the page you came from. Separately, our server reports new Ovenbell seller shops created on our website through the Conversions API. When you arrive from a Meta ad, we also keep the click identifier for up to 90 days in our own first-party cookie, ob_fbclick. The server's signup report carries the same event identifier as the pixel's signup event, so Meta counts your signup once, and contains the time of the signup, our website address, SHA-256 hashes of your account email address, your first and last name when your account has them, your shop's Ovenbell identifier and your shop's city, state and country (never the plain values), your browser's user agent, and the _fbp identifier and the click identifier when you have them. Later reports follow the first time your shop is published, starts a subscription and makes its first payment; each carries the same hashes, user agent and identifiers, and the subscription and payment reports add the plan price. Meta uses this information to credit our ads and improve their delivery, under its own terms. Our server reports include your name only as those SHA-256 hashes, never the name itself, and do not include your phone number, IP address, shop contents, customer orders or payment details. Signups in our native apps are not reported, and the pixel never loads in our apps, on sellers' storefronts, on private buyer links or in the rest of the seller app. Under California privacy law (the CCPA, as amended by the CPRA), sharing this information with Meta may be a "sharing" of personal information for cross-context behavioral advertising. Privacy choices and a Global Privacy Control signal turn it off, as described next.

You can opt out at any time with Privacy choices in our website footer or on this page. We treat a Global Privacy Control signal from your browser as an opt-out. Opting out stops Meta's pixel from loading in that browser, deletes the ad cookies from your browser (ob_oppref, ob_gclick and ob_fbclick, and Meta's _fbp and _fbc) and keeps a later signup from that browser from being reported to OpenAI, Google or Meta. When you are signed in, it also cancels your shop's reports that have not been sent, deletes the hashes, user agent, browser identifier and click references stored for your shop and stops future reports. It cannot recall a report already sent; contact support@ovenbell.com about data already shared. We remember your opt-out in that browser for one year in the ob_ads_optout cookie; if you clear your cookies, opt out again. Opting out does not affect your account or our own first-party analytics.

The native apps use AppsFlyer to measure installs and campaign attribution. Its SDK can process app/device identifiers, device and operating-system information, install and attribution information, including Android advertising identifiers where available. RevenueCat can associate subscription events with an AppsFlyer identifier and collect Apple's AdServices attribution token to measure Apple Search Ads. These services process data under their own policies and our configured integrations. Our app does not request access to the iOS advertising identifier through an App Tracking Transparency prompt. You can manage available advertising and privacy controls in your device settings; contact support@ovenbell.com with questions about attribution or a data request.

Our current public-site analytics integration does not change its behavior in response to the browser's Do Not Track signal. You can manage cookies in your browser and use Google's analytics opt-out tools. Blocking cookies or other storage can affect sign-in, carts and offline features.

All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

• How Google uses information from sites and apps
• Google Analytics opt-out browser add-on
• PostHog Privacy Policy
• AppsFlyer services privacy policy
• Meta Privacy Policy

8. Messages and your choices

Order confirmations, payment updates, replies and other messages needed to provide a requested service are distinct from promotional messages. A seller's email subscription applies to that seller. Use the unsubscribe or preference link in seller marketing messages to change that subscription; unsubscribing does not erase order records or stop necessary service messages.

Text alerts: if you enter a mobile number and tick the text box on a seller's storefront or product page, Ovenbell sends you recurring automated marketing texts announcing when that seller opens orders, at most one a day from each seller, or one marketing text when an item you asked about is back in stock. Texts come from Ovenbell's number. Order-opening and back-in-stock texts start with the seller's name and end with "Via Ovenbell"; the welcome and confirmation texts start with "Ovenbell text alerts". You get a welcome text when you sign up; if you signed up before text alerts started, we text you to confirm first and send alerts only after you reply Y. Message and data rates may apply. Reply UNSUB and the seller's keyword shown in order-opening texts (for example UNSUB MAYABAKES) to stop that seller's texts, HELP for help, or STOP to stop all Ovenbell texts; reply START to turn them back on. Text alerts are for US mobile numbers, and consent is not a condition of purchase. The program is described at ovenbell.com/text-alerts.

The seller is the business whose alerts you chose. Ovenbell does not give it your number: the seller sees that you signed up for texts and the last four digits of your number, and sees the full number only if you give it to that seller another way, for example with an order. Sellers cannot send their own texts through Ovenbell.

You can change available seller notification settings in the app and revoke push permission in your browser or device settings. For an Ovenbell news or resource subscription, use an unsubscribe option where offered or contact support@ovenbell.com to withdraw consent.

9. Retention, account deletion and privacy requests

Ovenbell keeps shop, customer, order, payment-reference, consent, message and draft records to operate the service and maintain business history. These records do not currently have a single automatic deletion period. Discarding an import can keep it available for recovery; it is not a request to erase its source material.

You can delete your account in the Ovenbell app (your account → Account settings → Delete account) or at ovenbell.com/delete-account. When you are the sole shop owner, deletion closes the shop, removes access through its private links, removes its photos, direct personal/contact details, customer descriptions, messages, subscriber list and other operational content, and then deletes your sign-in. Financial rows are kept with descriptive personal fields removed; amounts, dates, statuses, internal links between records and necessary payment-provider references remain for accounting, reconciliation and disputes. These retained references are not a promise that all records are irreversibly anonymous. If another owner remains, your membership and devices are removed and their shop continues to operate. If you answer the optional question about why you are leaving, we keep that answer, and whether you signed up on the web or in the app, with the closed shop’s retained records, without your name or contact details. Deletion also removes the shop’s Where to post area (its neighborhood and towns); the shared lists of places and public Facebook groups aren’t about any person and stay.

Deletion cancels a web-billed Ovenbell subscription before closing a sole-owner shop. Apple and Google subscriptions must be canceled in the relevant store; deleting your Ovenbell account does not cancel them. The deletion flow clears Ovenbell drafts, offline records, queued actions and cached pages on the device completing it. Other devices, downloaded or shared files, backups and records held by service providers follow separate processes. Previously collected analytics and attribution records are not erased merely by signing out or resetting a device identifier; contact support@ovenbell.com for a provider-data deletion request. We assess and coordinate those requests subject to required retention and provider processes.

If deletion is interrupted, the app may already have completed some steps. Retry to finish or contact support@ovenbell.com. For access, correction or deletion requests, include the account email and relevant shop or order, but do not send passwords or full card details. We may need to verify your identity and authority before acting.

We assess requests under applicable law and may retain information needed for legal obligations, accounting, disputes, fraud prevention or the rights of other people. Backups and service-provider records may follow separate retention processes. A seller may also need to handle your request for information in its own systems.

Depending on where you live and which law applies, you may have rights to access, correct, delete or obtain a copy of your information, withdraw consent, object to or restrict certain uses, or appeal a decision about a request. Contact us to exercise a right or appeal; you may also contact the relevant privacy authority. These statements do not imply that every privacy law applies to every Ovenbell user.

10. Security and processing locations

We use technical and organizational measures to protect the service, including authenticated seller access and encrypted connections. No service or transmission is completely secure. Keep your account and private links secure and tell support@ovenbell.com if you suspect unauthorized access.

Ovenbell is intended for businesses and customers in the United States. Our providers may process information in the United States and other countries. We do not promise that all records or AI processing remain in one country.

11. Children

Ovenbell is not directed to children under 13, and we do not knowingly collect their personal information. Seller accounts are for adults. If you believe a child under 13 has provided information, contact support@ovenbell.com so we can review and address it.

12. Changes and contact

We will post changes on this page and update the effective date. For material changes, we will provide additional notice where required, such as an in-app notice or email. A revised notice does not override consent or other protections required by applicable law.

Privacy requests and questions: Wild West Labs LLC, operator of Ovenbell, at support@ovenbell.com.