The book is the merchant's

The sales history an AnKedai merchant keeps is the merchant’s own record — stock, sales, credit (utang) and expenses — stored so a small business can finally read its own day back. It is not a profile we build about you. An individual’s books are never exported, sold, or used to train anyone else’s campaign, pricing or advertising.

AnKedai does not hold, move or lend ringgit. Settlement rides DuitNow rails through Bank Negara Malaysia-licensed acquirers and partners. AnKedai sees that a sale happened so the ledger balances; the funds themselves pass through rails operated by licensed institutions — the Patricia doctrine applied to the micro-merchant, so there is no float of ours to risk with yours.

Where market-level numbers are published at all — for example cohort price signals that flow to AnHarga and, in aggregate, to KPDN — they are opt-in per cohort, k-anonymized, and carry floors so no single kedai can be reverse-engineered from a figure. There is no join key that links an aggregate back to an individual merchant’s books. This is the same no-join-key doctrine that runs across every Antrex product.

When AnKedai drafts and submits an e-invoice, it does so from the sale already in the ledger and sends only what LHDN’s mandate requires, to LHDN, on the merchant’s behalf. The compliance trail is the merchant’s to keep; AnKedai does not repurpose invoice contents for anything other than filing and reconciliation.

AnKedai inherits the AnKampung offline state engine: entries post on the device and sync on reconnect. A pasar-malam pitch with no signal keeps its working book locally. Sync exists to reconcile the merchant’s own ledger and enable their chosen surfaces — not to collect location or behavioural telemetry for its own sake.

During pilot-scouting, participating merchants, markets and campus vendors are named only with their consent. Pilot results are reported without identifying any individual merchant, trader or institution that has not agreed to be named — anonymity for the first cluster is a privacy rule, not a suggestion.

To exercise access, correction or deletion rights, or to ask how any field above is implemented, write to ankedai@antrex.app or use the Antrex contact desk at antrex.app/contact.