Home / How it works

How it works

How Auditrek will do it, step by step.

How it will work

What using it will look like

Auditrek is not open yet, so these steps are the order it is planned to work in, not a sequence to start here.

  1. Record the agreement first

    Add an AI system and record its data processing agreement confirmation. Until signed_at exists on that confirmation, the connect endpoint returns 403 and issues nothing.

    Auditrek: Record the agreement first
  2. Take the credentials

    With the DPA recorded, connecting the system issues an API key and a webhook secret scoped to that system. Store them in your secret manager.

  3. Post inference events out of band

    Your pipeline posts input hash, model id and version, output, confidence, timestamp and human override flag to the REST endpoint or fires the webhook.

  4. Watch the chain hold

    Each accepted record takes the next sequence number and a hash computed from the previous record. Run verification on any record and the server recomputes the chain from sequence 1 and tells you where it breaks, if it does.

  5. Generate the record for a date range

    Pick a system and a period, and Auditrek renders PDF and HTML output structured against EU AI Act Article 12 and 13 fields, disclaimer included, ready to hand to counsel or an auditor for their own assessment.

For what it covers, see the pages this site publishes.

Append-only decision records

An async REST and webhook API accepts inference event payloads: input hash, model id and version, output, confidence, timestamp, human override flag.

A dashboard a non-engineer can read

Decisions logged, systems connected, last report generated, and current tamper-verification status, written for a compliance officer rather than for the engineer who owns the pipeline.

Questions

Answers before you ask

Does Auditrek make us compliant with the EU AI Act?

No, and we will not say otherwise. Auditrek produces structured records and documentation designed to support Article 12 and 13 record-keeping and transparency obligations. Whether your programme satisfies those obligations is a determination for your own counsel and your supervisory authority. Every report we generate carries a footer stating that the output does not constitute legal advice and has not been reviewed by qualified regulatory counsel.

Does Auditrek sit in our inference path?

No. Ingestion is async and out of band, over REST or webhook. Inline critical-path middleware is explicitly out of scope, so an outage or slow response on our side does not stall a production prediction.

Do we have to migrate or re-serve our models?

No. Auditrek takes an inference event payload over a documented generic REST and webhook schema, with field mapping guides for AWS SageMaker and Azure ML. There is no SDK to embed and no bespoke platform agent at launch.

What exactly is hashed?

Each decision record is written with a sequence number and the previous record's hash, and the stored hash is sha256(prev_hash + payload), all committed atomically. Verification recomputes the chain from the first record rather than trusting a stored status field.

What happens to sensitive fields in our payloads?

The ingestion API inspects payloads for recognisable raw sensitive-field patterns, such as SSN formats, ICD-10 style diagnosis codes and unredacted credit bureau fields, and rejects them with a 422 before anything is written. Subject identifiers are pseudonymised by default. Sending a raw sensitive field into the ledger is contractually prohibited unless you have confirmed your own lawful basis.

Can we connect a system before the paperwork is done?

No. A countersigned data processing agreement confirmation with a signed_at timestamp must be recorded before any API key or webhook secret is issued, and that check runs server-side on the connect endpoint.

Which regulations and formats are covered at launch?

One template, EU AI Act Article 12 and 13 fields, rendered as PDF and HTML. EEOC and HIPAA templates and custom report builders are out of scope until the first template has been exercised with real customers.

What does joining the waitlist mean right now?

Auditrek is pre-launch. Joining puts you in the first pilot cohort conversation, where we walk through the payload schema, the verification endpoint and a sample report against your own pipeline before anything is connected. No pipeline is connected without a countersigned DPA.

Join the waitlist

Leave your work email and we will send the payload schema, the verification endpoint documentation and a sample Article 12 and 13 report before you talk to anyone. Pilot cohort conversations start with your own pipeline, not a demo script.

One email when it launches, and one now to confirm your address. Unsubscribe any time. Privacy.