Pathreto Konkret
Privacy

We run the software. We cannot read your records.

A company's internals — what it sells, to whom, at what price — are its own. We do not provide them, we do not have them, and the system is built so we cannot reach them. This is what that means in practice.

What we can see

Only what it takes to run the service and keep it healthy. All of it is a number or a setting.

  • How many accounts a company has, and how many are active.
  • How many roles there are, and how many things each may do — never who is in them.
  • How many tables the software holds for it, how many rows, and how large the database and the stored photos and documents are.
  • Whether the software is answering, and how quickly.
  • Which fixes, additions and upgrades are switched on for it, and which plan it is on.

What we cannot see

A company's internals are forbidden to us, and the system is built so they are out of reach, not just out of bounds.

  • Orders, customers, salespeople, contractors, prices, ledgers, invoices, mixes, casting or slab sheets: no record of the business.
  • What anything is called, what it costs, who bought it, or how much was sold: those are the company's internals, and they are not ours to see.
  • A password. Passwords are kept as salted hashes that cannot be turned back into the password, by anyone.
  • The key that locks a company's records. It lives with the company's own software, not in this console or this portal.

How that is kept true

01

Locked before it is saved

The business details in a record — names, amounts, descriptions, notes — are encrypted by the software before they reach the database. What the database holds is ciphertext.

02

The console is built without the key

The console that runs the platform reads and writes settings and counts only. It has no key to the company's records, so even with full access to the console there is nothing to read.

03

Counts, never contents

When the console asks a company's software how it is doing, the answer is numbers. A role is “role 1”, “role 2”: how many people, how many permissions. No names, no values.

04

Secrets are shown once

A temporary password is made, shown to the person it is for, and only its hash is stored. If it is lost, a new one is made; the old one cannot be read back.

05

Each company on its own

Companies do not share records. A portal account belongs to one company and reaches only that company's own page of settings and numbers.