Sonny & Robo · StormBeacon

Privacy policy

Reviewed October 28, 2026 · Android, iOS & browser

Publisher: Brian Schwartz (individual)

Brand: Sonny & Robo

Publisher website: https://sonnyandrobo.com/

Privacy contact: support@sonnyandrobo.com

Effective date: 2026-10-28

Contact privacy support · Delete local data or request deletion

Intended audience and the local age check

StormBeacon is intended for teens and adults ages 13 and older, not children under 13. Starting with version 1.39.3, Under 13 and Prefer not to answer leave weather features unavailable and show an offline notice. The local age-safety check is required before opening those features. It asks no exact age or birth date and stores only an access category on this device. That choice is never sent to the developer or a service. The screen is not identity verification or verified parental consent.

An unknown or restricted category cannot start weather-provider requests, use GPS, open saved places, enable background weather or widgets, upload feedback or diagnostics, or open social feeds or payment links. Privacy information remains readable offline. Existing restricted categories stay restricted when upgrading, and earlier background jobs are disabled. Normal 13-or-older profiles keep their saved settings and weather data. Clearing operating-system app storage removes local choices. The hosted browser app still contacts its web host to load the page and assets before an age choice; this is not a claim of zero hosting metadata.

Versions 1.39.0 through 1.39.2 offered a restricted city-weather view that sent selected public city-center coordinates and ordinary connection metadata to NOAA/NWS. That mode is no longer offered in 1.39.3 onward. Version 1.39.0 briefly used a numeric age entry that was discarded after selecting the category. Versions before 1.39.0 had no age screen. Updating cannot remove information already held by providers or erase copies shared from earlier versions.

We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, contact support@sonnyandrobo.com so we can investigate and delete information under our control as appropriate. Do not send identity documents or a child's unnecessary personal details. The following sections describe the available app features for users 13 and older and the providers they contact.

At a glance

StormBeacon is independent weather software published by Brian Schwartz, an individual using the Sonny & Robo brand. This notice covers the Android and iOS apps and the browser app. It does not cover unrelated websites. No account is required. Saved places, preferences, weather caches and local performance totals stay on your device unless you choose to export or share them. The app has no advertising SDK, advertising identifier or cross-app advertising tracking, and we do not sell your personal information.

Weather and maps still need internet requests. The services described below receive the place coordinates, search text, map area or public weather reference needed for the feature you use, along with connection information such as your IP address. Choosing a place does not tell us whether you live there. GPS is optional; you can search for a city instead. Optional background checks use saved coordinates, without continuously tracking your device.

Feedback is sent only after you review and submit or share it. You choose whether to include a reply email and technical diagnostics. Internal test controls belong to separate testing editions. Normal crash recovery and local App data & performance reports remain available in the public app.

Settings backups you choose to save

Backup & restore lets you select preferences and individual saved places. Locations start unselected. Portable encryption starts on for every export and uses a passphrase you choose; StormBeacon does not retain or send the passphrase and Sonny & Robo cannot recover it. Turning encryption off requires confirmation for each export: readable JSON can expose settings, addresses and exact coordinates. Removing address text does not hide the saved point. Choose a private destination; your chosen Files/cloud provider controls uploads, access, synchronization and retention. StormBeacon does not upload backups to its website, automatically synchronize them or connect to a cloud account.

Restoring a file lets you review the included items. Chosen places are added or updated without deleting unrelated saved places. Permissions, notification and background enable switches, widget assignments, diagnostic consent and downloaded weather are excluded. A local undo copy retains only replaced settings and affected places for 24 hours, until the next restore, or until you remove it. Android/iOS undo records are encrypted with a key protected by the device's secure storage. The browser preview holds undo only in memory for the current page session. Expired copies are removed on the next startup or backup-screen check; expiry does not promise deletion while the app is closed.

Sharing temporarily stages the already-encrypted file in private app cache, or readable JSON if you explicitly choose an unencrypted export. The next share or Delete saved places and weather data removes those temporary exports. A file picker or cloud provider may stage its own copy. Deleting local app data cannot delete backups saved elsewhere or recall shared copies. Losing an encrypted backup's passphrase makes that file inaccessible.

Sharing weather alerts

Opening infographic previews uses official NOAA/NWS alert text, boundaries, times and published hazards to prepare a StormBeacon infographic. For supported tornado and severe thunderstorm watches, it also downloads a matching official SPC map directly from www.spc.noaa.gov and offers the unchanged image separately. These requests contain a public alert or watch reference and normal connection information, including your IP address; no saved address or GPS fix is sent for this lookup. The app checks the active NWS message before exporting an official watch image. The StormBeacon summary remains available when a government image cannot be matched or retrieved. Infographic preparation does not search social-media posts or contact the warning-graphics backup service. The separate optional office updates described below are not used as official alert graphics. Older installed versions may still request public X pages, images and the backup service under their earlier notice. Opening an external source or office social link uses that website under its own policy.

Text-only sharing opens your device's share sheet with the full alert message. Opening a storm-surge shape without an alert identifier can query NWS for the tapped map coordinates to find a matching message. Preparing an infographic can request the selected public alert and its mapped area or nearby county boundaries directly from NOAA/NWS. Those services receive the alert identifier, requested map bounds, your IP address and normal connection metadata. The graphic is drawn on this device and includes alert text, source, timestamps and official boundaries when available. It does not include your GPS marker, saved location label or street address. It is not automatically uploaded to Sonny & Robo or any image-generation service.

When you choose Share for either image, the app offers the PNG and full text to the sharing destination you select. The destination may omit the image or caption and handles what you send under its own policies. On Android and iOS, exported PNGs remain temporarily in private app cache so a receiving app can read them. At most eight sharing exports are retained; files older than twenty-four hours are removed on a subsequent share, not by a background timer. Delete saved places and weather data also removes these cached PNGs. Copies already shared cannot be recalled.

Copy for each version places only that selected image on the system clipboard at your request, replacing its current content. StormBeacon does not read clipboard contents. The operating system and apps you paste into control clipboard access, retention and any device synchronization. Android keeps copied PNGs in a separate private app cache directory and grants read access through the normal clipboard. The latest image and up to three previous copies are kept briefly; older copies and previous files older than one hour are removed on a later copy, not by a background timer. Delete saved places and weather data also removes these files. Local deletion does not clear the system clipboard or recall copies already pasted or synchronized.

Weather forecast sharing

Current conditions and Week ahead can be copied as text or shared using your device's share sheet. Infographics are drawn locally from the displayed weather data and include the source, forecast time and the same public location label shown on the Weather card. A custom location nickname may appear. Preparing a forecast infographic does not upload it or request an AI-generated image. Copy text or Copy image replaces the system clipboard at your request; StormBeacon does not read it. Shared forecast PNGs use the same temporary storage, cleanup and destination behavior described for alert images above.

Optional office weather updates

For alerts from all 122 NWS forecast offices, Load office updates retrieves public posts from allowlisted unofficial Bluesky bots for the issuing office. This includes Alaska, Hawaii, Guam and Puerto Rico. The separate Pago Pago weather service office has no verified supplemental feed and shows an availability notice. St. Louis also offers an unofficial Mastodon feed on social.edist.ro. Nothing is requested until you choose to load a feed. These independent accounts repeat weather-office products and may create their own text images; they are not official NWS accounts. Their posts do not change alert status, boundaries, expiration or notifications and are not matched to the selected alert.

Bluesky or the Mastodon server receives the public account identifier, pagination or post reference, your IP address and normal request headers. A selected image loads from cdn.bsky.app or social.edist.ro. No login, saved place name, street address, GPS fix or persistent device identifier is sent. Native requests omit cookies; browser image display and links opened in your browser follow that browser's cookie and referrer settings. Opening the original post, source profile or linked bulletin contacts the indicated website under its own policy.

Feed responses reuse the bounded provider cache for two minutes; refreshed or rechecked posts still obey request limits. The panel shows at most three pages and 90 posts from the past seven days. Closing it discards displayed posts and previews, while the shared session cache can retain its bounded copies until eviction, clearing or app restart. Browser image caching follows browser/provider rules. Images load on demand. Missing, removed or unsupported attachments keep their available text and source link; cached or already-visible content may remain until refreshed. Posts are not stored as official alerts, exported as official NWS graphics, or uploaded to Sonny & Robo.

Android current-weather notification

An optional silent weather card shows conditions for your selected or chosen saved place in the Android notification shade. It is off by default and separate from weather warnings. When enabled, it reuses saved forecasts and targets a refresh about every thirty minutes; Android may delay work. Wi-Fi-only is the default network choice, including manual Refresh. You can allow cellular in the card settings. Requests go directly to the same weather providers, which receive the requested coordinates and normal connection metadata. The card does not continuously track GPS or keep the app running indefinitely.

The card stores its display text and update timestamp in private app storage and marks lock-screen details private. Android and your notification settings control how it appears. Disable the card or delete local app data to remove its stored display information. Dismissing it hides it until you show it again from Settings. Its device-only activation and location choice are excluded from portable backups. A failed update keeps the prior forecast and original timestamp.

Android home-screen widgets

Adding a widget stores its location choice and a bounded weather snapshot privately on this device. The Android launcher displays that snapshot on your home screen, including its place label, so others viewing your screen can see it. Each widget can use its own saved place, follow the selected app place, or follow device location. Deleting a widget's saved place leaves it asking for a new location. Deleting all local app data clears widget snapshots, location choices and the last device fix too; the empty widgets may remain on your home screen until you remove them.

Weather widgets refresh about every thirty minutes on unmetered Wi-Fi by default, when Android permits it. Settings can allow any network or turn automatic refresh off. Battery Saver and Data Saver pause widget downloads. Several widgets share forecasts, and each pass downloads at most three locations. Manual refresh uses your current network. NOAA/NWS receives the requested coordinates, your IP address and connection metadata. Saved location names are not sent to weather providers.

Radar widgets also request radar frames from NOAA for their chosen area, zoom and product. A preview, initial setup or manual refresh can request the visible base-map tiles from OpenStreetMap; automatic radar refreshes reuse saved base-map tiles instead of downloading new ones. Map tiles are reused for at least seven days before revalidation, subject to validation and storage limits, and retained privately until cleanup or deletion. Removing a widget does not immediately erase those reusable tiles. Loading and playing a widget can show a short-lived Android notification with a Stop control. Playback stops automatically. Home-screen and lock-screen widget availability depends on Android and your launcher; these are not iOS widget features.

Follow device location requests a foreground GPS fix when you open StormBeacon or tap a device-location widget, after permission is granted. It stores only the latest fix and its time, not a travel history, and uses it for weather requests. It does not track travel while the app is closed. Automatic forecast downloads can use the last fix for up to twenty-four hours; older forecasts and location times remain labeled until refreshed or cleared. GPS is optional; saved-place widgets work without location permission.

iOS home-screen and lock-screen widgets

On iOS 17 or newer, optional StormBeacon widgets display saved weather and the latest radar scan. The app shares a bounded forecast catalog and radar images with its own WidgetKit extension through a private on-device App Group, excluded from device backups. This does not send the catalog to the developer. Location names are hidden by default; if enabled, people viewing the screen may see them. iOS controls lock-screen privacy redaction and refresh timing.

The extension makes no network requests and does not request GPS. The app prepares widget data using the existing forecast and radar caches and the selected Wi-Fi-only, any-network or automatic-refresh-off setting. Radar images use NOAA radar and state/county outlines. Providers receive the requested coordinates or map area, IP address and normal connection metadata, as with weather viewed in the app. No new provider is introduced for iOS widgets. Device-location widgets use a recent fix obtained in the app, valid for up to twenty-four hours; they do not track travel in the background.

Forecast snapshots expire after forty-eight hours and radar scans after ninety minutes. Failed or partial radar downloads keep the previous image with its original scan time until it expires. Removing a saved place removes its widget data during the next app publication; deleting local app data or entering the restricted audience state clears the shared widget store. iOS may retain an already-rendered widget briefly until it processes the requested timeline reload. Remove the widget from the Home Screen or Lock Screen if you need to hide it immediately.

Current NOAA lightning

If you enable on-device GLM lightning, the app downloads public NOAA GOES-18 or GOES-19 lightning catalogs and satellite files from NOAA's Amazon S3 open-data buckets while Radar is active and showing Current. The visible map determines which satellite feed is downloaded; maps spanning the coverage boundary use both. This selection can indicate the broad region you view. The phone decodes the files and groups nearby flashes locally. Requests identify satellite products and observation times, without GPS coordinates, map bounds, saved locations or place names. NOAA's data hosting service receives your IP address and normal connection metadata and may retain request logs under its policies. No publisher relay or FreeLightning request is made. Downloads can use significant mobile data, varying with satellite activity and the number of feeds; the layer is off until enabled. Turn lightning off to stop new downloads; requests already in progress cannot be recalled. Recent decoded observations are reused in memory, and local download and processing totals are not uploaded.

Flashes are displayed for five minutes after their observation time and are hidden during radar playback, historical viewing or when the feed is stale or unavailable. The feed covers a bounded North American area; satellite detection coverage varies. An empty map does not establish that an area has no lightning. Lightning is not monitored in the background and does not send lightning alerts.

Unavailable optional providers

Philippines forecasts/radar and the FreeLightning layer are unavailable in this release. Stored settings and restored backups cannot enable their provider requests. Saved locations remain on your device. Earlier app versions may have contacted these providers under the settings described in their notices; installing this update does not delete information already held by those providers.

Publisher services and testing editions

Sonny & Robo operates the optional feedback service and a legacy backup lookup used by older versions for public NWS warning graphics at sonnyandrobo.com, hosted by Hostinger. Most weather, map and address requests go directly to the named providers. Separately installed testing editions have their own settings, storage and permissions. An optional radar-cache pilot is limited to testing editions and is described below; it is not enabled in the public app.

Weather, maps and internet requests

Winter-impact tiles and forecast dates are requested from NOAA/NWS WPC. If you enable the U.S. Drought Monitor, StormBeacon downloads a generalized national report from the National Drought Mitigation Center's public Esri ArcGIS service. That national-report request does not include your coordinates or saved place names, but NDMC/Esri receives your IP address and normal connection metadata. The report is cached locally and normally checked every six hours while the layer is visible; it is included in the app's weather-data deletion controls.

When the normal NWS forecast service fails, StormBeacon may request an alternate official NOAA/NWS NDFD forecast using the same place coordinates. Alternate results are labeled in the app, reused for thirty minutes, and stored with your other saved weather. Saved place names and street-address text are not sent in these forecast requests. Alert checks stay separate from forecast fallback.

NOAA / National Weather Service receives the coordinates of places you view for forecasts and alerts. NOAA map services and OpenStreetMap tile servers receive the geographic areas and map images you request. NOAA services also supply visible/infrared satellite, temperature, feels-like temperature, dew point, cloud cover, precipitation chance, forecast rain/snow/ice amounts, analyzed snow depth, recent radar-estimated rainfall, wind, fronts and pressure, and Climate Prediction Center temperature/precipitation outlooks. Animated wind is drawn locally from downloaded forecast data. The Storm Prediction Center receives requests identifying the outlook day, type and issue time when you open discussion text or prepare its official-map infographic. Those discussion/graphic requests do not include saved place names or GPS coordinates. Pages and bounded static images use local caches and deletion controls; generating a preview does not upload your generated image. Requests expose your IP address and normal connection metadata, such as request time and app/browser headers, to the provider.

After you choose a starting location, the app may quietly prepare weather and the latest radar image while you use another tab. Radar history preparation follows your Auto (unmetered Wi-Fi), Always or Never setting and bounded memory limits. Preparation prioritizes the current map zoom, then nearby zoom levels within the same map area. Never disables advance history preparation; current images and frames you request still need internet. Providers may retain connection or request logs under their own policies; these requests are not promised to be anonymous or immediately erased.

Keep radar fresh while away defaults to On for new settings; existing On or Off choices are preserved. You can turn it off in Settings. Background downloads require platform permission and an eligible network. With Radar open, switching away from the app can continue NOAA radar downloads for the last viewed map area during a short session, up to fifteen minutes. Auto requires unmetered Wi-Fi, Always permits mobile data, and Never disables this preparation. Android shows a download notification with a Stop control and checks for new observations about once a minute. iOS controls background transfer scheduling and may defer work; the app checks again when you return. No new background GPS fixes are taken. Playback, map drawing, lightning and other overlays stay paused. NOAA receives the requested map area and connection metadata during these downloads.

Optional radar cache test

Testing builds may offer a Radar cache test switch. It is off by default, requires a testing-build flag, and turns off again when the app restarts. While enabled and Radar is active, the app checks a small manifest at sonnyandrobo.com and may request supported reflectivity PNG tiles from Sonny & Robo’s Hostinger hosting and CDN. The tile path identifies a NOAA observation time and a map tile, which can reveal the approximate area you view. Hostinger and the publisher can receive your IP address, request time, requested path, status and normal connection headers. These requests do not contain saved place names, typed street addresses, diagnostic files or an exact GPS fix.

The app continues to get its playback timeline from NOAA and falls back to NOAA for missing, invalid or unavailable cache images. Other products, areas and optional background radar sessions continue to use the existing direct providers. Turning the test off stops new pilot requests; a request already in flight cannot be recalled. Your saved locations, preload preference and device cache limits are unchanged.

The pilot stores shared NOAA PNG tiles, observation metadata and aggregate job status. Its default origin image retention is one hour from observation time, with deletion during bounded scheduled cleanup; missed jobs can delay deletion. CDN and device copies may remain until their own expiry. The pilot code does not write individual visitor logs, but hosting, CDN security and access logs can contain personal data and have separate retention and access rules. Before enabling an externally distributed testing build, the publisher must confirm and publish those log practices and a monitored privacy contact. Clearing app data does not delete hosting logs or recall earlier requests. Contact the publisher using the published privacy contact about records held by the publisher; independent providers handle their records under their own policies.

City, address and GPS choices

U.S. city-name searches and saved-place matching run on your device. Street address mode sends partial search text to Photon, operated by Komoot, after at least four characters and a short typing pause. It includes the set location rounded to two decimal degrees to improve matching. In the Android and iOS apps, an entry that appears to include a house number, street and city is automatically sent to the U.S. Census geocoder after about a one-second typing pause. State and ZIP are optional. Tapping Look up full address also sends the entry. Automatic lookup stops when you leave the field or search screen, switch modes, or background the app; a request already sent may finish, but outdated results are ignored. No location is selected or saved until you choose it. The browser does not perform Census lookups. These services receive your IP address as well.

Choose on map lets you attach an entered address to a point you choose manually. If the city is absent from the offline directory, opening this picker sends the entered city and state to Photon once to find a starting area. It does not send the street address in that city-only request. OpenStreetMap receives requests for the map area you view. The city center is not treated as a house match; you must choose and confirm a point, then save it separately in Locations. The saved entry identifies its position as manually placed.

Use my location requests foreground location permission and obtains one GPS fix, sometimes reusing a recent accurate fix. The point is sent to Photon for nearby address suggestions unless the reported accuracy is worse than one kilometer. In U.S. search, the nearby city is found locally. You can choose the city center, GPS point or an address. The selected coordinates are then used for weather. City search works without GPS permission, and you can revoke permission in your device settings. There is no continuous or background GPS tracking.

Holding the map or selecting a GPS/address point creates a temporary weather preview. It is not saved as a location until you save it in Locations. Preview coordinates are sent for weather, but preview forecasts are not written to the saved forecast store. Restarting the app discards the preview. The Alerts tab continues to use your set location.

Local storage and retention

Your selected place, up to 12 saved places, their coordinates, addresses and names, preferences, recent forecasts and notification history are stored on this device. These records remain until changed, removed or cleared. Recent forecasts are limited to 12 cache entries and are not reused after 48 hours. That is a freshness limit, not a promise of deletion at 48 hours; older files may remain until replaced or cleared. Removing a saved place does not by itself erase every cached forecast for that place.

Notification duplicate history is limited to 512 entries; entries older than seven days are pruned when the history is read or updated. The local error journal holds up to 50 error groups and prunes entries older than seven days when accessed or updated. Address suggestion responses are limited to 32 entries in memory, expire for reuse after five minutes and are removed during later lookups or when the process exits. Native radar PNG files are cached locally, up to 16 MiB in Lite mode or 128 MiB in Standard mode, separately from the bounded map memory cache. NOAA and RainViewer tiles stored as reusable, time-stamped frames expire for reuse 90 minutes after download; other cached radar files expire after 30 minutes. Matching files can be reused after an app restart, within these storage limits. Files are pruned on cache use; expiry is not a guarantee of deletion while the app is closed. Radar disk files are excluded from backup and included in Delete saved places and weather data. Weather-provider responses use a separate 48-entry session cache. Large responses can move from memory into private, backup-excluded temporary files; they may contain requested coordinates, address results or weather content. Freshness limits trigger revalidation rather than immediate deletion. Files are removed when entries are replaced, during Delete saved places and weather data, or when a later app session first uses this cache. Other bounded network/image caches may remain for the process or in platform-managed storage.

Android app backups and device-to-device backup transfer are disabled. On iOS, the app’s saved places, settings, forecasts and local report history are excluded from iCloud backup. The browser preview instead stores data in that browser. Device memory and connection type are checked locally to adjust performance and preloading; the app does not read your Wi-Fi network name.

Local app data and performance totals

Lightweight app-data collection is on by default and can be paused in App data & performance. Fixed numeric totals cover monitored weather requests, cache reuses, rejected responses, radar tile downloads and payload bytes, radar frame-ready events and local problem reports. Native radar totals include ordinary widgets and background radar work. No request URLs, frame identifiers, coordinates, saved names, search text, weather content or device identifiers are stored with these totals.

Totals reset into a new local calendar day at midnight. Retain today only, three days or seven days, with seven days as the default. Older days are pruned during the next app or radar activity; the phone is not woken solely to erase them. No totals are retained forever. Writes are batched during activity, so an abrupt crash can lose the latest unsaved batch. Opening or refreshing the report takes one available process-memory sample; this is not a continuous monitor or whole-device/GPU measurement. Memory samples are not saved to the daily history.

App-data reports stay on the device unless you review and share them. These totals are never sent by automatic error reporting. Local support/feedback diagnostic drafts can include retained app-data totals; the dedicated App data report also includes available native radar totals and its memory sample, with an optional local error journal. Your chosen sharing app controls any copies you send or save. Reset app data deletes the retained totals without clearing weather. Delete saved places and weather data also deletes these totals and leaves local app-data collection off; only the off preference is retained.

Optional weather-alert notifications

If you enable notifications, the app checks NOAA/NWS at your selected and saved U.S. places using their stored coordinates. You can choose watches and warnings, warnings only, all NWS alerts, or the severe/extreme filter. Philippine locations are excluded. Foreground alert and visible radar-hazard checks offer one-, two- or five-minute intervals. Background alert targets are fifteen, thirty or sixty minutes; the operating system can delay or prevent them. Partial or unavailable checks are shown in the notification status. A bounded on-device ledger records the last attempt and successful check for up to thirteen monitored coordinate pairs; it is replaced during checks and cleared by Delete saved places and weather data. It does not obtain new background GPS fixes. Notifications are generated on your device without a developer push-notification service. Turn the feature off in Settings to stop scheduled checks. Your phone can delay or prevent checks; these notifications are supplemental and are not an immediate emergency warning service.

Feedback and reports you choose to share

Feedback is optional and is unavailable when the local age choice is Under 13 or Prefer not to answer. Android and iOS builds with direct feedback enabled use the same hosted service and retention rules. When Submit feedback is available, it sends only after you review the report and tap Submit. The HTTPS service receives your message, category, optional reply email, diagnostics you chose and a random ID for that draft. This information helps us respond, investigate faults and consider requests. Feedback is not anonymous: your message or email may identify you, and the hosting service receives your IP address and connection information. A reference confirms server receipt, not inbox delivery or a reply. Failed drafts stay in the open editor; no automatic retry or background submission is performed.

The private application queue encrypts report contents while waiting to send them to support@sonnyandrobo.com. It removes those contents when the SMTP server accepts the email for delivery. Acceptance does not prove that the message reached the inbox or that a resulting email was deleted. Unsent queue contents expire 72 hours after receipt and are removed by the scheduled cleanup job. A stopped job can delay removal; new submissions pause when its health check becomes stale. Receipt IDs, keyed content hashes and processing states expire seven days after receipt. Keyed IP counters expire at the end of their current hour or UTC day, and mail-attempt counters after 24 hours; cleanup removes expired counters. The application queue stores no raw IP addresses. These limits apply to active application records, not delivered email, hosting logs or backups.

Feedback drafts stay in the current app session. Copy feedback places the reviewed text and any diagnostics you chose on the system clipboard; your keyboard or clipboard sync service may retain a copy. Copy email address places only the support address there. Neither copy action sends the report. You choose whether to include diagnostics, review the contents, and finish sending in your email or sharing app. That recipient receives your message and any included report. Email also reveals your sender address and may reveal your name. Your message may contain personal information you type yourself. Sharing a forecast or alert sends the content you choose to the chosen recipient under the sharing service’s policy.

Optional feedback diagnostics add app/build and operating-system versions, manufacturer/model, rounded memory capacity and up to 10 recent sanitized error groups. The local journal uses fixed error categories, timestamps, repeat counts, stack locations and provider/status codes. It excludes raw error messages, saved places, coordinates, search text and weather responses. The manual diagnostic attachment adds no persistent device identifier. Review it before sending.

Feedback accepted for delivery goes to the support mailbox. Messages that reach it remain there until deleted under the publisher’s mailbox practices; deleting a queue record does not delete the email. We use support correspondence to respond, investigate problems and consider requests. Our policy is to delete resolved support and privacy correspondence 12 months after resolution. This is a mailbox-management practice, not an automatic app timer or a promise about provider logs and backups. You can request access, correction or deletion at support@sonnyandrobo.com, including a feedback reference or approximate date if available. Local app deletion cannot recall a message you already sent.

Hosting logs, backups and provider retention

Hostinger hosts sonnyandrobo.com and its feedback service. Hosting systems automatically generate access logs and may keep separate error, security and backup records. These can include IP addresses, request times, requested resources, device/browser information from request headers, country, sizes, response times and status. They support delivery, troubleshooting and abuse prevention. StormBeacon sends feedback contents in a POST body, not URL parameters, and does not add messages, reply email addresses or diagnostic payloads to its application logs. Host-level handling of request bodies and headers is separate and has not been confirmed for this account. The older warning-graphics endpoint is retired; older apps may still contact it.

Support email also has separate delivery logs, mailbox-access logs and provider recovery or backup copies. Public mail-routing records identify Hostinger Email as the receiving service for support@sonnyandrobo.com. This does not establish forwarding settings or deletion periods for every infrastructure copy. Dashboard viewing windows and customer-visible recovery periods do not establish deletion dates for every infrastructure copy. We have not confirmed this account’s complete logging, backup, processing-location or subprocessor details.

Deleting active queue or mailbox records may not immediately remove copies in provider backups or security systems. A private hosting directory and queue encryption do not keep those files or their encryption keys out of backups. Hosting and email providers control those copies under applicable terms; we do not promise a particular infrastructure deletion period or U.S.-only processing. Restored feedback must be reviewed before processing resumes so deleted or previously sent messages are not automatically made active again. Contact support@sonnyandrobo.com for deletion requests, including requests that need help from the provider.

Other weather, map, address, image and optional office-feed services have their own logging and retention practices. Their records can outlast StormBeacon’s local caches. Philippines services and FreeLightning are excluded from the launch edition; they are not active recipients in that edition. Provider policy links appear below; clearing StormBeacon cannot erase independent providers’ records.

Optional automatic error reporting

Automatic error reporting is not connected in the current public release. In builds that offer it, reporting is off by default. If available and you enable it, hosted Sentry receives app errors and native crash/hang diagnostics to help fix faults. Native reports can include technical device/OS details, stack traces and SDK installation identifiers beyond the local report preview. Sentry also receives your IP address as connection metadata. The app does not attach saved places, application storage or notification contents. Screenshots, session replay, breadcrumbs, console logs, advertising and performance tracing are disabled.

Native crash reports can be buffered and sent on a later launch with reporting enabled. Turning reporting off stops collection and sending after the SDK closes; it cannot recall in-flight or delivered reports. Clear reports removes the app’s local journal, not Sentry’s separate pending buffer or hosted reports. Hosted retention depends on the configured Sentry project. When this feature is available, the published privacy policy provides the hosted retention period and contact for requests about received reports.

Your controls and deletion

Use Settings → Delete saved places and weather data to remove persisted places, cached forecasts, weather preferences, notification history and the local error journal, and turn automatic reporting off. The separately stored appearance theme remains. Clear reports deletes only the local journal. Uninstalling removes app-local data and buffers; copies already exported, sent or retained by external providers remain subject to their policies.

You can request access, correction or deletion of information held by the publisher, or withdraw optional reporting consent. Depending on where you live, additional rights may apply, including making a complaint to your local privacy authority. The publisher may need enough information to locate a message or report; do not send passwords or unrelated identity documents. The publisher cannot directly delete independent providers’ records. Use their published privacy contacts for those requests.

Security, external services and future changes

The app’s weather, map, address and hosted-reporting connections use HTTPS. No service or device can guarantee absolute security. Email and sharing delivery depend on the app and provider you choose. External providers may process information in countries other than yours under their own policies.

On iOS, StoreKit checks your App Store storefront on-device to make external support links available only for the United States. Unknown storefronts keep those links unavailable. StormBeacon does not send this storefront value to its feedback service or use GPS, language or IP to infer payment eligibility. Where available, optional Buy Me a Coffee and PayPal support buttons open their services outside StormBeacon. They receive your connection information and handle checkout and information you submit under their own policies. Opening Settings does not contact them, and the links do not include saved places, coordinates or diagnostics. StormBeacon has no payment SDK or payment-card collection. Contributions do not unlock app features. Review the amount and any recurring-payment choice with the provider before paying. Future paid feeds, accounts or purchases will need updated notices and store disclosures before launch. These links are unavailable when the local age choice is Under 13 or Prefer not to answer.

This notice will be updated when the app’s practices change. Weather, radar and alerts can be delayed or unavailable. StormBeacon is independent and is not an official NOAA or government app; follow official emergency instructions.

Provider policies and information

Website privacy · Back to top