Capabilities
Security and privacy themes
Security statements here are design intent. The launcher and the customer app have no code to audit, the packaging tool has not been audited, and the site makes no certification claim of any kind.
Status
Planned Everything on this page is a plan. The repository contains a catalog and design documents, not a released app. Entries are tagged with their own status.
Local-first data
Data lives on the shop's own devices by default; nothing requires a cloud account.
Read →DesignedNo telemetry
The README states no telemetry or data collection.
Read →PlannedRoles and permissions
Giving cashiers, supervisors and owners different rights, and limiting risky actions..
Read →PlannedAudit trail
An append-only record of edits, voids, discounts and logins is planned.
Read →Not decidedEncryption at rest
Protecting the database file on a lost device.
Read →PlannedBackups
Local backups to drives or another device, with restore tests..
Read →PlannedRestore
Rebuilding a device from a backup, checking integrity first..
Read →PlannedDevice pairing
Trusting a second device on the shop network..
Read →Built (repo)Signed files
Everything the launcher installs is signed: packages, update manifests, entitlements, the catalog snapshot and price documents.
Read →PlannedData minimisation
Only collecting what the sale needs, with customers' details optional..
Read →PlannedPINs and sessions
Quick staff logins that time out safely..
Read →Built (repo)Secure updates
Updating without a mandatory internet connection, with rollback.
Read →DesignedSoftware supply chain
Building and signing releases and checking dependencies.
Read →DesignedSecurity model and threat model
A written security model exists in the repository: assets, attackers, eight rules (true removal, signed everything, local authority for offline use only, online features decided by the host, no hidden doors, staging discipline, break-in tests, an honest limit) and a table of what is built and what is not.
Read →Built (repo)True removal of unselected elements
A package holds nothing for elements outside its spec: no code, assets, migrations or data tables, and hiding by a flag does not count.
Read →Built (repo)No hidden doors
Rules enforced by tests: no demo or default keys, no default network binding, no runtime CDN or remote asset loads, no founder or vendor accounts, no auto-start, and no hidden start path.
Read →DesignedStaging discipline
Release rules from the security model: snapshots first, data never moves with code, a backup before any data-touching change, test on a copy, one stage per release, the previous build kept for real rollback, and ledger and customer data last.
Read →Built (repo)Removal audit chain
Each removal decision is written to a local log in which every entry commits to the previous one, and the current state is cross-checked against the chain.
Read →