Enrolment and pilot product access — ifCEM
Effective date: 15 November 2026.
Entity: DataMPowered Pty Ltd.
Product: ifCEM.
1. Purpose
This notice explains what an ifCEM enrolment invite or code grants to organisations using the initial public and pilot-access parts of ifCEM, and what it does not grant (see Section 3). Enrolment is B2B and for guided pilot / evaluation product access only. This notice should be read together with the Website and Pilot Product Terms and the Privacy Policy listed in Section 6.
A guided pilot under this notice is scoped to the use case for which the enrolment invite or code was issued. It is not a general organisational enrolment beyond that use case.
2. What an enrolment code grants
When a DataMPowered ifCEM operator (a person authorised by DataMPowered to run the pilot desk) issues an enrolment invite/code and an authorised representative of the organisation completes enrolment, the organisation receives:
- Pilot product access to ifCEM evaluation / pilot packaging made available for that enrolment, for the use case named or described in that invite
We also record the organisation’s details and the buyer details supplied at enrolment (the commercial contact named for that pilot) in our commercial records for that pilot.
3. What an enrolment code does not grant
Enrolment does not:
- Give anyone authority to act for the organisation inside the organisation’s own enterprise, including appointing organisational roles or institutional mandates
- Move or enrol the organisation’s systems of record (the organisation’s own business systems and source data) into ifCEM’s keeping
- Approve institutional work under ifCEM’s full operational rules, or create participation rights beyond pilot product access for that use case
- By itself connect the organisation’s login system to ifCEM, set up links to the organisation’s systems of record, or complete production integrations with the organisation’s enterprise systems
- Create a consumer subscription or retail banking product
- Authorise live payment charging unless a separate agreement says so
Enrolment is for the guided pilot of the use case on the invite. Connecting the organisation’s login system or other enterprise systems is a separate step, only when the organisation and DataMPowered arrange it later. It is not required to start or run that pilot, and its absence does not mean ifCEM itself is incomplete.
4. Attestation
Completing enrolment requires the person completing the form to confirm that they are authorised to enter a commercial agreement for product access for the organisation. That confirmation does not mean that they are giving DataMPowered (or anyone else) authority to act for the organisation beyond that product access.
5. Retention
Organisation and buyer records for pilot product access are retained for the duration of the guided pilot (which is scoped to the use case for which the invite was issued) plus six months after the end of that guided pilot. After that period they are deleted or de-identified, unless a new commercial agreement provides for migration or different retention. See Retention and deletion.