Different features, different data.

Public power reports

When you submit a report, its location coordinates, power status, optional source (grid, generator, or solar/battery), and submission time are used to build public neighborhood zones. Reports and resulting zone summaries can be viewed by other visitors. Do not submit a report if you are not comfortable making that location and status public.

A short-lived report token helps reduce repeated weighting from the same browser. Its temporary duplicate-vote ledger lasts six hours and is separate from visit counting. Repeat votes may be down-weighted in the recent-status calculation; this token does not make a report private or prove a person’s identity. Temporary anti-abuse checks use an in-memory rate limit; IP addresses are not stored with report or visit records.

Zone likelihoods are based on eligible community reports, with a six-hour fresh window and historical fallback when reports are stale. They are not an official NEPA or distribution-company reading.

Anonymous visit counts are separate

A random browser-held visit identifier is used only to count visits. It is not joined to report coordinates, report status, saved places, local profile totals, or quote requests. UpNepa does not use it to build a location trail.

Optional private place alerts

If you explicitly enable alerts, the selected place coordinates and browser push subscription are stored separately so UpNepa can send an alert after a qualifying fresh status change. You can choose a listed area or press “Use my current area”; device location is requested only after that click, and the coordinates stay in the form until you save the alert. There is no background location tracking. Browser notification permission is requested only after you choose to enable it. Place labels such as Home and Office are stored only in this browser’s IndexedDB and are not sent to the alert service.

Alerts are limited per saved place over a rolling hour. A browser push service chosen by your device processes delivery. The notification contains a place label and a power-change message. You can remove one place or unsubscribe from all places at Alerts.

Device-local features and offline data

The optional profile stores only a successful-report total and reporting dates on this device; badges and streaks are calculated from those aggregates. Source preference, install eligibility, and the next-visit reminder are also device-local. They are not account records and reset if browser storage is cleared or you change devices.

After an online visit, the service worker can keep a bounded snapshot of public aggregate map and zone responses for offline use. It does not cache report submissions, alert-management calls, private admin data, or quote forms. Snapshot figures are labeled as last known and may become stale. Map tiles are separate: tile requests go to the OpenStreetMap tile service, which may receive your network address and browser connection information. Basemap tiles are not bulk-downloaded for offline use.

Optional quote requests

Quote requests are currently disabled. UpNepa does not accept lead details while the server feature flag is off.

Sponsorship and third parties

Sponsorship placements and their event tracking are currently disabled by the server.

Map tiles and browser push delivery are provided by third-party services. Those services may receive connection details as your browser makes requests to them.

Questions or privacy contact

No privacy contact has been configured for this service.

For changes to optional data, remove alert places in the Alerts page and clear device-local profile or browser storage. Public reports remain community data and are not removed by resetting local recognition.