Repository navigation
Privacy
What NeroPower stores about players, and how to erase it. The full disclosure, including the
GDPR / POPIA basis, is in the repository's PRIVACY.md.
The UUID of the player who linked a Beam Transmitter or Beam Relay, saved in that block's own
data (the LinkOwnerMost / LinkOwnerLeast fields) inside the world save. It exists so that only
the linking player (or an operator) can break a beam link — nobody can re-aim your transmitter and
cut your base off. It stays server-side: world save only, and stripped from the block update
sent to nearby clients, so no client ever receives it. It is never a name, never a timestamp,
never logged, and it goes away when the link is changed, the block is broken, or you ask for
erasure.
While you are linking two endpoints with the Configurator, the server also remembers which block you picked first — in memory only, for at most 30 seconds.
A Fission Reactor's "owner" is NeroTech's own machine-owner field, stored only when a server admin turned on NeroTech's per-player pollution attribution (off by default). NeroTech documents and erases it; NeroPower only reads it to address failure events, gate remote actions and open the owner's quest milestone records (see Quest Chapter). Those records are player-scope gates in Neroland Core's progression store, covered and erased by Core's own privacy disclosure; an owner who opted out of attribution gets none.
- No usernames, IPs, positions, inventories, chat or statistics.
- Battery banks, RTGs, Stirling generators, receivers and scorch zones record no player at all.
- No analytics or tracking of any kind.
NeroPower sends anonymous error reports to its developers (Sentry, EU servers) when something in NeroPower's own code fails: the stack trace, mod / Minecraft / loader / Java / OS versions, your installed mod list and three NeroPower settings. Never a username, UUID, IP, coordinates or world data, and your account name is scrubbed from file paths. At most 10 reports per session.
It is on by default. To opt out, set telemetryEnabled=false in config/neropower.properties and restart. The full
details are in PRIVACY.md.
Neroland Core's shared erasure command covers every Neroland mod at once:
/neroland data eraseme # your own data
/neroland data erase <uuid> # operators
For NeroPower this drops your linking session and lists your UUID for link-owner erasure: every loaded transmitter you linked forgets you on its next tick, every unloaded one on its next load, and the list entry itself expires after 30 days. The beam link (which block it aims at) is world data and stays; only the player reference is removed.
If the server runs the NeroLink bridge, the app's NeroPower sections show only loaded machines within 128 blocks of you, in your dimension, while you are online — never a server-wide list. A transmitter or reactor with a recorded owner is shown only to that owner. Snapshots carry machine ids, positions, status and output figures, never a UUID or a name. The two remote actions — acknowledging a reactor alarm and SCRAM — work on a reactor you own from anywhere; on a reactor with no recorded owner (the default) they work only while you are online, in its dimension, within 128 blocks of it, and allowed to use that block by the server's protection rules. The server re-checks all of it itself.
Failure alerts are sent to a machine's owner only; for an unowned machine, only to online players within 128 blocks of it. They are never broadcast to everyone.