WDS and 4070 Privacy Policy

Weather Decision Solutions, LLC. Effective date: September 23, 2026.

1. What this policy covers

This policy explains what personal information Weather Decision Solutions, LLC (“WDS,” “we,” or “us”) collects, how we use and disclose it, and your choices. It covers:

•Our shared weather platform and mobile applications, used by both 4070 consumer customers and WDS business customers. The same services may be accessed through different websites, domains, or branding.

•Partner forecaster memberships, content, and communities offered through the platform. A partner forecaster’s independently operated services may have their own privacy policies.

•Our public websites and the forms on them.

•The forecasts, reports, alerts, newsletters, proposals, account administration, and support we provide through these services, including services delivered to business customers outside the portal.

WDS operates these services; 4070 is our consumer brand. The WDS Platform License Agreement and your accepted plan or business proposal set the service terms. The way you access the platform does not change who operates it. Business organizations manage parts of their accounts. When we process personal information on an organization’s behalf, its documented instructions and any applicable data-processing agreement govern that processing. WDS is responsible for information we use for our own customer relationships, billing, security, and legal obligations. Contact us or your organization about the information each controls.

2. Information we collect

What you give us

•Account details. Your email address, display name, and sign-in credentials. Our authentication provider handles password verification; our application does not store your account password in a form our staff can read.

•Locations. The addresses, names, and map positions of the places you want weather for, and any notes you add about a site.

•Team and business contacts. Names, email addresses, roles, and any contact details you provide when adding team members, requesting a proposal, placing an order, or arranging support, including a business contact’s telephone number and signature.

•Messages and posts. Chat messages, replies, reactions, photos, videos and supported audio attachments, precipitation and storm reports, and questions you ask the weather assistant. Audio attachments may be transcribed to provide the requested feature.

•Weather station connections. The station identifier, location, and access credentials needed for a connection you enable. Depending on the integration, credentials may include an API key, access token, or the station provider account’s email address and password. Stored connection credentials are encrypted.

•Purchases. Billing and contact details, the services or reports you buy, payment status, and limited payment-method information needed for billing and support. Payment processors or the applicable store receive the payment credentials entered through their checkout; WDS does not receive the full payment card number through that checkout.

•Forms and email. What you enter in our contact, waitlist, demo, and report request forms, and anything you send to support.

What we collect automatically

•Sign-in and usage records. Sign-in times, device and browser information, and pages and features used. We also receive IP addresses in sign-in, security, and website request records.

•Device location. Only if you turn on Current Location. Section 4 explains how it works.

•Notification tokens. The device token that lets us send push notifications to your phone or browser, with the app version and platform.

•Errors and performance. If the app crashes or a page fails, we record what went wrong, which page you were on, and your device type.

•Analytics. Which features are used, recorded under a random identifier we assign to your account. Section 11 has the details.

What we receive from others

•Partner forecasters. If a partner forecaster brings an existing membership onto our platform, we receive the contact and subscription information needed to establish your access, such as your name, email address, and membership status.

•Payment and billing providers. Payment confirmations, subscription status, transaction records, and billing information needed to administer your purchase.

•Mapping services. The coordinates, county, and elevation for the addresses you enter.

•Weather data sources. Forecasts and observations from public agencies and other weather-data providers. The source weather information is generally not about you, but account-linked locations and records we combine with it may be personal information.

3. How we use information

•To give you forecasts, radar, outlooks, reports, and alerts for the locations you choose.

•To send the notifications you turn on.

•To run your account, sign you in, and bill you.

•To run chat, community features, and the weather assistant.

•To answer support requests.

•To keep the service secure, prevent abuse, and fix problems.

•To understand how features are used so we can improve them.

•To check our forecast accuracy over time by comparing past forecasts for your sites with what happened.

•To meet legal, tax, and accounting obligations.

•To send newsletters and product news with your consent or another lawful basis where required. Marketing messages include an unsubscribe method. Essential account, security, billing, and requested service messages may continue after you unsubscribe from marketing.

We do not sell personal information or disclose it for cross-context behavioral advertising or targeted advertising. We do disclose information to the recipients described in this policy to operate the services. We may also disclose information where reasonably necessary to comply with Law or valid legal process, prevent fraud, protect safety or rights, or establish or defend legal claims. If WDS undergoes a merger, acquisition, financing, or sale of assets, information may be disclosed to relevant advisers and parties subject to appropriate safeguards and continuing privacy obligations.

4. Location

Where you want weather

You choose your forecast locations by entering addresses or placing points on a map. We store those locations with your account so your forecasts, alerts, and reports work. Business accounts can also store routes and multi-point sites.

Where your device is

•Current Location is off unless you turn it on. When it is on, the app asks your phone or browser for its position while you are using the app and sends those coordinates to WDS to fetch weather and alerts for where you are.

•We use device coordinates for location-based requests and do not maintain a separate location-history feature. Coordinates may also appear in request or diagnostic logs. Those records follow the retention periods described in section 12.

•We receive your IP address in technical records and share it with providers when your device contacts their services. Some providers may infer an approximate location from it, including for analytics or security.

•Your device may retain the latest location to support local weather features, including supported widgets.

•The mobile apps do not request continuous background location tracking. You can turn device-location features off through account controls or your device’s location permissions.

5. Alerts and notifications

•You can choose among the notification options available to your plan, device, and delivery channel, including chat updates, weather alerts, watches and warnings, storm summaries, and video briefings.

•To send them we store a push token for each device or browser you enable, with the app version and platform, so we know how to reach it.

•We record sending attempts and delivery status available from our providers to help check whether alerts are working. A successful send does not establish that a person received or read it.

•Notification settings control the selected category or channel. Disabling device notifications stops presentation on that device; separately subscribed email notices have their own controls. Push tokens may remain in our records until they are removed through account controls, account deletion, or delivery-failure cleanup.

6. Messages, posts, and who can see them

Chat in a workspace

•Workspace chat is visible to members with access to that workspace, company administrators, and WDS staff supporting it. In a partner forecaster workspace, the partner forecaster can also read the shared chat. Your display name appears with your messages. Business administrators can manage member names, email addresses, roles, and workspace access.

•Assistant conversations are separate from workspace chat and are not available to other members, company administrators, or partner forecasters through their accounts. WDS personnel and service providers may process them to operate, support, and secure the service. Section 7 explains this processing and how suggestions sent through the assistant can reach WDS staff.

•Deleting a message removes its text from the conversation and schedules its associated attachment files for deletion. A deletion notice, with the sender’s name and time, may remain. Restricted file recovery copies and separately retained support records follow section 12. Copies independently saved by other people are outside our deletion controls.

Community

•Community posts, comments, and reactions are visible to members who can access that community, with the display name and profile information shown by the feature. Poll results are presented as totals; we retain individual vote records so people can change their votes. Removing a post from view does not necessarily erase all stored copies.

•For supported photos and videos uploaded through our chat, community, and profile tools, we remove embedded camera metadata, including recorded capture time and location, before storage. This does not remove identifying details visible or audible in the content. Do not include information in an upload that you do not intend its audience to see.

Reports you submit

•Precipitation and storm reports you submit show your name to other members of your workspace and to the partner forecaster or WDS staff who review them. We keep your email address with the report so we can follow up.

Profile photo

•If you add a profile photo, it may appear next to your name to other users who can see your profile, messages, or posts.

Shared images and reports

•Shareable radar and forecast images may include the location or site name shown on screen. Reports may include site addresses and customer-supplied information. Some report links allow anyone who has the link to view the report; a recipient may save or forward the content. Your choice to share a report does not give other people access to your account.

7. The weather assistant

•The weather assistant processes your questions, relevant prior conversation or saved context, and weather and operational information available within your account’s access permissions. Assistant histories are kept separately from workspace chat. Section 12 describes retention. The assistant may automatically copy relevant suggestions, message excerpts, and your name and account contact details to WDS support records and internal staff discussions for follow-up. These automatic copies follow the retention rules in section 12.

•We use commercial AI service providers to generate assistant replies and other requested outputs, such as written report summaries. We send them the prompts, content, and relevant context needed for that task. We do not authorize them to use our customer inputs to train their general-purpose models. They may retain or review information for permitted operational, security, abuse-prevention, or legal purposes under the applicable service terms; a restriction on training does not mean zero retention.

•The assistant may maintain a summary of relevant weather and operational context to support follow-up conversations. Conversation-derived information in that summary follows the same 30-day retention period as assistant messages; carrying it into a later summary does not restart that period. Clearing a conversation removes its associated summary. Locations and preferences you separately save as account settings follow the account-information rules in section 12.

•WDS does not use your messages or questions to train AI models.

•Answers can be wrong. Check anything important against the forecast pages and official warnings.

8. Partner forecaster memberships

Partner forecasters are independent forecasters or forecasting businesses that publish through our platform. If you choose a partner forecaster membership:

•The partner forecaster can see membership details such as your name, email address, join date, subscription status, and activity indicators, including recent sign-in or use. The partner forecaster may export subscriber records, read the membership workspace’s shared chat, send membership communications, help with password-reset requests, and manage access. The partner forecaster cannot open your private assistant history through their account.

•We provide your membership and contact details to the partner forecaster whose membership you choose, to administer that membership.

•Partner forecasters do not receive full payment card details from WDS. For subscriptions purchased directly from WDS, WDS manages billing through its payment providers and pays the partner forecaster its share. An existing membership may remain billed by the partner forecaster under its own arrangement. If an app store processes a purchase, its billing and privacy terms apply to that processing.

•A partner forecaster is a separate business. Its independent websites, direct communications, and other services may have their own privacy policies and responsibilities. Contact WDS about our disclosures or platform controls and the partner forecaster about its independent handling of information.

9. Payments

•Payment processors handle purchases made through our checkout. WDS keeps customer and subscription identifiers, what you bought, amounts, tax, payment status, and limited billing information to administer purchases and provide support. Business billing follows the accepted proposal or order. If an app store or partner forecaster bills a purchase, that seller or provider handles information under its own terms.

•A receipt or billing record may include the site name or address covered by a purchase.

•The applicable seller and payment provider are identified in the purchase or billing process. Their privacy notices apply to information they process for their own purposes.

10. Service providers and other recipients

We disclose information to providers for the functions below. A provider receives information relevant to the work it performs for us; it does not receive every category simply because it is listed here. Some providers, including payment, mapping, and app-store providers, also process information for their own purposes under their privacy notices.

•Hosting and account services. Host databases, files, and application systems, authenticate users, and operate the service. They process the account, content, location, and technical information stored or transmitted through those systems.

•Payments and business administration. Process payments, subscriptions, tax, and partner forecaster payouts, and support accounting, customer administration, and preparation or storage of business deliverables. They receive the relevant transaction, contact, agreement, or deliverable information.

•Communications and app delivery. Deliver account emails, newsletters, membership messages, notifications, app downloads, and updates. They process recipients, message content, device or push identifiers, app and device information, and delivery records as needed for that function.

•AI processing. Generate assistant replies, summaries, and other requested outputs using the prompts, content, and relevant context described in section 7.

•Mapping and location lookup. Provide maps, imagery, address lookup, and related location details. Requests can disclose an IP address, device or browser information, the map area viewed, and the address or coordinates used for the request.

•Weather and media delivery. Supply weather data, distribute radar or other imagery, and host live or recorded media. Requests can disclose coordinates, the area or content requested, an IP address, and technical request information. We do not include your name or account contact details in external forecast-data requests.

•Analytics and reliability. Measure visits and feature use and help diagnose performance or errors. They receive usage events, account-linked or device identifiers, and technical information as described in section 11.

•Security and fraud prevention. Help prevent spam, protect forms and accounts, and investigate abuse. They process relevant IP addresses, device and request information, interaction signals, and security records.

Other users, business administrators, and partner forecasters receive information within the access and membership arrangements described in sections 6 and 8. Section 3 describes legal, safety, and business-transaction disclosures. Providers performing the functions above can change. Contact us for further information about recipients; any additional notice, consent, or contractual notification required for a change still applies.

11. Cookies and analytics

Cookies we set

•Authentication and security storage keeps you signed in and protects your account. Blocking essential storage can prevent the service from working.

•Temporary profile caches help pages load reliably during brief service interruptions.

•Preference storage remembers selections such as your last view or dashboard tab.

•Analytics cookies and similar identifiers measure usage as described below. Blocking optional analytics storage may reduce measurement.

Storage on your device

We save preferences such as map layers, unit choices, saved views, and your last viewed location on your device so the app opens where you left off. The mobile app stores your sign-in token in your phone’s secure storage.

Analytics

•Our websites and web platform use Google Analytics to measure visits, page and feature use, and checkout steps. It uses cookies and event and device information, and may derive approximate location from an IP address. Google describes its processing at https://policies.google.com/technologies/partner-sites. The service providers described in section 10 may collect information directly when your browser or device contacts them; their notices explain any collection across other sites or services.

•For signed-in web analytics, we use a random account-linked identifier rather than deliberately sending your name or email address as an analytics identifier. This is pseudonymous information, because WDS can connect it to your account.

•We also record web and mobile feature use, errors, and performance in our own operational logs to troubleshoot problems and improve reliability.

•Our sites do not respond to the older browser Do Not Track setting. That setting is different from legally recognized opt-out preference signals such as Global Privacy Control, which we will honor where applicable law requires. You can manage storage through your browser or device and use Google’s Analytics opt-out tool at https://tools.google.com/dlpage/gaoptout. We will seek consent before using a cookie or similar technology where consent is legally required.

12. How long we keep information

We retain personal information for the periods or purposes below, only for as long as reasonably necessary and proportionate to those purposes. Where a fixed period is not specified, the criteria below determine retention. Legal requirements and applicable business-customer instructions may require particular records to be retained; they do not justify keeping unrelated personal information indefinitely.

•Account and team information. We keep it while needed to provide the account and complete related business purposes. Our account-deletion process is designed to remove or de-identify personal account data within 30 days of a verified request, subject to the exceptions described here. An individual’s departure does not erase the business workspace’s shared records or end the organization’s service agreement.

•Chat and assistant information. Our standard retention period is 30 days for workspace chat and assistant message history, associated attachments, conversation-derived assistant memory, and automatic assistant follow-up copies. We remove this information through scheduled cleanup. Copying conversation-derived information into a newer summary or automatic follow-up record does not restart its retention period. Separately opened support cases follow the rule below. Specific records may be retained longer only where necessary for a documented legal, security, or dispute-related reason. Copies independently saved by other people are outside our deletion controls.

•File recovery copies. When an uploaded file is deleted or replaced, a restricted recovery copy may remain for up to seven additional days after removal from active storage. These recovery copies are not available through the service and expire automatically. This recovery period also applies to older file versions replaced when embedded camera metadata is removed.

•Community content. Posts and comments generally remain until removed by you or a moderator or addressed through a deletion request. Removal may first hide content from users while stored copies, vote records, reactions, or moderation records remain. We assess retained personal information under the request and retention rules in this policy.

•Sign-in and security records. Routine sign-in attempt records are scheduled for deletion after 30 days. Other account-security and administration records may be retained longer to investigate abuse, document access changes, or address legal claims.

•Push tokens. While needed for enabled delivery or until removed through account deletion or delivery-failure cleanup. Turning off a device’s notification permission does not necessarily erase the token from our records.

•Newsletter and delivery records. We retain records needed to troubleshoot delivery, document communications, and honor preferences. We retain enough information about an unsubscribe to prevent further unwanted marketing, even after an account closes. This does not mean we need to retain every newsletter or delivery event permanently.

•Weather station readings. Historical readings can remain in our weather archive after a station is disconnected. Disconnection stops the integration’s future collection and removes the station from the shared views controlled by that connection. Account-linked station records remain subject to applicable privacy requests and retention limits.

•Historical forecasts and site records. Our weather archive retains past forecasts, associated site names and addresses, and observations for long-term verification and accuracy analysis, rather than deleting them automatically when an individual account closes. Where these records identify an individual, requests to delete or de-identify them are assessed under applicable Law and any business-customer instructions. Historical forecast and site records may be retained for as long as reasonably necessary for forecast verification, legal obligations, or business-customer requirements, with personal information deleted or de-identified when no longer necessary.

•Purchase and agreement records. We retain billing, tax, transaction, proposal, and acceptance records for the periods needed for accounting, applicable legal requirements, and disputes. The appropriate period depends on the record and obligation. A business customer’s agreement, invoice, transaction record, or other record that must be retained for accounting, legal, contractual, security, or dispute-related purposes may be retained for the period reasonably necessary for that purpose. Retaining such a record does not require WDS to retain unrelated messages, files, assistant conversations, or other personal information beyond the retention periods stated above.

•Logs and security records. Routine cloud application logs are generally kept for 30 days. Other security and administrative records may be retained longer where necessary to investigate abuse, document access changes, or meet legal obligations.

•Support cases. We retain the personal information needed to handle a separately opened support case while it is being resolved and delete it within 30 days after the case is first resolved. This includes related correspondence, excerpts, and attachments in our support records and internal follow-up copies. Selected records may be retained longer where necessary for a documented legal, security, dispute-related, or business-record obligation. That exception does not extend to unrelated conversation content. Account-deletion requests also cover support records; we assess any necessary exception when handling the request.

•Deletion records. We keep a limited record of a deletion request and its outcome for 90 days after completion. Where a request remains unresolved or particular records must be retained, we keep the limited information needed to complete the request or manage that retention, with a documented reason and review date.

•Analytics. We configure Google Analytics with two-month retention periods for user-level and event-level data, followed by Google’s scheduled deletion. New activity does not restart the user-data retention period. Standard aggregate reports may remain longer. Our account-deletion process also requests deletion of Analytics data associated with the account’s analytics identifier.

•Reports and other retained copies. You may keep a report you lawfully obtained, subject to your service terms. Report access follows the terms supplied with the report. We may retain records needed to comply with Law, resolve disputes, enforce agreements, or carry out business-customer instructions. Copies others have independently saved are outside our deletion controls. If we retain personal information after a deletion request, we will explain the applicable reason when required by Law.

13. Security

•We use encrypted connections and access controls to protect information. WDS staff and service providers may access information as needed for their authorized work. No system or access control can guarantee that unauthorized access will never occur.

•We use role-based access controls and maintain security and administrative records. Those controls differ by service and function.

•Weather station connection credentials are encrypted in storage and can be decrypted by systems that need them to collect station data. Account password verification is handled by our authentication provider.

•No system is perfectly secure. If a security incident affects your information, we will tell you as the law requires.

14. Your choices and requests

Account and device controls

•Change your name, photo, locations, and notification choices.

•Manage or cancel a subscription using the billing controls for the seller that charges you. Cancellation generally stops the next renewal; it is separate from a privacy deletion request.

•Turn Current Location on or off.

•Use the available communication settings and the unsubscribe mechanism in marketing messages to change your preferences. Essential account, security, and service messages may continue as described in section 3.

Deleting your account

•Where available in your version of the service, open Settings, choose Delete account, and follow the confirmation steps. You can also request deletion at info@weatherdecisionsolutions.com. We may verify your identity before processing the request. Account access is disabled as part of this process; deletion and any retained records follow section 12. If you are the only administrator of a business workspace, arrange another administrator or contact us for help first. Canceling a subscription or uninstalling the app does not delete your account. Uninstalling the app also does not cancel a subscription; manage the subscription with the provider that bills you.

•A business administrator can manage or remove your workspace access. That action is not necessarily a request to delete all your personal information from WDS or the business’s records. Contact us for a privacy request; we may coordinate with the business where it controls the relevant records.

Access, copies, and corrections

•Depending on applicable Law, you may request access to or a copy of your personal information, correction, or deletion; withdraw consent where processing depends on consent; or exercise other privacy rights available to you. Email info@weatherdecisionsolutions.com. We may need to verify your identity or an authorized agent’s authority. We will respond within the time required by applicable law. By way of illustration, covered California requests generally require a response within 45 calendar days, while PIPEDA access requests generally require a response within 30 days, subject to applicable extensions. We will explain a refusal and any available appeal or complaint process. You may contact the privacy regulator where you live. We will not unlawfully discriminate against you for exercising a privacy right.

•California residents have rights under the CCPA where it applies, including knowing the categories and specific personal information collected, its sources and purposes, and the categories of recipients; correcting or deleting information; and opting out of sale or sharing. Applicable Law may also provide rights to limit certain uses of sensitive information or opt out of targeted advertising or specified profiling. We do not sell information or share it for cross-context behavioral advertising. We use precise location and account credentials for requested services, security, and other permitted purposes, not to infer sensitive characteristics for advertising. Business contacts and employees using a business account do not lose applicable privacy rights because their account is commercial.

•Depending on where you live and the circumstances of our processing, you may have additional privacy rights under applicable state privacy laws. These rights may include rights to access, correct, delete, obtain a copy of, or restrict certain uses of personal information, and to opt out of certain sales, sharing, targeted advertising, or profiling. We do not deny applicable privacy rights to business users, employees, or business contacts solely because they use our services in a business capacity.

15. Children

Accounts and paid services are intended for adults who are at least 18 and have reached the age of majority where they live. We do not knowingly maintain accounts for children. If you believe a child has supplied personal information without appropriate authorization, contact us so we can review and delete it where required.

16. Where we process information

WDS is based in California and primarily uses infrastructure in the United States. Our providers may process, route, or store information in other countries, including for distributed hosting, content delivery, and AI processing. Information transferred across borders may be accessible to courts, law enforcement, or other authorities under the destination country’s laws. We use contractual and other safeguards required by applicable law. Contact us about providers and international processing.

17. Changes to this policy

We review this policy and update it when needed to reflect our information practices or legal requirements. We will post changes with a new effective date and give notice of significant changes through the service or by email before they take effect. If applicable law requires consent to a new use or disclosure, we will obtain that consent; posting an updated policy alone is not that consent.

18. Contact

Weather Decision Solutions, LLC

455 Market St Suite 1940 – 845266, San Francisco, CA 94105

info@weatherdecisionsolutions.com

For privacy questions, complaints, and requests, contact WDS at the address or email above, attention Privacy Contact. Copyright complaints follow the procedure in the Platform License Agreement.