# Refinery

> Refinery checks operational data before an approved AI system or workflow uses it. Trusted data passes, uncertain data is limited or blocked, and eligible repairs are verified in the source before they are called fixed.

Canonical website: https://getrefinery.nl/
Contact: noreply@getrefinery.nl
Status: Controlled PostgreSQL-first design-partner conversations. Refinery is not generally available.

## What Refinery does

Refinery is a purpose-bound, read-only Verified Data Gateway between operational systems of record and AI or workflow consumers. It is designed to:

1. Bind every data request to an approved consumer, purpose, source, and field scope.
2. Read current operational data and check freshness, completeness, identity, evidence, classification, and policy.
3. Return trusted data, return explicitly limited data, or block unsafe and uncertain data with a reason.
4. Detect and prioritize important invalid, missing, stale, duplicate-like, or conflicting values.
5. Route only eligible low-risk issues through explicit policy or human approval and a governed connector path.
6. Verify an allowed repair through exact fresh source readback and a durable receipt.

Core rules:

- A gateway request is read-only and cannot execute a repair.
- Refinery never calls a record fixed without a governed write, exact fresh readback, and durable receipt proof.
- Source systems remain authoritative.

## Current boundaries and honest claims

- The public website is an MVP information site, not a product login or live customer application.
- The current commercial scope is PostgreSQL-first and approval-first.
- Refinery does not claim universal connector coverage, general availability, a public SLA, formal certifications, customer counts, reviews, or proven customer outcomes.
- AI may help analyze evidence and prepare recommendations, but it is not independent approval, write, execution, or proof authority.
- Identity conflicts, destructive changes, ambiguous financial facts, unsupported connectors, and stale or conflicting evidence remain held or blocked.
- Customer data remains in source systems by default. Customer-data training is not enabled by default.

## Canonical pages

- Home and plain-language product definition: https://getrefinery.nl/
- How Refinery works: https://getrefinery.nl/product/
- Trust posture and current boundaries: https://getrefinery.nl/trust/
- Company focus: https://getrefinery.nl/about/
- Design-partner use-case check: https://getrefinery.nl/pilot/
- Privacy notice: https://getrefinery.nl/privacy/
- Website terms: https://getrefinery.nl/terms/

This file is a concise factual aid for systems that choose to read it. The visible canonical pages remain the authoritative public source.