Yesterday stays yesterday.
What your teams record, nobody can rewrite afterwards. Not your manager. Not your head office. Not us. That is not a setting and not a subscription tier. It is how the thing is built.
What Brikx records holds up
These four pillars give you an honest picture, every day, of what your teams actually do. And when someone else asks, such as a food safety inspector, a franchisor, an insurer or your own procurement department, you can show it with confidence.
Unchangeable
Nothing is overwritten
What has been recorded stays until your own retention period expires. A correction is placed next to what was there, never over it. There is no way to change or delete a completed task. Not by your manager, not by your head office, not by us.
Searchable
Who changed what, and when
Who changed this task, when, and from which value to which one? It is not scattered through a log file but searchable per zone, per task and per period. You ask for it when you need it, and it is there straight away.
About us as well
Supplier access
When our support helps you and we act on behalf of one of your users, that lands in the same trail as everything else: who, when, on whose behalf, and what was done. Nobody can look in unseen.
Protected
Photos and data
Photos are kept strictly separate per zone, never on a public address, and can only be opened through a link that expires shortly afterwards. The hidden location data that a camera writes into every photo is removed before the photo is stored.
Where your data sits
The database, the application and the storage of your files all run with European suppliers.
Kept strictly separate per zone, never on a public address, and openable only through a link that expires shortly afterwards.
A camera quietly writes into every photo where it was taken. Brikx removes that before the photo is stored, so a photo from your warehouse does not give away where your warehouse is.
Available on request, and tailored on Keystone.
How long we keep things
Those periods apply in every package, the cheapest one included. We could have made a selling point of it by keeping less on Base, but then the customer with the smallest budget ends up with the weakest record, and that is exactly the customer least able to judge what that risk is worth. Keeping things longer is available, and on Keystone you set the period yourself.
The retention period is also the only route by which anything leaves the system, and it is enforced by a background job that does a dry run before it clears anything.
Uptime
StatusThat is at most three hours and thirty-nine minutes of downtime a month. If we miss it, a credit follows automatically on the next invoice without you having to ask, because a guarantee you have to chase is not a guarantee.
| Measured uptime | Credit |
|---|---|
| 99.0% – 99.5% | 10% |
| 95.0% – 99.0% | 25% |
| below 95.0% | 50%, and the right to terminate immediately |
Excluded are announced maintenance (notified at least 48 hours ahead, outside 07:00 to 22:00, at most 4 hours a month), force majeure, and faults in your own network. The real figures per day and per month are on the status page. Nobody believes a standard without a public measurement, and rightly so.
And when there is no network?
Then it carries on working, on the screen on the wall as much as on a personal device. Sign-offs queue on the device and are sent the moment the network is back; the same action replayed twice never produces a double sign-off. An outage delays your record, it does not lose it.
Two things we do not promise
We are a small supplier. That is a real risk and you should hear it from us rather than have to work it out yourself. So the contract states that your data is exportable through the API at any time, that the contract itself is a published OpenAPI specification, and that source code escrow is open to discussion at chain scale.
We have no ISO certification. What we do have is a security pack that answers every question with a concrete answer instead of a badge. Ask for it; it is written to be read by your IT department.