Open Data & API Use
AlaskaTides.app is built on top of public data sources and aims to support responsible reuse of that data while protecting the Service from abuse. This page explains what you may reuse, what is protected, and how we think about future API access.
Public data from upstream providers
Many underlying tide and water‑level data products come from U.S. government agencies such as NOAA. In general, these data are public domain and may be reused under the terms and guidelines of the original providers. When you need authoritative data, we encourage you to retrieve it directly from the provider (for example, via official NOAA websites and APIs).
What you may reuse
Subject to the terms of upstream providers, you may:
- Use AlaskaTides.app’s tide predictions and tables for personal, educational, or research use.
- Save or print pages or charts for your own planning and record‑keeping.
- Reference AlaskaTides.app as one of several information sources when discussing tides or planning trips.
What is protected
While upstream data may be public, the AlaskaTides.app service itself (including its code, compiled datasets, design, and branding) is protected by copyright and other laws. Without our prior written consent, you may not:
- Systematically scrape or harvest large portions of the Service or its data.
- Repackage AlaskaTides.app as a competing commercial service or API.
- Use our name, logo, or branding in a way that suggests endorsement or partnership.
Automated access and scraping
Automated scraping of the AlaskaTides.app user interface is generally prohibited, except where we have explicitly granted permission in writing. High‑volume or abusive traffic can degrade service for everyone and may be blocked or rate‑limited without notice.
If you are interested in automated access for research or integration, please contact us so we can discuss appropriate options.
Future JSON/API endpoints
We may expose JSON or other machine‑readable endpoints in the future. Any such endpoints will be governed by their own API Terms, which may include authentication, rate limits, attribution requirements, or usage restrictions.
Until those terms are published, you should not assume that automated access to internal or undocumented endpoints is permitted.