1. Who we are and how to contact us
The Services are operated by the operator of Marine Conditions. For privacy requests, questions, or complaints, contact support@marineconditions.com.
This Privacy Policy should be read together with the Terms of Use. If you do not agree, do not use the Services.
2. Scope
This policy covers the website, the iOS app (including widgets, Live Activities, and background refresh), any Android app we publish under the same name, and our servers at marineconditions.com that provide buoy data, camera images, search, nearby-station lookups, and remote configuration.
It does not control the practices of independent third parties such as NOAA National Data Buoy Center, Apple, Google, map providers, advertising networks, or analytics vendors. Those parties have their own policies.
3. No account; what we do not collect
You can use the Services without creating an account, signing in, or providing a name, password, payment card, or government ID to us. We do not operate a public user profile, social network, or in-app messaging product.
We do not intentionally collect precise health data, contacts, photos from your device camera, microphone audio, SMS, call logs, or files from your photo library. “Camera” features in the Services display publicly available NOAA buoy camera images, not images from your device.
If you email us, you choose what to include. Do not send sensitive personal information that we do not need.
4. Information we collect
We collect the categories below. Some items stay only on your device. Others are sent to our servers or to processors listed in Section 8.
4.1 Information you provide
- Support and feedback messages sent to support@marineconditions.com, including any buoy station ID, screenshots, or diagnostic details you attach.
- Optional onboarding choices such as a use-case preference (for example boating, fishing, or surfing), if you complete onboarding.
- Alert rules you create (station, metric, threshold, and comparison). These are stored on your device and used to evaluate local notifications.
- Favorite stations, unit preferences (wind, temperature, pressure, distance, wave height, tide), and pinned widget stations. These are stored locally on the device and, where needed, in the app group used by widgets.
4.2 Location
If you grant location permission, the mobile app requests “when in use” location at approximately kilometer-level accuracy to find nearby buoy stations, show your position on the map, estimate distances, and let widgets resolve a “nearest favorite” station.
When you use Nearby, the app sends the current latitude and longitude to our API (for example /api/v1/nearby) so we can return stations within the requested radius. We use those coordinates to compute results for that request. We do not require an account to do this.
A last-known latitude and longitude may be stored locally in the app group so widgets can work without asking for a fresh GPS fix every time.
On the website, the Near Me page may use the browser Geolocation API in your browser only. We do not receive that browser location unless you later use a feature that sends coordinates to our API.
You can refuse or later revoke location permission in system settings. Nearby and map-centering features will then be limited or unavailable.
4.3 Device, app, and usage data
- App version, build number, bundle identifier, device type, operating system, language, time zone, and whether the install is a debug or production build.
- An anonymous persistent identifier created on first launch, stored in the iOS Keychain and UserDefaults, and used to recognize the same install for subscriptions (Adapty customer user ID) and analytics user properties. This is not your name or email.
- Product events such as screens viewed, buoys or regions opened, searches (query length and result count, not the raw search text in analytics parameters), favorites added or removed, alerts created, chart range changes, share actions, deep links, notification permission status, and session length.
- Technical events such as API errors, offline state, force-update prompts, and crash or “application not responding” reports.
4.4 Notifications
Condition alerts use local notifications scheduled on your device. We request permission for alerts and sounds. We do not currently operate our own remote push-notification service or collect a push token on our servers for marketing blasts.
Background refresh may run on the device to re-check buoy observations against your alert rules. Delivery is not guaranteed and depends on the operating system.
4.5 Purchases and subscriptions
If you buy a premium subscription or other in-app product, Apple or Google process the payment. We receive entitlement status (for example whether “premium” is active), product identifiers, and restore/purchase results through Adapty. We do not receive your full payment card number.
Premium currently unlocks an ad-free experience, higher or unlimited favorite and alert limits, advanced charts, and fuller camera-feed access. Exact offerings are shown in the store listing and paywall at the time of purchase.
4.6 Advertising and tracking identifiers
Free users may see ads served by CAS.AI (Clever Ads Solutions) and downstream networks that can include Google AdMob and other mediation partners. Ad types in the current iOS app include app-open ads and banners. Interstitial and rewarded placements may be enabled later.
On iOS, we may show Apple’s App Tracking Transparency prompt. If you authorize tracking, advertising partners may access the Identifier for Advertisers (IDFA) and use it for measurement, frequency capping, and personalized ads. If you deny tracking, we still may show contextual or non-personalized ads that use SKAdNetwork and other privacy-preserving signals.
Advertising SDKs typically collect device identifiers, IP address, approximate location derived from IP, device model, OS version, app identifier, consent signals, and ad interaction and revenue events.
4.7 Website logs, cookies, and session analytics
Our web server and content-delivery infrastructure may record IP address, date and time, requested URL, referrer, user agent, and basic error logs. These logs are used for security, abuse prevention, capacity planning, and debugging.
The website uses Yandex Metrica (counter ID 108263419), including cookies and similar technologies, page-view tracking, referrer capture, link tracking, click maps, and Webvisor session replay. Webvisor can record interactions with the page (clicks, scrolling, and mouse movement). Do not enter secrets into the website; the site does not provide an account form, but support emails are outside that page.
The website also stores unit-display preferences in your browser localStorage so converted values stay consistent between visits. That preference stays on your device.
4.8 Marine observations we process (not about you)
The Services fetch, cache, and display public marine observations and station metadata from NOAA National Data Buoy Center, including wind, gusts, waves, period, pressure, air and water temperature, dew point, visibility, tide, and buoy camera images. We may derive condition labels, fog-risk hints, trends, and “best conditions” rankings from those observations. Those datasets describe the ocean and stations, not you, unless you combine them with your own location.
5. How we use information
- Provide, maintain, and improve the Services: maps, nearby stations, charts, camera feed, regions, search, widgets, Live Activities, and remote feature flags.
- Remember your settings, favorites, alerts, and unit preferences on the device.
- Evaluate alert rules and show local notifications when thresholds are crossed.
- Process and restore subscriptions and gate premium features.
- Show advertising to free users and measure ad performance.
- Understand product usage, diagnose crashes, prevent abuse, and enforce the Terms of Use.
- Respond to support requests and legal obligations.
- Communicate service-related notices such as a required app update when a minimum version is configured.
6. Legal bases (EEA, UK, and similar jurisdictions)
If the GDPR, UK GDPR, or a similar law applies, we process personal data on these bases:
- Contract: to provide the features you request (nearby lookup, subscriptions you buy, support you initiate).
- Legitimate interests: to keep the Services secure, understand aggregate usage, prevent fraud, and improve reliability, balanced against your rights.
- Consent: device location, notification permission, App Tracking Transparency, and non-essential website cookies / Yandex Metrica where consent is required. You may withdraw consent in system or browser settings.
- Legal obligation: to keep records required by tax, accounting, or lawful requests.
7. How we share information
We do not sell your name or email, because we generally do not have them. We do share information with processors and platforms that help us run the Services. “Sharing” for advertising measurement may occur as described below.
7.1 Service providers and platforms
- Hosting and our own API on marineconditions.com — receives nearby coordinates when you request nearby buoys, plus ordinary request logs.
- Apple App Store / StoreKit and Google Play Billing — purchase, restore, and subscription status.
- Adapty — subscription paywalls, entitlements, customer user ID, and purchase analytics.
- Firebase (Google) — analytics events and a user ID we set to the anonymous persistent identifier.
- AppMetrica and AppMetrica Crashes (Yandex) — analytics, sessions, revenue auto-tracking, crash and ANR reports, and the same anonymous profile ID.
- CAS.AI and its ad networks (which may include Google AdMob and others) — advertising identifiers, device data, and ad events. SKAdNetwork items are configured for measurement.
- Kingfisher and on-device caches — store NOAA and camera images locally; this is not a transfer to a new company.
- MapKit / Apple Maps and any map tiles or reverse-geocoding the operating system performs.
- Yandex Metrica on the website — cookies, page views, and session replay as described above.
- Email providers if you write to support@marineconditions.com.
7.2 Legal and business transfers
We may disclose information if required by law, regulation, legal process, or governmental request; to protect the safety of any person; to prevent fraud or abuse; or in connection with a merger, acquisition, financing, or sale of assets, in which case the successor will be bound to this policy or a successor notice.
7.3 What we do not do
We do not rent a list of user emails. We do not run a data-broker marketplace. We do not share your precise location with advertisers as a standalone product. Advertising partners may still infer approximate location from IP address as is standard in mobile ads.
8. International transfers
The Services are used worldwide. Information may be processed in the United States, the European Union, and other countries where our processors operate. AppMetrica and Yandex Metrica are services of the Yandex group and may process data in jurisdictions that include the Russian Federation.
Where required, we rely on the processor’s transfer mechanisms (such as Standard Contractual Clauses) and on your consent for optional SDKs. If you do not want analytics or advertising SDKs to run, do not grant tracking permission, limit tracking in system settings, and do not use the website if you object to Yandex Metrica.
9. Retention
- On-device favorites, alerts, units, last location, and the anonymous Keychain identifier remain until you delete them in the app or uninstall the app (Keychain items may survive reinstall on the same Apple ID until you reset them).
- Nearby API requests are processed to return a response. Server access logs are kept only as long as needed for security and operations, then deleted or aggregated.
- Analytics, crash, advertising, and subscription records are retained by the relevant vendor under that vendor’s schedule.
- Support emails are kept as long as needed to resolve the request and for legitimate record-keeping.
- Cached NOAA observations and buoy camera images on our servers follow short operational TTLs and are not a personal profile about you.
10. Security
We use commercially reasonable administrative and technical measures, including HTTPS for our API and limited access to servers. No method of transmission or storage is completely secure. You are responsible for the security of your own device and Apple/Google account.
The current iOS app declares that it does not use non-exempt encryption beyond standard HTTPS (ITSAppUsesNonExemptEncryption = false).
11. Your choices and rights
11.1 Device controls
- Location: iOS Settings → Privacy & Security → Location Services, or the equivalent Android setting.
- Notifications: system notification settings for Marine Conditions.
- Tracking / IDFA: iOS Settings → Privacy & Security → Tracking.
- Personalized ads: OS-level ad personalization controls and, where shown, in-ad controls.
- Website cookies: browser settings; clearing cookies resets Yandex Metrica identifiers and localStorage unit preferences.
11.2 Access, correction, deletion, export
Because we do not operate user accounts, most personal data we hold is either on your device or in third-party analytics/ad/subscription systems keyed by device or anonymous IDs.
You may request access, correction, deletion, restriction, or portability by emailing support@marineconditions.com from the address you used to contact us and including your platform, app version, and approximate dates of use. We may need to verify the request. We will respond within the time required by applicable law.
Uninstalling the app deletes local favorites, alerts, caches, and most identifiers from that installation. To request deletion of vendor-side analytics records tied to the anonymous ID, email support@marineconditions.com and we will take reasonable steps with our processors.
11.3 California and similar US state laws
If you are a California resident (or a resident of a state with a similar privacy law), you may have the right to know, delete, correct, and opt out of “sale” or “sharing” of personal information for cross-context behavioral advertising.
We do not sell personal information for money. Advertising SDKs and analytics may constitute “sharing” or targeted advertising under some state laws. You can opt out by denying App Tracking Transparency, disabling personalized ads in system settings, and using any opt-out link a vendor provides. You may also email support@marineconditions.com with the subject line “Privacy rights request.” We will not discriminate against you for exercising these rights.
We do not have actual knowledge that we sell or share the personal information of consumers under 16.
11.4 EEA/UK complaints
You may lodge a complaint with your local data protection authority. We encourage you to contact us first so we can try to resolve the issue.
12. Children
The Services are for mariners, boaters, anglers, surfers, and other adults. They are not directed to children under 16, and we do not knowingly collect personal information from children under 16. If you believe a child has provided personal information, contact support@marineconditions.com and we will delete it as required by law (including COPPA where applicable).
13. Do Not Track
The website does not respond to browser “Do Not Track” signals. Use cookie controls and the choices in Section 11 instead.
14. Third-party privacy notices
Please review Apple Privacy Policy, Google Privacy Policy, Adapty’s privacy notice, CAS.AI / Clever Ads Solutions policies, Firebase / Google Analytics policies, AppMetrica and Yandex Metrica policies, and the NWS disclaimer. Apple and Google process payment data under their terms, not ours.
15. Changes
We may update this Privacy Policy. The “Last updated” date at the top will change. Material changes will be posted on marineconditions.com/privacy and, where appropriate, surfaced in the app. Continued use after the effective date means you accept the updated policy, except where applicable law requires consent.
16. App Store and Google Play disclosures
The data types below are intended to align our public store privacy labels / Data safety forms with this policy. Store UIs change; this section is a guide, not a substitute for those forms.
- Location: Precise or coarse location, collected if you grant permission, used for app functionality (nearby buoys, map, widgets). Shared with our API when you request nearby results. Not used for tracking if you deny ATT.
- Identifiers: Device ID / advertising ID (if tracking is authorized), and an anonymous app-instance ID. Used for analytics, subscriptions, and advertising.
- Purchases: Subscription or in-app purchase history, processed by Apple or Google and Adapty.
- Usage data: Product interaction and diagnostics / crash data.
- Diagnostics: Crash logs and performance data via AppMetrica Crashes and similar tools.
- Advertising data: collected by ad SDKs for free users.
- We do not collect user contact information as a required field. Email is collected only if you write to us.
17. Contact
Privacy requests: support@marineconditions.com
Website: marineconditions.com
Related terms: Terms of Use
Liability for use of marine data is limited as described in the Terms of Use (including a damages cap of USD 50 or the amount you paid us in the prior 12 months, whichever is greater, to the maximum extent permitted by law). This Privacy Policy does not expand that liability.