AI processing notice

This notice is given by Zero Touch Integrations, operated by Chaley Consulting (“we”, “us”, “our”), to its customers (“you”, “your”). Words defined in the Customer Agreement have the same meaning here.

1. Why this notice exists

• We use AI tools to help scope, build, test and repair integrations. You accept this notice with each SOW, so that you know, in plain words, what those tools do, what data they see and what they can never do.
• This notice forms part of the Customer Agreement. How we handle personal data is governed by the Data Processing Addendum.

2. What AI tools do

AI tools:

• read your request and the documentation of the apps involved;
• read every email sent to our support address, including email from people who are not customers, to sort it and draft answers. A person handles anything the AI tool cannot answer;
• find publicly listed business contact details (a company’s name, a work role and a work email address) of businesses that may need an integration, and draft outreach emails to them. A person decides whether each email is sent, and anyone can ask not to be contacted again;
• look at the structure of your data (field names, types and a small number of sample records) through read only access, to write the scope and examples;
• draft the plain language scope, acceptance criteria and examples for the SOW;
• write the integration code and its tests;
• check another tool’s work, as an independent automated reviewer; and
• propose fixes when an integration fails after go live.

3. What AI tools can never do

AI tools can never:

• move money, set or change a price, or sign anything;
• deploy code, change the stage of a project, or approve their own work;
• hold or see your passwords or access tokens. Credentials are held only by specialist secret stores;
• write to your apps directly. Only the deployed integration writes, and only after you approve the trial results and a person approves go live; or
• decide your price or see the budget you told us.

4. Human and automated checks

• A person approves every SOW price and scope before you see it.
• Code must pass tests based on the signed acceptance criteria, an independent automated review, and a trial run against real data in which nothing is written. A planted fault check also runs: it reports to the person approving the work how well the tests catch faults planted on purpose, and it does not by itself block the work.
• You review the trial results and approve go live, and a person approves it too.
• Before a person approves a repair after go live, we test it by replaying the failed records and a sample of good ones. The only exception is narrowly defined low risk fixes described at www.zerotouchintegrations.com/security.
• The inputs, outputs, tools used and cost of every AI session are recorded in an audit trail.

5. Data the AI tools see

• Only what a step needs: the scope documents, descriptions of your data’s structure, and the minimum sample of records needed to write examples or diagnose a failure, with secret values removed.
• Recordings of exchanges with app vendors used for repairs are kept for 30 days.
• AI sessions are deleted when the step they served is finished. Their outputs stay in the project’s record.

6. AI providers

• The AI models are provided by the subprocessors named at www.zerotouchintegrations.com/legal/subprocessors (for example Anthropic), under terms that do not allow your data to be used to train their models.
• Model providers process data in the regions listed at www.zerotouchintegrations.com/security.

7. Learning without customer data

• We improve our process using de-identified, aggregated know-how (patterns, mapping rules and checklists), which a person reviews before it is kept. It contains no customer records and does not identify you.

8. Accuracy and responsibility

• AI output can be wrong. That is why every output described above is checked by tests, by a separate review and by a person before it affects your systems.
• What the plan covers, and our remedies for defects, are set out in Customer Agreement section 6, whatever tool wrote the code.

9. Questions and objections

• Send questions to support@zerotouchintegrations.com.
• At launch, we cannot serve a customer that does not accept AI assisted building. If you do not accept it, you may decline the SOW at no cost.

10. Versions and acceptance record

• Each version of this notice has a version number and a sha256 fingerprint of its text. The fingerprint is printed on the SOW and recorded in your acceptance record.
• Every past version stays published at /legal/ai-processing-notice/v<n> on our website.
• New versions follow the change rule in Customer Agreement section 12.