Privacy policy

Last updated October 4, 2026

Veabird is owned and operated by Alex Houck Consulting, LLC.

Veabird (veabird.com) publishes free weather, beach and snow forecasts. You can use the whole site without an account, and we don't ask for your name, email or payment details.

What we collect

• Anonymous visit counts. We use GoatCounter, a privacy-friendly analytics service that doesn't use cookies or track you across sites. It records pages viewed, the referring site, browser type and country, plus clicks on partner links so we know which partners are useful.
• Settings in your browser. The site stores things like your last viewed resort and cached photos in your browser's local storage. This stays on your device and you can clear it at any time.
• Messages you send us. The contact form sends your name, email and message to us through Formspree, a form-delivery service. We use them only to reply and keep them no longer than needed.
• Concierge requests. The Veabird Concierge form sends what you type (name, email, trip details and, if you came from Vea, the questions you asked her) to us through Formspree. We use it only to plan your trip and reply, and keep it no longer than needed.
• Your approximate city. To suggest trips that fit where you are, the home page asks our server for the city our hosting provider, Cloudflare, estimates from your IP address, then checks that city's weather forecast with Open-Meteo. We don't store or log it. You can pick a different city or turn this off with the "change" link on the "Worth the trip" ticker; that choice stays in your browser's local storage.
• Searches. What you type into the search bar at the top of our pages goes to our server and to TypeSafe, the AI service that works out what you're looking for, along with the city Cloudflare estimates from your IP address (so a flight search can start from a nearby airport). We keep a log of searches for three months to improve the site and see what people want that we don't offer yet: the words you typed, what we matched, which result you clicked and your country. We don't log your IP address or anything that identifies you, so please don't type personal details into the search bar. If a search is a question, it may also be sent to the AI provider behind our "ask" feature, below.
• Book-direct links. When you click a link to a local rental manager's own site (it goes through veabird.com/go/), we count the click so we can tell the manager how many visitors we sent: which home, where on Veabird (or which AI assistant) the link was shown, your country and the site you came from. We don't log your IP address. The link adds "utm" tags so the manager's own analytics see the visit came from Veabird.
• Questions you ask. If you use an "ask" feature, your question is sent to our server and to the AI provider that answers it. We don't attach your identity to it.
• Ask Veabird (the trip chat on our pages). What you type in the chat, earlier messages in the same conversation and the title of the page you're on go to our server. A quick lookup (one place's snow or beach forecast, or two places compared) is answered from our own forecasts: the question goes to TypeSafe's Jev model, or Cloudflare's Workers AI, only to sort what kind of question it is. Anything else goes to Meta's Muse Spark AI model (Meta Model API) to write the answer. We use the Muse Spark "Contributor" service, under which Meta may use prompts and answers to improve its products, so please don't put names, contact details or other personal information in the chat. We keep a three-month log of the questions typed into the chat (the words, the page you were on, whether it came from the search bar or a suggested question, and your country) to improve the answers, without your IP address or anything that identifies you; we don't keep the answers or tie a conversation to you. Each browser gets five of those Muse Spark questions a day, so the first time you ask, our server sets a cookie named "vea" (a random id, sent only to our chat endpoint, kept for a year) and counts that day's questions under it and under a one-way hash of your IP address that changes every day, so the address itself is never stored. The counts hold nothing else, aren't linked to the question log, and are deleted after two days. Your browser holds the conversation in session storage until you close the tab or start a new chat. To decide when to offer our mailing list, your browser also counts, in local storage on your device only, the days you've visited, pages and chats, and which sections you read; it isn't sent to us. Places, dates and party details from the chat are used to look up conditions, lodging (through LiteAPI) and flight searches, as described below.
• "Keep an eye on it" emails. If you ask Vea to watch a beach or ski resort, we store your email address, that place and when you asked, and email you only after you confirm by email. Each watch ends after 60 days, and every email has a one-click link to stop it, which deletes it. Your browser remembers the address you used, in local storage on your device, to fill it in next time.
• "Tell me when it's clear" emails. If you sign up on a beach page, we store your email address, that beach or region, when you signed up and when we last emailed you about each beach. We email you only after you confirm by email, at most once a week per beach, through our email provider (Cloudflare or Resend). Unconfirmed sign-ups are deleted after seven days. Every email has a one-click unsubscribe, which deletes that alert, and a link to see and stop all of yours. Your browser remembers the address you used, in local storage on your device, to fill it in next time.
• Mailing list. If you join, we store your email address and the topics you picked, and use them only to email you about those topics after you confirm by email. Every email has a one-click unsubscribe, which deletes your address.
• AI assistants and our API. When you use Veabird through an AI assistant such as ChatGPT or Claude (our connector at veabird.com/mcp) or through our API (veabird.com/api/v1), we receive only what the assistant sends to our tools: places, travel dates, your home airport or city, party size, children's ages, ability level, pass and budget. We never see your conversation, name or account. We use those details only to answer that request. They pass through our hosting provider's short-lived request logs, which we use for security and debugging, and we don't build profiles from them. For lodging prices, the destination, dates and party size are sent to our hotel-rate provider, LiteAPI. Your assistant's own privacy policy covers what it does with your chats.
• Hotel prices on resort pages and Veabird Snow. When a resort page shows a live price for its hotel, or Veabird Snow lists places to stay at a ski resort, your browser asks our server for prices with the hotel or resort, your dates and the number of guests. Our server passes those to our hotel-rate provider, LiteAPI, along with the country Cloudflare estimates from your IP address (rates and taxes depend on it). We don't store any of it beyond a few hours of cached prices, which aren't linked to you. Your nights and guests choice stays in your browser's local storage.
• Rental demand checks (veabird.com/hosts). When you check a property, the location, the calendar (iCal) link and the nightly rate you enter are sent to our server, which reads the calendar once to see which nights are booked and then discards it. We look up the town's coordinates with Open-Meteo's geocoding service. Guest names in the calendar are never read into the result. Nothing is stored unless you sign up for email alerts.
• Host email alerts. If you sign up, we store your email address, the property's location, its calendar link and the rate you entered, so we can check the property every week and email you. We send the emails through our email provider (Cloudflare or Resend). Unconfirmed sign-ups are deleted after seven days; unsubscribing (a link in every email) deletes everything we hold for that property right away.

Partner links and cookies

Some links go to travel partners such as Booking.com, Expedia, Vrbo and tour or insurance providers, through affiliate networks including Stay22, CJ Affiliate and Impact. When you click one, the partner or network may set cookies to credit Veabird for a booking. Their use of data is covered by their own privacy policies. "See rooms & book" buttons on resort pages open Veabird's hotel booking site, run for us by LiteAPI (Nuitée). Anything you enter there to book, such as your name, contact and payment details, goes to LiteAPI and the hotel under that site's own terms and privacy policy, not to this site. See our affiliate disclosure.

Third-party content

Forecast data loads from public sources (for example Open-Meteo, NOAA and USGS), and photos may load from Wikimedia Commons or hotel content providers. Those services receive standard web request information, such as your IP address, when your browser loads their content.

We don't sell data

We don't sell or rent personal information, and we don't run behavioral ad tracking.

Children

Veabird isn't directed at children under 13 and doesn't knowingly collect their information.

Your rights

You can ask us to access, correct or delete personal information you've sent us (for example, a contact form message). Use the contact form with the topic "Privacy request".

See also our cookie policy and terms of use.

Changes and contact

We'll update this page if our practices change. Questions: hello@veabird.com.