Trust Center

How we protect company data

What Hiram Trade does to protect company data, and where it is enforced. Each statement below describes a mechanism that exists in the platform.

The statements are limited to mechanisms that exist in the platform today. Where something is not listed, this page makes no claim about it.

Last reviewed: November 6, 2026

Data isolation between companies

Company data is isolated between companies. Every query for company-private data carries an authorization scope taken from the signed-in session, and a company identifier sent by the browser is never accepted as proof of access. Automated tests check that one company cannot read or change another company's deals, RFQs, quotes, inspections, disputes or listings by identifier.
The application connects to the database as a role that owns no tables, so it cannot alter table structure or disable triggers. Schema changes are made only through versioned migrations run under a separate identity.
Counterparty identity and contact details stay hidden until the disclosure rules allow them. By default a counterparty sees an anonymous profile until a connection is accepted, and direct contacts are shown only once a deal is agreed. The rules are enforced on the server.

The audit log is append-only. Updates, deletions and truncation of audit events are blocked by database triggers, and the application's database role has those privileges revoked.
Sensitive state changes, such as deal transitions, write an audit event in the same database transaction as the change itself.
Quote versions, deal terms, deal events and the deal payment register cannot be updated or deleted. A change is recorded as a new row, so earlier versions remain.

Analytics and marketing storage is off until the visitor opts in. No box is pre-ticked, and the choices to accept all and to reject all are presented with the same size and style.
Each cookie consent choice is recorded as proof: policy version, choice, language, page path, browser family and, at most, a keyed hash of the IP address. The IP address itself is not stored. Records are kept for five years, and the link to the user is cleared when an account is anonymised.
Acceptance of the Terms and other legal documents is recorded per user with the document version, language and time. These records cannot be altered or deleted by the application.
Users can request an export of their data and delete their account, and company administrators can close a company. Deleting an account anonymises the user record. Records that must be retained, such as evidence of accepted legal documents, are kept for the period stated in the Privacy Policy.
Read the Privacy Policy

AI-assisted features produce drafts. AI output never sends messages, accepts terms or commits to commercial terms; a user reviews and approves it first.

The production database is PostgreSQL hosted by Supabase in Frankfurt, Germany (region eu-central-1). The application connects to it over TLS and verifies the server's identity.