Privacy Policy
Last updated 2026-05-07info@swatgenx.com
Plain-language summary
We collect account, usage, and technical data to run SWATGenX, keep it secure, and deliver the outputs you request. We use vendors as processors, do not sell your personal information, and retain data only as long as needed for the service or law. The sections below spell this out in full legal form.
This policy describes how SWATGenX (the operator of this website and platform, reachable at the contact above) collects, uses, stores, and shares information when you use our hydrologic and watershed-screening analytics services, including accounts, workspaces, reports, and related workflows.
Authentication providers (including Google / OAuth). If you sign in with a third-party identity provider (for example Google), we receive information that provider shares with us, typically including a stable provider user identifier and email address, and we may store which provider you used. We use that data to authenticate you and maintain your account. The provider’s own privacy policy also applies to their processing.
Optional API access keys. If you create an API key in your account (for example from the subscription area), we store a cryptographic hash of that key, an optional label you provide, creation time, and coarse last-used timestamps so you can manage and revoke keys. We do not store the full secret after it is first shown to you.
Usage and product telemetry. We collect information about how the Service is used so we can operate, secure, and improve it. Examples include page or route visits, workspace or project opens, model or report orders and their outcomes (e.g. start, success, failure), feature usage, and—where available—administrative or editorial actions for platform operators. If we offer periodic digests or similar notifications, we may log delivery-related events (for example sends, opens, or clicks) at a level sufficient to measure engagement and troubleshoot delivery.
Technical and security data. Our servers and infrastructure may log IP addresses, request timestamps, URLs, HTTP status, device or browser type (when transmitted), session identifiers, and security-relevant events (such as failed logins or suspected abuse). We may use this information for security, abuse prevention, debugging, and capacity planning. IP addresses and similar online identifiers may be treated as personal information where applicable law defines them that way.
Generated content and history. The Service stores content you generate or request, such as saved reports, downloaded or generated model packages, configuration choices, map selections, watershed or station selections, and—where the product includes them—analytical briefs or feeds you save, view, or manage. Historical records may be retained to restore your workspace, fulfill orders, comply with law, or resolve disputes.
Communications. We process email addresses and message content needed to send account verification, password reset, transactional notices (for example model job status, queue updates, or support-related messages), and—if you opt in or if a feature is offered to you—product digests or newsletters. Marketing email, where used, will include a way to unsubscribe; transactional messages may continue as needed to operate your account.
Analytical product; not an emergency service
SWATGenX provides analytical intelligence tools (maps, models, reports, and related outputs). It is not an official warning service, regulatory determination tool, or emergency-response guidance system. Map layers and public datasets used in the product remain governed by their stewards—follow each source’s citation and attribution requirements in publications. Example steward links (not exhaustive): PRISM climate data (Oregon State), NSRDB, USGS NHDPlus HR, USGS NWIS, NLCD, gSSURGO.Information we collect
Account and profile. When you register or maintain an account, we may collect identifiers such as email address, username or display name, password hash (for password-based accounts), account status, and timestamps related to sign-in and account updates.Authentication providers (including Google / OAuth). If you sign in with a third-party identity provider (for example Google), we receive information that provider shares with us, typically including a stable provider user identifier and email address, and we may store which provider you used. We use that data to authenticate you and maintain your account. The provider’s own privacy policy also applies to their processing.
Optional API access keys. If you create an API key in your account (for example from the subscription area), we store a cryptographic hash of that key, an optional label you provide, creation time, and coarse last-used timestamps so you can manage and revoke keys. We do not store the full secret after it is first shown to you.
Usage and product telemetry. We collect information about how the Service is used so we can operate, secure, and improve it. Examples include page or route visits, workspace or project opens, model or report orders and their outcomes (e.g. start, success, failure), feature usage, and—where available—administrative or editorial actions for platform operators. If we offer periodic digests or similar notifications, we may log delivery-related events (for example sends, opens, or clicks) at a level sufficient to measure engagement and troubleshoot delivery.
Technical and security data. Our servers and infrastructure may log IP addresses, request timestamps, URLs, HTTP status, device or browser type (when transmitted), session identifiers, and security-relevant events (such as failed logins or suspected abuse). We may use this information for security, abuse prevention, debugging, and capacity planning. IP addresses and similar online identifiers may be treated as personal information where applicable law defines them that way.
Generated content and history. The Service stores content you generate or request, such as saved reports, downloaded or generated model packages, configuration choices, map selections, watershed or station selections, and—where the product includes them—analytical briefs or feeds you save, view, or manage. Historical records may be retained to restore your workspace, fulfill orders, comply with law, or resolve disputes.
Communications. We process email addresses and message content needed to send account verification, password reset, transactional notices (for example model job status, queue updates, or support-related messages), and—if you opt in or if a feature is offered to you—product digests or newsletters. Marketing email, where used, will include a way to unsubscribe; transactional messages may continue as needed to operate your account.
How we use information
We use the information above to:- Provide, operate, and improve the Service
- Authenticate users, enforce access tiers, quotas, and premium entitlements
- Process and deliver reports, models, and other outputs you request
- Maintain security, detect abuse, and protect the platform
- Communicate with you about the Service and, where permitted, product updates
- Meet legal obligations and respond to lawful requests