Who operates Seyva
Seyva is operated by Oliver Bartlett in the United Kingdom. This notice covers the public Seyva website and the Seyva mobile app. You can contact us about your information at seyva.app@gmail.com.
Information used by the Today page
When you search, Seyva processes the place name you enter and the coordinates of the result you choose so it can retrieve a nearby coastal outlook. The public page does not ask for your name or an account.
Technical records
Our hosting and service providers may process standard request information such as IP address, device or browser information, timestamps and error logs for security, rate limiting and reliability.
Data providers
Searches and outlook requests are used to obtain information from weather, tide, geocoding and water-quality providers. See the data sources page for the services involved.
Cookies and analytics
Before advertising is enabled, Seyva asks for consent before loading Google Analytics. If you accept, Google Analytics uses cookies and similar identifiers to measure visits, traffic sources, pages viewed, approximate location derived from IP address, device and browser information, and interactions such as scrolling or outbound clicks. Seyva uses this information to understand demand and improve the service.
When advertising is activated, Google’s certified consent management platform will replace Seyva’s analytics-only prompt and manage analytics and advertising choices together. The legal basis for optional analytics cookies is consent. You can change your choice at any time using the privacy and cookie settings link in the footer. Google Analytics is configured without Google Signals.
Google may process Analytics information on Seyva’s behalf. Learn more about how Google uses information from sites that use its services.
Website advertising
Seyva has applied to Google AdSense and is currently under review, so adverts are not yet being shown. Once adverts are enabled, Google’s certified consent management platform will collect the required analytics and advertising choices for visitors in the UK, EEA and Switzerland before optional technologies are used.
Google’s consent platform stores privacy choices in a cookie named FCCDCF for up to 390 days. You can review or withdraw consent using “Privacy & cookie settings” in the footer.
The mobile app
The app uses your chosen location, activities, beaches and conditions preferences to find matching sessions. Settings, cached forecasts and session-detail unlocks are stored on your device. Outlook requests send the selected location and conditions criteria to Seyva’s backend and the relevant weather, tide, location and water-quality services.
If you choose “Use my location”, the app asks for your device’s location permission and uses a current position to find nearby places. You can search for a place instead and change location permission in your device settings. Seyva does not use continuous background location tracking.
Notifications and tracked sessions
For enabled alerts, Seyva’s backend stores an installation identifier, notification preferences, selected locations and activity criteria. Push delivery uses a Firebase Cloud Messaging token and device/platform information. If you track a session, the backend also stores the session and forecast information needed to check for changes and send its updates.
You can change alert preferences in the app, stop tracking individual sessions, or disable notifications in your device settings. Switching notifications off stops delivery; it does not by itself delete every backend record.
Accounts and subscriptions
In builds with account and subscription features enabled, Supabase provides account authentication, including an anonymous app identity or the credentials you choose to use for sign-in. Seyva uses the account identifier to associate access and service records with the correct account. Google Play processes Android subscription payments; RevenueCat and Seyva’s backend process purchase identifiers and subscription status to verify and restore Seyva+ access. Seyva does not receive your full payment-card number.
Optional rewarded ads in the app
When rewarded ads are enabled, you can choose to watch a Google AdMob ad to unlock details for one selected activity session. Completing the ad stores that session’s unlock on this device until its forecast finish time. The reward does not include session tracking. An incomplete or unavailable ad does not grant an unlock.
Google’s Mobile Ads SDK and advertising providers may process your IP address and approximate location, app/device identifiers, ad and app interactions, and diagnostic information to deliver and measure ads and prevent fraud. The Android app disables collection of the Android advertising ID; other identifiers and technical information may still be processed. See Google’s privacy policy and how Google uses information from apps that use its services.
For users in the UK, EEA and Switzerland, Google’s User Messaging Platform presents the applicable advertising choices before the app requests an ad. You can consent, choose “Do not consent”, or manage purposes and providers. You can revisit the form through Settings → Ad privacy choices when Google makes privacy options available. Ad availability and the type of ad depend on your choices. Declining advertising consent does not remove access to Seyva’s free features.
Mobile analytics
In mobile builds with Firebase enabled, Google Analytics for Firebase records screen views, feature interactions and app/device information to help us understand use and improve reliability. Seyva’s custom analytics events are designed without location names, coordinates, notification tokens or free text. The Android configuration disables advertising-ID collection and advertising-personalisation signals. Mobile analytics is separate from the website’s cookie choices and the optional rewarded-ad journey.
Services used by the app
Seyva uses Supabase for its backend and account services, Google Firebase for push delivery and mobile analytics, Google Play and RevenueCat for enabled Android subscriptions, and Google AdMob for enabled rewarded ads. Weather and location services are listed on our data sources page. These providers process the information needed for their role. Some service processing may take place outside the UK; provider privacy information describes their arrangements.
Retention and your rights
Operational logs are retained only as needed for security, diagnosis and service operation. UK data-protection rights may include access, correction, deletion, restriction and objection, depending on the circumstances.
Clearing the app’s storage or uninstalling removes local app information, but does not automatically delete server-side account, purchase or alert records. To request access, correction or deletion of information held by Seyva, contact us using the email below. Rewarded session access expires when the selected session finishes; service records are separate from that local unlock.
Contact
Privacy enquiries and information requests can be sent to seyva.app@gmail.com.