Skip to content
Sunset Beach, NC
Get Support

Privacy — what leaves your phone

Sunset Beach collects one thing: an Apple push token, not linked to you and not used for tracking — sent only when you switch on a pushed alert, or while a launch Live Activity is running (the app starts one when it loads conditions in the hour before a visible launch, unless Live Activities are off for the app in iOS Settings). There is no account, no analytics or crash reporting, no advertising identifier, no location services (the app is about one fixed beach and never asks where you are), and no third-party SDKs — the iOS app has zero external package dependencies, and its privacy manifest declares one collected data type — a Device ID (the push token), not linked to you, not used for tracking, for app functionality. The App Store label is Data Not Linked to You: Identifiers. Two kinds of request leave the phone: a plain fetch of beach conditions from the app’s own server, which carries no identifier; and, only if you switch on one of the three “When conditions change” alerts (or a launch Live Activity is running), your device’s Apple push token sent to the shared NeuralConfig push service so the Worker can notify you. Everything else — tide, moon and launch alerts, Remind me reminders, your preferences, the last conditions loaded — stays on the device. Version 1.1 added no new kind of request.

RequestWhereWhat it carriesWhen
Beach conditionssunsetbeach.neuralconfig.comNothing about you — the same public data everyone gets. No cookie, no device or user identifier.On launch, on pull-to-refresh, and on returning to the app after five minutes or more
Widget summarysunsetbeach.neuralconfig.comSame — a small public summary, identical for everyoneOn WidgetKit’s schedule, asked for about every 30 minutes
Push registrationpush.neuralconfig.comYour APNs device token (hex), the APNs environment (sandbox/production), and the list of topics you opted into: safety, sunset, sunriseOnly while at least one “When conditions change” toggle is on; re-sent on each launch so a reissued token replaces the old one
Push withdrawalpush.neuralconfig.comThe token to removeWhen you switch the last “When conditions change” toggle off — the Alerts screen says “Turning all three off removes this phone from the server.”
Live Activity tokenpush.neuralconfig.comAn activity push token, kind: "liveactivity", the APNs environment, and the launch’s id — addressed to one running Live Activity, with no topics, so it is never in the audience an alert push queriesWhile a launch Live Activity is on your Lock Screen, if Live Activities are enabled for the app
Links outBeach cams, ship trackers, every View at the source link on the Sources screen, and the guide, support, privacy, terms and neuralconfig.com links on the More tabOpened in Safari — you are then on that site under its privacy policyWhen you tap them

The Worker in turn reads NOAA, the National Weather Service, USGS, NC DEQ, Open-Meteo, Cornell Lab and the other public sources listed on Where every number comes from. Those requests come from the server, not from your phone, so none of those organisations ever sees your device or your network.

The same is true of the AI-written summary at the top of Today. The server sends a language model (Claude Haiku from Anthropic, or a Cloudflare Workers AI model as fallback) the beach facts it has already computed — tide, rip risk, water temperature and so on — and nothing else. No request from your phone, and nothing about you or your device, is part of it; everyone sees the same summary.

Tide alerts, “Full moon over the ocean”, “Visible rocket launches” and Remind me reminders on almanac windows are scheduled locally on the phone from data the app already holds — they need no server, register no token, and fire with no signal. Only the three toggles under “When conditions change” — When the water gets worse, A sunset worth walking down for, A sunrise worth getting up for — need the Worker to reach your phone, and all three are off by default. The push service is shared by every NeuralConfig app because an Apple push credential is team-scoped; it treats the topic strings as opaque and never learns what they mean. See Alerts and notifications.

  • Your alert preferences — which tide, moon, launch and push alerts you have switched on, and their lead times — in the app’s own UserDefaults. This is the only “required-reason” API the privacy manifest declares.
  • Your Remind me reminders — each window’s name, start and end time — in the same UserDefaults. A reminder is dropped once its window has started, so the list never grows.
  • The last conditions the app successfully loaded, saved verbatim in the app’s Application Support folder (excluded from backup) so it can draw the beach immediately on opening and still show something with no signal. The app also keeps the ordinary iOS HTTP cache.

Deleting the app removes all of it from the phone. A push token registered at the time stays on the push service until Apple reports it invalid on the next send, and is removed then; to remove it at once, switch the “When conditions change” alerts off before deleting the app. Nothing is written to a shared App Group.

The Nature map draws NOAA zone outlines and iNaturalist points with MapKit. It does not show your position, does not use a location manager, and the app has no location entry in its Info.plist — iOS will never show a location prompt for it. iNaturalist’s coordinates for protected species are already blurred by iNaturalist before they reach the app.

The app’s privacy policy is at https://neuralconfig.com/privacy/sunset-beach/, with the product terms addendum at https://neuralconfig.com/terms/sunset-beach/. https://sunsetbeach.neuralconfig.com/privacy redirects there. Its “What is stored on your device” list matches the one above; the opt-in push registration described on this page is what the current build does.

Support is at https://support.neuralconfig.com/sunset-beach.