HENRYEXCHANGEJoin the Exchange

HENRY INSIGHTS PRODUCT AND PROCESSING SCHEDULE

Effective Date: 24 August 2026
Version: 1

This Schedule forms part of the Agreement when the accepted Online Order Record includes Henry Insights. It provides the product-specific processing description and must be read with the Terms of Service, Privacy Policy, Operator Agreement, Security and Incident Schedule, Retention, Deletion and De-identification Schedule, Suboperator List and International Transfer and Recipient Register.

Standard and Enterprise arrangements: The standard position described in this document applies unless a signed Enterprise Annex expressly varies an eligible, identified contractual matter. Where legally and operationally available, any enhanced or non-standard scope, service level, support, infrastructure, assurance, reporting, implementation or other commitment must be separately requested, assessed, approved and priced under the Enterprise Agreement. An Enterprise Annex cannot alter statutory rights or mandatory legal obligations.

1. Product Scope and Roles

1.1. Henry Insights structures, links and analyses authorised records to provide search, dashboards, digital-twin views, summaries, indicators, scores, predictions, recommendations and other decision-support outputs.

1.2. The Tenant is generally the Responsible Party and Henry its Operator for Tenant Data, linked records and Tenant-Specific Henry Outputs. That role allocation regulates processing and does not alter intellectual-property ownership. Henry is an independent Responsible Party for account, billing, security, fraud, compliance and narrowly defined Service Usage Data.

1.3. The Tenant instructs Henry through selected datasets, Users, rules, prompts, models, reports, thresholds, dashboards, integrations and output recipients.

1.4. A Tenant instruction or configuration choice does not by itself authorise Henry to create, disclose, demonstrate, configure or enable a materially new dataset, purpose, profiling or AI use, model, decision rule, recipient, provider, country, transfer, retention rule, security exception or regulated workflow. The applicable impact assessment, Henry internal approvals and review by appropriately qualified external legal or compliance counsel must be complete before activation, and a non-standard contractual commitment requires a signed Enterprise Annex.

2. Data Subjects, Information and Sources

2.1. Data Subjects may include Tenant personnel, customers, applicants, business contacts, transaction participants and other persons represented in authorised source records.

2.2. Information may include:

  • Tenant-provided or Ingest-processed documents and structured records;
  • identity, contact, employment, financial, vehicle, application, transaction and communication data;
  • entities, attributes, relationships, provenance, timestamps and correction history;
  • prompts, retrieved context, summaries, classifications, indicators, scores, recommendations and reports;
  • Tenant rules, thresholds, annotations and review decisions; and
  • access, query, processing, quality, security and audit events.

2.3. Insights involving Children's Information, biometric, health, criminal, credit-reporting or other special information, or a solely automated decision with legal or similarly substantial effect, require a documented lawful assessment and any approval, prior authorisation or safeguards required by law and the Online Order Record or signed Enterprise Annex.

3. Purposes and Operations

3.1. Henry may collect, receive, host, store, cache, replicate, back up, transmit, access, organise, index, retrieve, link, compare, analyse, aggregate, score, summarise, display, report, export, correct, restrict, de-identify and delete Tenant Data to:

  • provide configured search, analytics and digital-twin functions;
  • identify relationships, trends, exceptions and potential duplicates;
  • generate Tenant-specific reports and decision-support outputs;
  • support correction, provenance and review workflows;
  • provide support, reliability, metering, security and abuse prevention; and
  • follow documented instructions and comply with law.

3.2. Henry will not use identifiable Insights Tenant Data for targeted advertising, data-broker sale, unrelated user profiling or customer-specific competitive intelligence.

4. AI, Profiling and Human Review

4.1. Insights may use AI and statistical methods for natural-language interaction, summarisation, linking, analytics, scoring, recommendations, anomaly detection and risk indicators.

4.2. Henry will not use identifiable Insights Tenant Data to train a general-purpose or shared foundation model, or permit a model provider to do so, except on the Tenant's separate documented instruction.

4.3. Model inference, retrieval, evaluation of a Tenant-specific output and safety monitoring are distinct from foundation-model training. Provider safety retention or authorised review of flagged content may occur only where disclosed for the selected feature.

4.4. Insights is decision support. The Tenant must ensure meaningful qualified review before a material legal, financial, employment, credit, insurance or similarly substantial decision and must test for accuracy, relevance, unfair discrimination and foreseeable misuse.

4.5. Where POPIA section 71 or another automated-decision rule applies, the Responsible Party must document the lawful basis, safeguards, explanation, human-intervention route and opportunity for the affected person to make representations.

5. Storage, Locations and Providers

5.1. Insights data may be stored in standard database, document, analytical, cache, log and protected-backup systems and may be transiently processed by an enabled AI or integration provider.

5.2. Standard routes may include Supabase, AWS, Google Cloud/Gemini, Yield Point AI and authorised Microsoft or Google integrations. Exact roles, data and principal locations appear in the Suboperator List and International Transfer and Recipient Register.

5.3. The standard Service does not include country-exclusive residency. A signed Enterprise Annex must identify any covered datasets, analytical stores, model endpoints, logs, backups, support access and permitted exceptions.

6. Retention, Export and Deletion

6.1. During the subscription, the Tenant may use available controls to access, export, correct, restrict or delete Insights records, subject to product capability, legal holds, minimum security evidence and the Henry Output licence in the Terms of Service. Export does not transfer ownership.

6.2. Tenant-specific linked records, digital twins, reports, prompts and outputs ordinarily follow the source Tenant Data lifecycle. After termination, the standard 90-day limited-function export period and additional 90-day deletion period apply.

6.3. A source deletion or correction will be propagated to affected active derived records where reasonably practicable. Henry may retain lawfully De-identified Data only under the Agreement's de-identification standard and will not substitute de-identification for a specific Operator deletion instruction without authority.

6.4. Logs, support, security and compliance evidence follow their separate record-class periods.

7. Security and Shared Responsibility

7.1. Henry applies the Security and Incident Schedule to covered Insights systems, including access control, encryption, logical separation, logging, vulnerability handling and backups.

7.2. The Tenant is responsible for:

  • lawful, relevant and sufficiently accurate source information;
  • selecting authorised datasets, Users, recipients, prompts and thresholds;
  • testing and monitoring the workflow for its intended use and population;
  • meaningful human review and correction of material outputs;
  • notices, lawful basis, consent, prior authorisation and data-subject channels; and
  • preventing an output from being used outside its context or retained longer than necessary.

8. Output, Quality and De-identification

8.1. The Tenant retains its rights in pre-existing Tenant Materials and unchanged source Tenant Data. All linked records, relationship graphs, digital twins, summaries, classifications, indicators, scores, rankings, predictions, recommendations, reports, dashboards, visualisations, benchmarks, analytical findings, provenance, corrections, annotations and other Insights Outputs are Tenant-Specific Henry Outputs owned by Henry under the Terms of Service Section 2. The label identifies the intended recipient or source and not ownership. The Tenant receives only the applicable paid licence; payment, export, configuration and correction do not transfer ownership.

8.2. Henry will not warrant that an inference, link, score, summary, prediction or recommendation is complete or correct. Henry will provide available provenance, confidence, limitation or correction information reasonably needed for the Tenant's review.

8.3. De-identified analytics must not identify or reasonably permit identification or singling out of a person or Tenant. Pseudonymised data remains protected.

9. Changes and Product Exit

9.1. Henry may make commercially reasonable product changes. A material reduction of the processing, security, retention or availability commitments applicable to a paid fixed Subscription Period ordinarily applies on renewal, except for law or urgent security.

9.2. If Henry retires a material generally available Insights function without a reasonably comparable replacement, it will ordinarily give at least 12 months' notice unless security, law, provider withdrawal or system integrity requires earlier action. This does not apply to beta, preview or experimental functions.

9.3. No meeting statement, demonstration, roadmap discussion, email, proposal or individual representative's approval expands this Schedule or authorises reliance on an unapproved Insights capability, model, decision rule or processing route.

END OF HENRY INSIGHTS PRODUCT AND PROCESSING SCHEDULE