Control that stops the losses you can't see.
Most money lost inside a business is not lost to hackers. It goes through a shared login, a quiet edit and a month nobody could reconstruct afterwards.
Huchu MineThe Gate ShopsLux LiquorStart with where the data lives. The rest of this page sits on it.
The drawer is US$40 short. Now what?
- Today
- Sell
- Stock6
- Customers
- People
- Pay
- Books
- Sites12
- Compliance
- Void after tender · sale #10199Rudo N. · 11:42 · reason recordedUS$4.00Look here first
- Opening floatCounted in by Tendai M. at 05:58US$200.00Agreed
- Drawer opened without a saleTwice, both with a manager present2Logged
A four-dollar gap is a question tonight, with three named candidates against it, instead of a mystery in three weeks with none.
Who was signed in, and how far they could go.
Everyone authenticates as themselves, so no action on this system is ever attributable to “the counter”.
Everyone authenticates as themselves. No shared logins, so no action is ever attributable to “the counter”.
- Sell · till 2, MsasaRing, tender, print, void before closeFull
- Stock · MsasaCount and receive. Cannot write off.Partial
- Customers · MsasaLook up a balance. Cannot change a limit.Read
Access is shaped by company, site and role, so nobody sees the whole business by accident.
A site manager may release up to US$2,000. This is US$6,224.10, so it stops here and waits for a named approver rather than asking anyone to remember the rule.
The software enforces the threshold. Nobody has to know the rule for the rule to hold.
Thresholds are enforced by the software, so a payout above the limit stops and waits for a named approver.
Every change keeps its author. The trail is a report you run, not a reconstruction.
- A change with no authorThere is no unauthenticated write path0None
- A change with no reasonThe field is not optional above a threshold0None
- A row that replaced anotherA correction is added beside what it corrects0None
When something goes wrong. A person, a device, or us.
- Sign-inWithdrawn 29 Aug 17:04 by Tendai M.Closed
- Handheld · KOR-0121Bound to the person, not the deviceSigns in to nothing
- Sessions endedOn every site and device, at once3Ended
Withdrawing a person closes what they can do next. It never touches what they already did, because an audit trail that thins out when staff leave is not one.
Their sign-in is withdrawn centrally the day they go, and every record they wrote stays exactly where it is.
Access belongs to the person, not the handset. Withdraw the person and the device signs in to nothing — there is nothing on it to wipe, because there is nothing on it to read.
- Sign inThe account it knew was withdrawn at 14:21No
- Read the last sales on itIts queue posted before the withdrawal0Nothing there
- Take a payment as the shopTenders are bound to a signed-in personNo
Access belongs to the person, not the handset. Withdraw the person and the lost device signs in to nothing.
- ReachesAn engineer
- Acknowledged withinOne working day
- You are toldWhat we are doing about it
- Reports that went unanswered0
No bounty programme and no certification we have not established. A named engineer, a real clock, and an answer in writing.
Report it to security@corelith.co.zw and it reaches an engineer, not a queue. We confirm receipt and tell you what we are doing about it.
The losses walk in the front door.They rarely come through the firewall.
Every action carries a name
No shared logins, so a question about last Tuesday has an answer rather than four people who might have been at that till.
The original is never replaced
A correction sits beside what it corrected. Both stay on the record, and both carry an author and a reason.
You keep all of it
A full export whenever you ask, audit history included, in a format you can read somewhere that is not here.
What you keep, and what we will not claim. Said plainly.
A full export whenever you ask, audit trail included, at no charge and in a format you can read somewhere else. We do not hold a business hostage with a proprietary format.
We do not market certifications we have not established. No compliance badges, no uptime guarantees, no payment-security accreditations on this page.
If a certification or a regulatory obligation matters to your organisation, we assess it explicitly during enterprise discovery and put the answer in writing.
Before you ask.
Corelith cloud runs on managed infrastructure. Exact hosting, region, backup and recovery commitments are confirmed for the service you buy rather than promised generically on a web page.
Yes. Access is shaped around the person, the company, the site, the role and the approval limit, so the workflow carries its own boundaries instead of relying on people remembering the rules.
The original value stays. The change sits beside it with the author, the time and the reason, so the history becomes more trustworthy over time rather than less.
Email security@corelith.co.zw. It reaches an engineer, not a queue. Tell us what you found and how to reproduce it, and we will confirm receipt and tell you what we are doing about it.
You export it, in full, whenever you ask — including the audit history. We do not charge for it and we do not hold a business hostage with a proprietary format.
We do not market certifications that have not been formally established. If a certification or regulatory obligation matters to your organisation, we assess it explicitly during enterprise discovery and put the answer in writing.
See who did what, and when.
We go through the controls your operation actually needs, and give you a straight answer on the ones we cannot yet claim.