Goodhills-Me Namazu
Namazu Mobile Privacy and Data Boundary
This page explains how Namazu mobile and API receiver data is handled in the current Goodhills-Me web-side implementation.
Data handled
Current mobile/API receiver data
Account dataGoodhills-Me login connects Namazu buildings, API keys, checklist status, notification preferences, and tensor jobs to the account.
Building profileUsers may enter building nickname, area/address, structure, floor count, usual floor, role, and notes. Many fields are optional.
Shake samplesThe receiver can store timestamped XYZ acceleration samples, device label, optional floor, optional location fields, sample rate, sample count, and payload hash.
API keysRaw Namazu API keys are shown only once when created. The server stores hashes and prefixes so keys can be checked and revoked.
Tensor jobsReviewed input can be queued for baseline-shake preparation and Namazu building tensor generation through the worker path.
Boundaries
What Namazu does not do now
Emergency alertsNamazu does not replace official emergency alerts, JMA, local government, police, fire, or emergency instructions.
InsuranceNamazu does not sell, underwrite, rate, recommend, approve, or decide insurance.
Wallet/chainThe mobile receiver does not connect wallet private keys, chain settlement, or token ledger execution.
Source codeUnreviewed outside tensor-generating logic is not executed in the public web request path.
Official decisionsNamazu records and simulations are support information, not official government, engineering, or emergency-service decisions.