July 9, 2026
A complete trust and support chart
Perigee now puts the practical rules and diagnostics beside the product instead of hiding them behind support email.
- Published plain-language privacy, recurring-billing terms, cancellation and refund rules, and an acceptable-use policy covering REST, MCP, OAuth, and AI agents.
- Added a searchable help center, live browser status checks, known-provider limitations, security reporting instructions, and machine-readable security.txt.
- Added a restrictive production Content Security Policy and modern browser security headers for the current Firebase, Stripe, MapLibre/OpenFreeMap, Google sign-in, and Vercel dependencies.
July 9, 2026
Decision-first trip planning
The no-account Trip Health Check gives visitors a useful coastal read before signup.
- Added transparent trip reads for fishing, paddling, boating, tidepooling, photography, and coastal living.
- Results show source, update time, missing inputs, uncertainty, and why the selected window received its read.
- Added a path for signed-in users to preserve the result and continue setup without treating the planning read as navigation or safety advice.
July 8, 2026
Cleaner discovery and canonical station paths
Search engines, answer engines, and people now converge on the same public place-based URLs.
- Expanded machine-readable site descriptions, canonical metadata, structured data, sitemap coverage, and crawler guidance.
- Redirected the legacy Vercel hostname to perigeetides.com while preserving path and query intent.
- Strengthened cross-links among tide, astronomy, fishing, annual, king-tide, guide, developer, and about surfaces.
July 7, 2026
Weekly Tide and alert self-service
Account-linked coastal email became a managed product surface rather than a one-off signup form.
- Added Weekly Tide station selection and account preference management.
- Added one-click unsubscribe that works without requiring sign-in.
- Added scheduled Weekly Tide and tide-alert delivery foundations with clear source and not-for-navigation wording.
What belongs here
The changelog highlights shipped behavior that a visitor, subscriber, or developer can notice. It is not a security disclosure queue, incident ledger, or promise that every roadmap item is available. For current diagnostics use Service status; for planned capabilities, rely on what the live product and current pricing page explicitly offer.