Privacy Policy

Information we collect

• Information you provide: names, email addresses, phone numbers, market or city, professional background, and messages submitted through our forms or sent to us.
• Studio account and broadcast information: login identifiers, show titles, descriptions, artwork, broadcast identifiers, selected destinations, settings, and live status.
• Connected social accounts: when you authorize YouTube or Facebook, we receive account or channel identifiers, display names, authorization tokens, and the broadcast information needed for the features you use. You enter your Google or Facebook password with that platform, not with Weather.Watch.
• Audience interactions: live comments, commenter display names or identifiers, and timestamps returned by connected platforms. Authorized studio users can view these comments in the live studio.
• Website usage and device information: hosting and analytics services may process IP addresses, browser and device details, referring pages, page visits, and technical logs. If you choose a city or allow browser location access for weather features, that information may be used to show local weather.

How we use information

We use information to operate the website, display weather and video coverage, respond to inquiries, manage authorized studio access, prepare and publish broadcasts you request, show broadcast status and audience comments, troubleshoot problems, protect the service, and understand website usage.

Connecting a social account authorizes only the features and permissions presented during that platform’s consent process. Broadcast titles, descriptions, artwork, audio, and video are sent to the destinations you select. Their visibility depends on your publishing settings and the platform’s rules.

YouTube and Google data

Our studios use YouTube API Services to connect an authorized channel, create and manage livestreams, set broadcast details and thumbnails, check streaming status, and display live chat. Google account data obtained through these APIs is used for these user-facing features, not to build advertising profiles or sell to data brokers.

Weather.Watch’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. YouTube features are also subject to the YouTube Terms of Service and Google Privacy Policy.

You can revoke Weather.Watch’s access through your Google account connections settings. Revoking access prevents future authorized access; contact us below to request deletion of information already stored by Weather.Watch.

Facebook and Meta data

When you connect Facebook, we use the authorized profile or selected Page information and access token to create and end broadcasts you request, check their status, and retrieve available live comments. When you connect a Page, we list Pages you are authorized to manage so you can select the broadcast destination. Meta controls which information is available based on permissions, account eligibility, and broadcast privacy settings.

You can review or remove the connection in Facebook’s Apps and Websites settings, or Business Integrations where applicable. Facebook also processes information under the Meta Privacy Policy.

Service providers and sharing

We use providers including Vercel for hosting and storage, Cloudflare for streaming and delivery, Google/YouTube and Meta for connected social features, analytics providers, and services that support email and commerce. These providers receive information needed to perform their functions. Embedded videos, maps, fonts, and social tools may send device and usage information directly to their providers when loaded or used.

Authorized Weather.Watch operators may access information needed to support the service. Social credentials are scoped to authorized studios; Gary and Jeff share the Lezak Weather social connections. We may disclose information where required by law, to protect rights and security, or as part of a business transfer subject to applicable privacy obligations.

Cookies, analytics, and browser storage

We use cookies for admin sessions and social connection security, and browser storage for preferences such as comment text size. The site uses Google Analytics and Vercel Web Analytics to understand usage. Third-party players and other embedded services may use their own cookies or similar technologies.

You can manage cookies and site storage through your browser settings. Blocking them may affect login, embedded playback, or other features. Google provides a Google Analytics opt-out browser add-on.

Storage, security, and retention

Social authorization credentials are encrypted in private backend storage. Access controls separate studio connections and settings. No system is completely secure.

We retain account connections and saved broadcast settings while needed to provide the service, unless you request deletion or applicable requirements call for earlier removal. Comment snapshots may be cached to limit platform requests. Other information may be retained as needed for support, security, legal obligations, and resolving disputes. Removing a connection does not automatically delete a video already published on YouTube or Facebook.

Website live chat

When you join live chat, we send a verification code to your email through our email provider. Your display name and approved messages are public on the show’s chat widget and available to authorized studio moderators. Your email is not displayed. The chat service stores verification records and hashed identifiers for rate limits and moderation. Verified email addresses are encrypted in private multistream user records, grouped by studio. The site owner can view these addresses to support chat access and data requests. Signing in is not consent to marketing emails. Email addresses are never included in public chat messages.

Chat sign-in lasts up to 12 hours in browser session storage. Codes expire after 10 minutes. A language and spam filter may hold messages for moderator review; it is not guaranteed to detect all abusive content. Moderators can approve or delete messages, mute viewers for 15 minutes, or block them for 30 days. Current room history is bounded and is replaced as later studio broadcasts receive messages. Verification and anti-abuse records may remain in private storage after their validity expires. Contact us using the deletion instructions below to request removal.

The same studio room can appear on weather.watch and lezakweather.com. The widget is served by Weather.Watch and only shares public display names and approved messages with viewers.

Request access or delete your data

1. Email stephen@weather.watch with the subject “Weather.Watch data deletion request.”
2. Include your studio or account email, the connected platform, and the channel or profile name. Tell us whether you want to remove a social connection, your studio information, or other personal information. Do not send passwords, access tokens, or stream keys.
3. We may verify that the account belongs to you before acting. We will review your request and remove the associated information we control, subject to applicable retention obligations, and confirm the outcome.

You may also request access to or correction of information we hold, and exercise other privacy rights available where you live, using the same contact address. To delete content stored by YouTube or Facebook, use that platform’s own controls or privacy request process.

Children and international processing

Our studio accounts and business services are intended for adults. If you believe a child has supplied personal information to us, contact us to request review and removal. Our providers may process information in the United States and other countries where they operate.

Changes and contact

We may update this policy as our services change. The effective date above identifies the latest version. Questions about this policy can be sent to stephen@weather.watch.