Question 1

Is SART giving legal advice?

Accepted Answer

No. SART is decision support. Every recommendation must be reviewed and signed off by a named officer at the housing association. The statutory test under UK GDPR and the Data Protection Act 2018 is theirs to apply.

Question 2

Can SART auto-release a bundle?

Accepted Answer

No. The pipeline cannot export a bundle without a signed reviewer record. The system is architected so that the human is on the critical path by construction, not by policy.

Question 3

What if Agent 2 and Agent 3 disagree?

Accepted Answer

The disagreement is escalated to the reviewer's queue with both positions logged. Silent reconciliation is forbidden — the audit ledger always shows the dissent.

Question 4

Does SART train on our SARs?

Accepted Answer

No. SART does not train models on customer SAR bundles. The product is deployed on-prem; customer data does not leave the perimeter, and there is no cross-customer learning loop.

Question 5

Who is the data controller during a SAR?

Accepted Answer

Your housing association remains the data controller. SART operates as a tool inside your environment; it does not become a processor over your SAR bundles in the sense that creates new third-party exposure.

Question 6

Who is liable if a redaction is wrong?

Accepted Answer

Liability sits with the housing association's named reviewer who signed the redaction plan. SART supports that decision with reasoning and an audit trail; it does not displace the reviewer's statutory responsibility.

Question 7

What does the ICO see if there's a complaint?

Accepted Answer

The evidence pack: every passage's rule citation and reasoning, every reviewer action with name and timestamp, and the hash chain that proves nothing was edited after sign-off.

Question 8

Is SART ICO-certified?

Accepted Answer

No software is. The ICO assesses outcomes and process. SART is built to be defensible against the ICO's actual review standard — reasoned, attributable, contemporaneous — not against a non-existent certification.

Question 9

Does SART read the whole bundle?

Accepted Answer

Yes. The classifier agent walks every passage. There is no sampling; sampling is incompatible with defensibility.

Question 10

What if a passage is ambiguous?

Accepted Answer

Ambiguous passages are surfaced to the reviewer with both interpretations and the adversarial-audit verdict. Ambiguity is never silently resolved.

Question 11

Can we add rules to the ruleset?

Accepted Answer

Yes — through quarterly logic review. New rules require a written specification, examples, and adversarial review before they enter production.

Question 12

Does SART integrate with our case management system?

Accepted Answer

Integration is bundle-level: you export the SAR bundle to SART and ingest the signed result. Direct integrations with housing case management systems are scoped per deployment.

Question 13

Where is data hosted?

Accepted Answer

Inside your perimeter. SART ships as a Docker container and runs on your infrastructure. There is no SART SaaS tenant for your data.

Question 14

Do you have access to our SAR bundles?

Accepted Answer

No. We do not access customer SAR data. Support is delivered with synthetic bundles and metadata where possible; production-data access requires your explicit, scoped, time-bound authorisation.

Question 15

How do you handle special category data?

Accepted Answer

Special category data is flagged in the bundle and surfaced for the reviewer. Recommendations follow the relevant exemption rule with elevated audit attention.

Question 16

What does deployment look like?

Accepted Answer

A Docker container, a small set of declarative configs, and a reviewer account. Most pilots are operational within one to two weeks of IT review.

Question 17

Does SART call out to the internet?

Accepted Answer

No outbound dependency for triage. Logic-review updates are delivered as signed artefacts; you apply them inside your perimeter.

Question 18

What about model dependencies?

Accepted Answer

Models are bundled in the container. Pilot configurations and model versions are pinned and changelogged so triage is reproducible from inputs.

Question 19

Why isn't the price on the website?

Accepted Answer

Because the figure depends on bundle volume, group structure, and tier. We publish what's included — see the Pricing page — and respond to pilot enquiries the same week.

Question 20

Is there a per-SAR fee?

Accepted Answer

No. SART is a per-deployment licence, not a per-document meter.

Question 21

Is there a free pilot?

Accepted Answer

Founding pilots are not free, but they are scoped tightly and shape the v1.1 ruleset directly. Pricing is on request.

Guardrails, legal responsibility, and how triage actually works.

Guardrails

Legal responsibility

How triage works

Data & sovereignty

Deployment & security

Pricing

Different question?