Privacy policy

Blacrex is operated by [legal entity name], [registered address]. Questions about this policy or about data we hold go to [privacy contact email].

Three kinds of information, and nothing else:

• Sign-in details. An email address and a password, held by our authentication provider. We never see the password — only a hash of it, which cannot be reversed.
• People records. The employees your organisation adds so equipment can be assigned to someone: name, employee number, department, work email, and which office they sit in. These people do not need accounts and usually have none.
• Asset records. Equipment, what it cost, where it is, who holds it, and the history of who held it before.

We do not collect payment card details, government identifiers, biometrics, location data from devices, or anything about your employees beyond what you enter.

Assignment history is append-only by design. Reassigning equipment closes the previous record and opens a new one rather than overwriting it, so the system can always show who held an item on a given date.

That is the entire point of the product — an asset register you cannot reconstruct is not evidence — but it does mean a person’s name persists in the record of equipment they once held, after they have left. If you need that removed, see Deletion below.

Each organisation’s data is isolated at the database level by row-level security policies, not by application code. A signed-in user issues queries that the database itself constrains to their own organisation, so a defect in the application cannot expose another organisation’s records.

Within an organisation, access follows the role you assign: viewers read, editors record equipment and movements, administrators additionally manage settings and membership.

We do not sell data, share it with advertisers, or use it to train anything. [Name your infrastructure providers here — for example the database and hosting vendors — and the countries their data centres are in.]

For as long as your organisation has an account with us, because an asset register is useful precisely in proportion to how far back it goes.

If you close your account we delete your organisation’s data within [retention period] days, except where we are required to keep something longer by law.

You can correct any record from within the application. For deletion of a specific person’s details from historical records — for example after an employee leaves and asks to be removed — contact [privacy contact email] and we will action it within [response period] days.

Note that equipment records are never hard-deleted through the interface. Retiring, disposing of or marking an item lost changes its status and the record remains retrievable, which is deliberate.

Data is encrypted in transit. Passwords are hashed by our authentication provider and are not recoverable by us or by you — only resettable. Access between organisations is prevented by database policy rather than by application logic, and that isolation is covered by an automated test suite that runs on every change.

No system is perfectly secure. If you believe you have found a vulnerability, please tell us at [security contact email] before disclosing it publicly.

If this policy changes materially we will tell account administrators before the change takes effect. The date at the top always reflects the current version.