Trust & data protection
Security that starts at the database, not at the login screen
Mining data is commercially sensitive: production volumes, costs, customers, prices, tonnages and people. CoreMS is built so that a user only ever receives the records they are entitled to — the filtering happens inside the database, before a single row leaves it.
Row-Level Security: data is filtered before it is retrieved
Most systems fetch data first and then decide what to hide on the screen. That means the information has already travelled to the device, and anyone able to inspect the traffic can read it.
CoreMS uses PostgreSQL Row-Level Security. Every table carries policies that are enforced by the database engine itself on every single query. When a user asks for "orders", the database rewrites the request against their identity and returns only the rows their policy permits. Rows outside their scope are not hidden, not filtered on the phone, not sent at all — they never leave the server.
The rule applies identically to the app, a report, or a direct API call, because it lives with the data rather than in the interface. A user who tries to request another site's records simply receives nothing.
What that looks like in practice
- Transporters assigning trucks in CoreLoad see only their own trucks, for the one customer and one site they were allocated to.
- Site staff see only the sites they are assigned to — a supervisor at one operation cannot query another operation's production.
- Customers receiving loads in CorePort see their deliveries, not your fuel burn, costs or other customers.
- Tally clerks and operators get a deliberately narrow screen and an equally narrow data scope.
- Management sees across sites in CoreView because their role grants it, not because the app decided to show more.
Platform security
Enterprise PostgreSQL, managed and monitored
Every app runs on a managed PostgreSQL platform (Supabase) with automated daily backups, point-in-time recovery, and monitored uptime. There is no server in a container on site to be stolen, unplugged or forgotten about.
Encrypted in transit and at rest
All traffic between a handset and the platform runs over TLS. Stored data and file attachments — photos of meters, seals, licences and job cards — are encrypted at rest.
Identity and role-based access
Each user has their own authenticated account with a defined role. Roles are held in a dedicated permissions table on the server, never in the browser, so a user cannot promote themselves by editing anything on the device.
Separate databases where separation matters
CorePort runs at the customer's destination against its own database holding only the load information that destination needs. A breach of one environment cannot expose the mine's production, cost or payroll data.
Continuous security auditing
Every deployment is scanned for exposed tables, missing policies and misconfiguration, and findings are cleared before release. Dependencies are scanned for known vulnerabilities on an ongoing basis.
A complete, unalterable audit trail
Transactions carry the user, timestamp, GPS position and supporting photographs. Records are appended, not overwritten, so any fuel, load or weight can be reconstructed exactly as it was captured.
Security on the handset itself
The apps can be deployed on managed devices that are locked down to the CoreMS apps and phone services only. The device becomes a purpose-built instrument rather than a phone somebody happens to work on.
Locked device profile
Only the specified apps and phone services are available. No browsing, no messaging apps, no camera roll to export photographs of your operation.
Geo-zone control
A device leaving its designated geo-zone raises an alert and can be locked, which matters for bowsers, weighbridge tablets and gate handsets.
SIM removal detection
Removing or swapping the SIM is detected and reported, so a device cannot be quietly repurposed or taken off the network.
Want the security detail for your IT team?
We will walk through policies, roles and hosting with them directly.