HENRYEXCHANGEJoin the Exchange

HENRY INGEST 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 Ingest. 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 Ingest connects authorised sources and receives, stores, extracts, classifies, redacts, structures, validates, links and routes documents and records for the Tenant's configured workflows.

1.2. The Tenant is generally the Responsible Party and Henry its Operator for Tenant-selected source content and resulting 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. Enabling a connector, mailbox, folder, API, database, upload route, AI function or recipient is the Tenant's documented instruction for the reasonably required processing. The Tenant determines the permitted source scope, Users, purpose and recipient configuration.

1.4. A Tenant instruction or configuration choice does not by itself authorise Henry to create, disclose, demonstrate, configure or enable a materially new source, purpose, data category, AI use, recipient, provider, country, transfer, retention rule, security exception or regulated workflow. The applicable workflow 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 whose information appears in an authorised source.

2.2. Information may include:

  • emails, messages, attachments, files, images and document text;
  • Microsoft 365; Google Drive, Gmail and Google Calendar; CRM, API and database content selected by the Tenant;
  • names, contacts, identifiers, employment, financial, vehicle, application and transaction information contained in those records;
  • source, folder, sender, recipient, timestamp, permission and synchronisation metadata;
  • extracted fields, classifications, redactions, confidence information, structured records, links and exceptions; and
  • access, processing, security and audit events.

2.3. Henry Ingest is not intended to receive payment-card security codes, passwords, private cryptographic keys or another person's authentication secrets. Children's Information, biometric information, health information, criminal information, privileged material or other sensitive categories require an approved lawful workflow and any additional safeguards stated in a signed Enterprise Annex.

3. Purposes and Operations

3.1. Henry may collect, receive, host, store, cache, replicate, back up, transmit, access, index, extract, transcribe, classify, redact, validate, enrich, deduplicate, link, route, display, export, correct, restrict and delete Tenant Data to:

  • connect and synchronise authorised sources;
  • convert unstructured records into Tenant-usable structured information;
  • identify duplicates, exceptions, missing information and workflow status;
  • route records and outputs to configured Henry functions or authorised recipients;
  • provide support, reliability, metering, security and abuse prevention; and
  • follow documented instructions and comply with law.

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

4. AI and Human Review

4.1. Ingest may use AI or machine learning for OCR, extraction, classification, transcription, redaction, validation and natural-language interaction.

4.2. Henry will not use identifiable Ingest 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. Processing content through a model to produce an extraction or classification is service inference, not training. A listed provider may temporarily retain or automatically assess inputs and outputs for security, abuse prevention or troubleshooting and may permit authorised review of flagged content where disclosed in the Suboperator List, Online Order Record or signed Enterprise Annex.

4.4. The Tenant must review outputs before a material legal, financial, employment or transaction decision. Confidence indicators and exceptions are decision-support information, not a warranty of accuracy.

5. Storage, Locations and Providers

5.1. Ingest content may be stored in the standard database, object storage, file service, logs and protected backups and may be transiently processed by an enabled AI or integration provider.

5.2. Standard provider routes include Supabase, AWS, Zoho, Google Cloud/Gemini, Yield Point AI, Microsoft and Google integration services, including Google Drive, Gmail and Google Calendar, where the corresponding function is enabled. 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 Tenant's Microsoft or Google Geo does not automatically govern data copied into Henry. A residency commitment must identify the covered content, processing state, providers and backup treatment in a signed Enterprise Annex and be selected in the Online Order Record.

6. Retention, Export and Deletion

6.1. During the subscription, the Tenant may use available controls to access, export, correct or delete Ingest 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. After termination, Ingest follows the standard 90-day limited-function export period and deletion from active production systems and protected backups within the additional 90 days.

6.3. Integration tokens are disabled promptly on disconnection and deleted from active systems within 30 days. Source content copied into Henry is not automatically deleted when a connector is disabled; the Tenant must use the applicable deletion function or instruction.

6.4. General logs, security logs and support records follow their separate record-class periods in the Retention, Deletion and De-identification Schedule.

7. Security and Shared Responsibility

7.1. Henry applies the Security and Incident Schedule, including encryption over public networks, encryption at rest in covered provider systems, logical Tenant separation, least privilege, privileged-access controls, logging and protected backups.

7.2. The Tenant is responsible for:

  • lawful access to every connected source and record;
  • selecting the minimum mailbox, folder, database, API and User scope;
  • maintaining source permissions and promptly revoking obsolete access;
  • configuring approved recipients and reviewing extracted information;
  • providing required notices, lawful basis, consent and prior authorisation; and
  • keeping independent copies of critical source records.

8. Output, Correction and Provenance

8.1. The Tenant retains its rights in pre-existing Tenant Materials and unchanged source Tenant Data. All extracted fields, structured records, classifications, redactions, validations, enrichments, linked records, provenance, corrections, annotations, reports, exports and other Ingest 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. Where technically available, Henry will preserve source references, timestamps, processing status and correction history reasonably necessary to trace a material output.

8.3. A substantiated correction to a source or extracted field will be propagated to affected active Henry records where reasonably practicable. It may not alter an independent recipient's record; the Responsible Party must notify that recipient where law requires.

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 Ingest 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 Ingest capability or processing route.

END OF HENRY INGEST PRODUCT AND PROCESSING SCHEDULE