Scope and access
Hearth-v2 is a private household application. Protected APIs require a verified identity that resolves to an authorized household membership, and production fails closed when authentication is not configured. There is no public sign-up or acquisition route on this site.
Development identity is a non-production testing facility and cannot be enabled in production. Hearth-v2 records are directly household-scoped or belong to a household-scoped parent.
Data and optional providers
Hearth processes the records you choose to keep for home maintenance, inventory, yard, garden, pool, recipes, costs, shopping context, and supporting photos or documents. Optional AI, weather, and geocoding providers are feature boundaries rather than startup dependencies.
| Data or control | Where it lives | Export or backup | Deletion and retention |
|---|---|---|---|
| Account and household membership | Hearth-v2 resolves verified Microsoft Entra/OIDC identity to an app-local user and household membership. | The audited source does not establish a public self-service account export. | Provider identity and app-local membership are separate. No public account-wide deletion or retention promise is established yet. |
| Household and property records | Maintenance, inventory, yard, garden, pool, recipe, and dashboard records are household-scoped in a migration-managed SQLite database. | Keep independent originals of records or evidence that must survive outside Hearth. | Owned record APIs support deletion, but backup expiry and account-wide erasure are not represented as complete public controls. |
| Photos, documents, and reports | Authorized durable blob storage holds supported maintenance, warranty, receipt, inventory, and pool-report evidence. | The audited source does not establish a complete public bulk-media export. | Unreferenced blob deletion is supported; storage-provider retention can continue under its own operational and legal rules. |
| Optional provider requests | Chosen recipe-AI, weather, or geocoding features send only the request needed to the configured provider. | Review and save useful results into your own records; unsaved recipe drafts are not persisted by Hearth. | Provider logs and retention follow the selected provider’s terms. Optional providers are not startup requirements. |
Scroll horizontally to read all four columns →
Current controls and known limits
Hearth supports household-scoped record operations, strict validation, and authorized blob access. The audited source does not establish a public self-service account export, account-wide deletion flow, fixed retention schedule, or completed legacy-data cutover. This policy does not imply those controls exist.
Legacy import is a separate, explicit operator action from a read-only snapshot. It is not a background migration, and the superseded runtime is not marketed here as the current product.
Questions and requests
Privacy questions can be sent toprivacy@nintek.com. General product questions can be sent tohello@nintek.com. Use of Hearth is subject to the Nintek Terms of Use.
Evidence note. Scoped to Hearth-v2 source at 6c9a7922884c41813acd918b3fba395f8c447e9b. Public release, account-wide deletion, retention, and bulk-export controls are not claimed beyond that source.