Local-first, explained plainly.

The current Beam Reach store beta is account-free and local-first. It does not offer sign-in or cloud sync, and it does not upload your Trips, Race data, preferences, downloaded charts, or exports to a Beam Reach account.

Beam Reach contains no advertising, analytics, Crashlytics, or background location tracking. Your phone platform, network provider, NOAA services, and app-integrity services may still process the ordinary technical data described below.

Foreground location permission lets Beam Reach show your position, calculate selected instrument values, follow a manually selected Trip Guidance leg, and find a nearby NOAA tide station. Beam Reach does not retain a sampled GPS track or location history.

Wind and active-alert lookup is a separate choice. If you enable Share rounded point with NWS, Beam Reach rounds the current point to about 0.01 degrees before requesting National Weather Service data. Turning that choice off prevents those coordinate-bearing wind and alert requests while map GPS and tide features remain available.

Other NOAA requests identify the information needed to serve the feature: a selected CO-OPS station for tides; visible bounds and image size for charts; visible bounds, image size, and current frame time for optional weather radar; or the selected regional package for an offline chart download. NOAA and NWS can also receive the request time, IP address, app identification, and ordinary network metadata.

Saved Trips, unfinished Trip drafts, Race markers and courses, a recoverable active Race session, Race setup drafts, preferences, and offline-chart inventories are stored in the app sandbox. Beam Reach does not create a voyage track. Finishing a Race clears the active session instead of creating a result, although an upgraded older installation may retain legacy result records until you export or erase them.

Downloaded NOAA regional chart files stay in a separate app-owned directory until you delete them, erase app data, or uninstall Beam Reach. Live chart and weather-radar images are caches, not offline products; abandoned allowlisted files are cleaned in bounded batches, and app-data erase clears those chart and radar caches.

Live marine results are held in memory and may remain available for up to 24 hours after their last use so a recently viewed value can still be shown offline. They are not a durable history.

Privacy and Local Data in Settings can create a JSON export and open the operating-system share sheet. The temporary share copy is deleted when sharing returns. Exports can include supported Trips and drafts, Race setup and records, preferences, and bounded offline-package inventories. They exclude live GPS, location history, chart or weather artifact bodies, authentication tokens, credentials, cache contents, and quarantined payloads.

Bulk erase requires an explicit confirmation and processes each supported category independently. It removes supported local records and caches, reports partial failures, and preserves data from a newer schema version that the installed app cannot safely interpret. It does not erase operating-system backups or copies you previously exported.

Beam Reach excludes downloaded chart bodies and sidecars from iCloud or iTunes backup on iOS and stores current Android chart files outside cloud-backup and device-transfer datasets. Other local app data may be included in a platform-controlled device backup depending on your account, device policy, and settings. Deleting app data does not retroactively remove a copy already present in an older backup.

The production app retains Firebase core configuration and App Check for the shared native app-integrity contract. Firebase Auth, Firestore, Functions, Google Sign-In, background-task modules, and development-client modules are not linked into the production artifact.

The production release gate does not initialize cloud sync or resolve Auth, Firestore, or Functions, and a remote setting cannot enable those features in this binary. Retained Firebase and platform integrity services may process installation, device-integrity, IP address, and ordinary network metadata. They do not receive Beam Reach Trip, Race, preference, chart, or export contents from this beta.