Privacy &
beta disclosures.

Baarish is a research beta for a future weather protection product. Here’s what this website does with your information.

What we collect

When you join the waitlist, we collect your name, email, business name, category, ZIP code, and your choice about product updates. If you join from the Explorer, we also save your selected illustrative coverage preferences and optional business opening year. These are not policy terms. We also record POS provider, pilot interest, and separate follow-up permission when you choose to share them. Manual revenue and contribution estimates remain in page memory unless you explicitly include them in an interest submission. Such optional research context includes generated options and your selected schedule.

The merchant questionnaire collects the business and weather-exposure answers you choose to share. Revenue ranges, estimated losses, budgets and other sensitive responses are optional. New survey responses require a business name and email address for merchant research. Providing an email does not subscribe you to marketing or beta promotions. Edited survey answers do not overwrite Explorer choices. You do not need to provide daily revenue records or connect a point-of-sale account.

Custom-quote contact requests collect your name, email, business name, ZIP code, desired annual protection amount, and any optional comments. These details are used for future contact, not to bind insurance or connect a POS account.

Locations and weather examples

An Astoria ZIP selection uses an approximate reference point. If address lookup is configured, your address query is sent to Mapbox for geocoding. No address lookup occurs when you use a supported ZIP code. We do not request your device’s location.

The Astoria reference-point model uses a user-supplied PRISM grid-cell export for 1991–2025 with public beta use confirmed. These are 4km grid-cell estimates, not storefront measurements. Insurance payouts remain hypothetical. Other locations require separately validated datasets.

How your information is used and stored

Research responses help us understand merchant needs. Waitlist information is used to manage early-access interest; optional product updates require your separate consent. Submissions are stored in Supabase with server-side access controls. Visitors cannot read other merchants’ submissions. We do not sell submissions.

Forms are disabled when storage is not configured. We never show a saved-registration message for a failed request. Hosting and database providers may process technical logs under their own policies.

Minimal analytics and abuse prevention

The beta uses temporary local interaction events for operational monitoring. Optional behavioral tracking is not enabled. No analytics vendor, tracking cookies or persistent visitor identifiers are used.

To limit automated submissions, the server derives a temporary keyed digest from a request’s network address. The abuse-prevention database stores the digest rather than the raw address. It is used for short-term rate limits, not marketing. Hosting infrastructure may retain its own request logs.

Your choices

You can leave optional research questions blank and decline product updates. This beta has no self-service data dashboard. Use the contact details in any direct research invitation or product-update message to ask the Baarish team about your submission or unsubscribe. A dedicated public privacy contact and a formal retention schedule must be established before broad public collection.

Research beta. No insurance for sale.

Baarish does not currently issue policies, collect premiums, or process claims. Coverage is not available for purchase. Displayed premiums and potential payouts are illustrative and subject to future underwriting approval. Historical performance would not guarantee future payouts. Actual coverage would require approved policy terms and a licensed insurance partner.

Illustrative insurance cash flow is separate from a business’s actual revenue and profit. Baarish intends to distribute through a licensed partner, rather than assume claims risk itself.

Before commercial launch

These notices are initial product information, not a completed legal compliance review. Counsel must review insurance marketing, privacy rights, retention, consent, approved data licensing, and policy disclosures before a public commercial launch. Live payment processing and insurance settlement are outside this beta.

Help shape the research →