ActiveOwner: DanUpdated: 11 Jun 2026
Definitions
Shared defined terms used across the Eddy Works Terms of Use, Acceptable Use Policy, Privacy Policy, and Data Processing Agreement.
COUNTER-DRAFT — Eddy Works, 11 June 2026. Published here for review — not yet approved by counsel and not yet in force.
1. Defined terms
Capitalised terms used in the Terms of Use, Acceptable Use Policy, Privacy Policy, and Data Processing Agreement have the meanings given below unless otherwise defined in the specific document.
| Term | Meaning |
|---|---|
| AUP | The Acceptable Use Policy, which forms part of the Terms. |
| Authorised Partner | A third party separately authorised by Eddy Works (under a written agreement) to resell, implement, or deliver services built on the Eddy platform. Distinct from a Customer who invites external participants into its own processes. |
| Beta Access Period | The period during which the Service or specific features are made available as a beta release. A beta release is a product status (invite-only private beta or opt-in public beta), not a per-Customer trial. The Beta Access Period has no fixed end date and will be notified via the Service or Website. |
| Customer | The legal or natural person that subscribes to the Service and is identified as the customer on the Order Form. The Customer is usually represented by an Organisation and its controlling Owners/Admins. |
| Customer Content | The data, text, files, votes, decisions, and other materials that users type, upload, or submit into the Service via Map stages or otherwise. |
| Customer Notice | Any terms, data-processing notices, or participant instructions that a Customer may choose to present to first-time Participants in its Processes via the Customer notice feature. |
| Data | Has the meaning set out on the Data categories page. References to specific data categories use the capitalised category names defined there. |
| Documentation | The user guides, help articles, and technical documentation we publish at help.eddy.works (planned — not yet live). |
| Eddy Works / we / us | Eddy Works Limited, incorporated in New Zealand. |
| External Participant | See Guest. "External participant" is a plain-language description of the relationship; Guest is the role. They are one and the same. |
| Fees | The amounts payable by the Customer for the Service as set out in the Order Form or Pricing Page. |
| Force Majeure | An event that is beyond the reasonable control of a party, excluding: (a) an event to the extent that it could have been avoided by a party taking reasonable steps or reasonable care; or (b) a lack of funds for any reason. |
| Guest | A person invited to participate in a Session via a link (start link, group invitation, or template permalink) who holds their own independent Eddy account. A Guest is not a general member of the Customer's Workspace — their access is limited to Sessions they are assigned to. "Guest" is an organisation role, not a separate account type. Also referred to in plain language as an "external participant." |
| Map | A reusable process design built in the Service — a structured graph of Stages, Transitions, Roles, and Blocks that can be executed as a Session. |
| Map Role | A named participant lane defined by the author of a Map (e.g. Submitter, Approver, Reviewer). Map Roles are author-defined and not a fixed system list. |
| Member | An Eddy user whose account holds a membership role (owner, admin, or member) in the Customer's Organisation. Members are invited or controlled by the Customer. This category does not include External Participants, whose relationship with Eddy Works is independent. |
| Order Form | A written or online order that references these Terms and sets out the subscription details. |
| Organisation | The top-level container in the Service associated with the Customer's subscription — encompassing billing, membership, Workspaces, and administrative control. |
| Participant / Eddy user / user | Any person with an Eddy account who accesses the Service, including Members and External Participants. |
| Process | The execution of a Map as one or more Sessions. |
| Row / Record | The structured output produced when a Session is completed — a row in a Table containing the structured data captured during that run. |
| Service | The Eddy platform — including the Builder, Session execution environment, Table, and Operator view — provided by Eddy Works under the Terms. |
| Session | A single live execution of a Map. |
| Session Assignment | The stage-level token that grants a specific Participant access to a specific Stage in a Session. Co-ownership of Session data attaches at this grain. |
| Stage | A single step in a Map — typically one screen that a Participant acts on. Access to a Stage is enforced per-stage; Participants see only the Stages they hold Session Assignments for. |
| Start Date | The date that the Customer first agrees to the Terms. |
| Table | The structured collection of Records produced by Sessions run against a Map. |
| Template | A Map made available for reuse in one of three tiers: Private Template, Partner Template, or Public Template. See clause 11. |
| Terms | The Terms of Use together with the AUP, Privacy Policy, and DPA where applicable. |
| Workspace | A container within the Customer's Organisation for a team's Maps, Tables, members, and Sessions. |
Terms of Use
Eddy Works Terms of Use — counter-draft applying the redraft guide (Kindrik draft set, 27 May 2026). British spelling per legal-pack register.
Data categories and subjects
The distinct categories of data in Eddy, who controls each, the data subjects covered by the DPA, and sensitive data tiers.
