Skip to content
VAULT_OS

Privacy policy

Your data stays on your hardware.

What IronGap Technologies collects through this website, and what Vault-OS does with your data once it is installed: nothing that leaves the machine.

Effective 14 August 2026 · Updated 22 October 2026

The principle

Your data never leaves your physical hardware. Vault-OS is installed on premises and runs offline. We do not collect, monitor, inspect, transmit or monetise your documents, model outputs, chat transcripts, embeddings or user identities. Once deployed, the appliance has no outbound connection.

Scope

This policy covers IronGap Technologies’ web services (iron-gap.com, the client portal and licence administration) and the operating principles of the Vault-OS appliance.

Unlike cloud AI services that process your prompts on their servers, Vault-OS runs entirely on your own machine: bare metal, a hypervisor you control, or our sealed appliance.

What the website collects

We collect only what we need to answer you, run a pilot and issue a licence:

  • Contact and pilot requests. What you type into the form (name, email, company, message, the tier you are interested in), used to reply to you.
  • Account information. Name, work email, company and role, if you have a client portal account.
  • Portal passwords. Stored only as salted hashes; the plain password is never stored. Your Vault-OS master password never reaches us in any form.
  • Google sign-in. If you use it, we receive your email address and verified name to sign you in. We do not request access to your Drive, contacts, mail or files.
  • Hardware fingerprints. The identifiers you send us at activation (such as the TPM endorsement key or system UUID), used only to sign your offline licence.

There is no card form on this site. Invoices are paid by bank transfer, so we hold no payment card data.

Inside Vault-OS

Documents and embeddings

Everything you ingest is indexed into the local PostgreSQL/pgvector database inside an encrypted volume you hold the password to. There are no cloud copies.

Models

Models such as Llama, Mistral, Qwen, DeepSeek or Gemma run on your own hardware through VEYMEER, Ollama, vLLM or TensorRT-LLM. Nothing is reported to the model makers or to us. The installer carries no models; you choose them.

Embeddings, vision and offline speech recognition come as an optional support package beside the installer.

The burn protocol

Vault-OS includes an authorised cryptographic erasure, the burn protocol. Once confirmed, it:

  1. Ends every session immediately.
  2. Deletes every document, chat message, embedding and index from the database.
  3. Removes the stored files from disk.
  4. Destroys the encryption keys, so the remaining storage cannot be recovered, even forensically.

Regulation

Because Vault-OS sends no data to a cloud, it removes the hardest part of most data protection obligations. Compliance still depends on how you run it.

  • GDPR. Supports data localisation and purpose limitation, and the right to erasure (Article 17) through the burn protocol.
  • HIPAA / HITECH. Protected health information stays on your clinical network, with no cloud business associate in the path.
  • KVKK. Personal data stays in the country and on your own hardware, with no cross-border transfer to approve.
  • SOC 2 and ISO 27001. No external dependencies, an immutable audit ledger and role-based access control to build your controls on.

Subprocessors

IronGap Technologies does not sell, rent or share customer data, in any circumstance.

For this website and the portal we use: Vercel (hosting), Supabase (portal data and sessions), Resend (transactional email) and Telegram (notifying us when you send the contact form). None of them has any access to a Vault-OS installation.

Your rights and contact

You can inspect, correct, export or delete the account data we hold about you. To do so, or to ask a question about this policy, contact us:

Organisation
IronGap Technologies
Email
info@iron-gap.com
Form
iron-gap.com/contact