Design stage: there is no released app yet. This site separates what exists in the repository from what is planned. See status

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.

Designed

Local-first data

Data lives on the shop's own devices by default; nothing requires a cloud account.

Read →
Designed

No telemetry

The README states no telemetry or data collection.

Read →
Planned

Roles and permissions

Giving cashiers, supervisors and owners different rights, and limiting risky actions..

Read →
Planned

Audit trail

An append-only record of edits, voids, discounts and logins is planned.

Read →
Not decided

Encryption at rest

Protecting the database file on a lost device.

Read →
Planned

Backups

Local backups to drives or another device, with restore tests..

Read →
Planned

Restore

Rebuilding a device from a backup, checking integrity first..

Read →
Planned

Device 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 →
Planned

Data minimisation

Only collecting what the sale needs, with customers' details optional..

Read →
Planned

PINs and sessions

Quick staff logins that time out safely..

Read →
Built (repo)

Secure updates

Updating without a mandatory internet connection, with rollback.

Read →
Designed

Software supply chain

Building and signing releases and checking dependencies.

Read →
Designed

Security 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 →
Designed

Staging 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 →

Questions

Is Simca certified?
No. No PCI, SOC 2, HIPAA, GDPR or EMV compliance is claimed.
Does it collect telemetry?
The README states a no-telemetry principle. It is a design principle, not a measured property of a shipped app.