All legal documentsVersion 2026-07-14
Shared Definitions
These definitions apply across every document in this pack. They are written in plain language and are intended to map to the statutory concepts under PIPEDA, Quebec Law 25, and the Alberta and British Columbia Personal Information Protection Acts. The split between De-identified and Anonymized Data is deliberate and tracks Law 25's distinction.
------------------- ---------------------------------------------------
**Term** **Meaning**
**Relae, we, us, Touch Grass AB, a Swedish company, which is the
our** contracting entity and the operator of the Platform
and the Services in every region. Relae may assign
its agreements to an affiliate or successor as
described in the Master Subscription Agreement.
**Region** A geographic deployment of Relae's data
infrastructure. A customer's Donor Data is stored
and processed in the customer's own Region. The
Canadian Region is the only Region operating today.
**Platform** The Relae software application or applications,
website, APIs, and related services.
**Services** The donor-management, reconciliation,
relationship-intelligence, and related functions
Relae provides through the Platform.
**Customer, you (in The organization that subscribes to the Services,
customer-facing ordinarily a registered charity or nonprofit. The
documents)** Customer is the Controller of its Donor Data.
**Authorized User** An individual the Customer permits to access the
Platform under the Customer's account (staff,
volunteers, or a Consultant acting for the
Customer), subject to role-based access.
**Consultant, A fundraising consultant or agency that manages one
Agency** or more client Customers within a single Consultant
account, switching between client workspaces under
authority granted by each client.
**Donor, An individual whose personal information a Customer
Constituent** uploads to or records in the Platform. Donors are
Data Subjects. Donors are not users of the Platform
and have no account with Relae.
**Donor Data** Personal information about a Customer's Donors
that the Customer uploads to, or generates within,
the Platform, including names, contact details,
giving history, relationship notes, event
attendance, photographs the Customer adds, ratings
and tiers, and model-derived estimates such as
predictive lifetime value and capacity ranges (the
full list is in the Privacy Policy). Relae
processes Donor Data as Processor on behalf of the
Customer.
**Customer Account Information about the Customer and its Authorized
Data** Users: organization details, user names, emails,
roles, login credentials, and staff profile photos.
Relae is the Controller of this data for
account-administration purposes.
**Website Data** Information about visitors to the marketing
website, including request-access submissions.
Relae is the Controller of this data.
**Controller** The party that determines the purposes and means of
processing personal information. For Donor Data,
the Customer is the Controller.
**Processor** The party that processes personal information on
behalf of, and on the instructions of, the
Controller. For Donor Data, Relae is the Processor.
**Data Subject** An identified or identifiable individual to whom
personal information relates.
**Sub-processor** A third party engaged by Relae to process personal
information in connection with providing the
Services (see the Sub-processor and Data Source
List in the DPA).
**Connected Data A third-party service (for example an event
Source** platform) that a Customer chooses to connect, from
which the Platform reads data at the Customer's
direction.
**De-identified Data from which direct identifiers have been
Data** removed so that a specific individual could not be
directly identified, but which may carry residual
re-identification risk. Used for processing within
the Services; corresponds to Quebec Law 25's
de-identified information.
**Anonymized / Data irreversibly aggregated across multiple
Aggregate Data** sources so that no individual and no individual
organization is reasonably identifiable, evaluated
against generally accepted best practices. This
higher standard, corresponding to Law 25's
anonymized information, is the standard the future
Benchmark Cooperative is designed to meet before
any pooling begins.
**Pilot** An experimental capability offered only to
organizations that enrol under a distinct, specific
pilot consent, governed by the Pilot and
Experimental Features Framework (Document 13).
Pilots are not part of current processing.
**Beta** The current pre-release phase of the Platform, in
which functionality and availability are limited
and may change.
------------------- ---------------------------------------------------