Privacy Policy — ifCEM (B2B guided pilot)
Effective date: 15 November 2026.
Controller: DataMPowered Pty Ltd (ABN 49 632 702 768) (“we”, “us”).
Product: ifCEM (a DataMPowered product), published at https://ifcem.com.au
Contact: privacy@datampowered.com.au.
This Privacy Policy explains how we handle personal information when an organisation or its authorised representative uses the initial public and pilot-access parts of ifCEM (the website, guided pilot requests, enrolment and operator desk) for B2B guided pilot or evaluation purposes. ifCEM is not a consumer (B2C) product and is not offered as a retail banking or APRA-regulated service.
We handle personal information in accordance with the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs), as applicable.
1. Who this policy covers
- Visitors exploring ifCEM on behalf of an organisation (landing and use-case exploration)
- People who send a guided pilot request or general question
- ifCEM operators who review intakes and issue enrolment codes
- People who complete enrolment using an enrolment invite/code for pilot product access
It does not cover processing inside a customer’s own systems of record, or institutional custody of bank or enterprise source data under a separate mandate.
2. What we collect
2.1 Public exploration (use-case)
When you explore with a use case, you may provide free-text descriptions of a need or situation and receive a provisional reading. Those turns are held temporarily in session memory so the visit can run (typically purged after about two hours of inactivity). They are not stored as a durable organisational record unless you later send a consented pilot request (or otherwise agree to send content to us).
2.2 Guided pilot request / general questions
A general question on the landing page may first create a session-scoped engagement (device cookie) so you can continue on the site. That content is not an operator intake until you later Send to ifCEM (or send a dedicated pilot request) with consent.
If you choose to send content to us for operator follow-up (pilot request or Send to ifCEM), we collect:
- The summary or question you submit
- Contact email (and any other details you include)
- Consent choices and time of submission
- Security signals needed to protect the service (for example reCAPTCHA results and basic request metadata)
2.3 Enrolment for pilot product access
If we issue an enrolment invite/code and you complete enrolment, we may collect:
- Organisation legal name and related organisation details you provide
- Buyer full name, work email, job title (if provided)
- Commercial attestation that you are authorised to enter a commercial agreement for product access (not institutional mandate)
- Invite/code status and timestamps
2.4 Operators
For operator accounts we collect Cognito sign-in identifiers (such as email/username), authentication logs, and allowlist membership needed to operate the desk.
2.5 Automatically collected
We may collect IP address, user agent, timestamps, cookie identifiers required for the session, and security/access logs. See also our Cookies and third parties notice.
3. Why we collect it (purposes)
We collect and use personal information to:
- Provide public B2B evaluation and guided-pilot discovery experiences
- Decide whether and how to follow up about a guided pilot
- Issue and honour enrolment codes for pilot product access
- Secure the service (abuse prevention, rate limiting, fraud/bot reduction)
- Meet legal obligations and resolve disputes
- Improve reliability of the evaluation experience (in aggregate or de-identified form where practicable)
We do not use the ifCEM website, guided pilot requests or enrolment process to enrol an organisation into institutional authority, mandate, or custody of its systems of record.
4. Basis for collection (APP 3)
We collect personal information that is reasonably necessary for our functions and activities described above. Where we rely on consent (for example sending a pilot request or general question to an operator), we ask for that consent before the content leaves your device for operator follow-up.
5. Disclosure
We may disclose personal information to:
- Operators employed or engaged by DataMPowered to run the ifCEM pilot desk
- Service providers who process data on our instructions, including Amazon Web Services (hosting, Cognito authentication, Amazon Bedrock for model-backed readings)
- Google (reCAPTCHA) for bot protection on public forms
- Professional advisers, or authorities, where required or authorised by law
We do not sell personal information.
6. Overseas disclosure
Personal information we hold for ifCEM (including intakes, enrolment records, operator accounts, and application logs) is stored and processed with Amazon Web Services in Australia (Asia Pacific — Sydney region). Model-backed provisional readings use Amazon Bedrock with an Australia geographic configuration so inference stays in Australia.
The intentional overseas disclosure for these parts of ifCEM is Google reCAPTCHA on public forms. When you use a protected form, Google may receive security and device signals (such as the reCAPTCHA token and related request metadata, which may include IP address) for bot protection. Google may process that information in the United States and in other countries where Google operates. It is not practicable to list every Google processing location because Google’s network and edge locations change. Form content that becomes an intake or enrolment record is held with us in Australia as described above; it is not sent to Google as the body of your submission.
Where overseas disclosure occurs, we take reasonable steps consistent with APP 8, including contractual and configuration controls appropriate to the service.
7. Retention
We retain personal information only as described in Retention and deletion. In summary:
| Category | Retention |
|---|---|
| Explore turns (no pilot request) | Not retained as a durable record (session memory only; purged on short TTL) |
| Explore-related content included when a pilot request is sent | 30 days, then delete or de-identify (intake record continues under intake rules) |
| Pilot / general-question intakes | 6 months after last contact; if a pilot request is declined, 30 days from decline instead |
| Unused enrolment invites/codes | Until expiry + 30 days |
| Completed pilot org/buyer records | Duration of the guided pilot (use case on the invite) + 6 months after that pilot ends, unless a new commercial agreement applies |
| Operator Cognito accounts | While role active + 30 days |
| Security / access logs | 90 days from each entry (then delete or rotate so older entries are permanently removed) |
8. Security
Personal information we hold for ifCEM is held in cloud hosting provided by Amazon Web Services in Australia (Asia Pacific — Sydney), separately from any institutional custody of a customer’s own systems of record. We use reasonable organisational and technical measures appropriate to a B2B pilot evaluation service, including access controls for operators, and transport encryption on public HTTPS endpoints. No method of transmission or storage is completely secure.
9. Access, correction and complaints
You may request access to or correction of personal information we hold about you, or make a privacy complaint, by emailing privacy@datampowered.com.au.
We will acknowledge a privacy complaint, investigate it, and then respond in writing. We aim to complete that response within 30 days of receiving your request or complaint. If we need more time, we will tell you why and when you can expect a further response.
If you are not satisfied with our response, you may contact the Office of the Australian Information Commissioner (OAIC): https://www.oaic.gov.au/
10. Children
ifCEM is intended for organisational and professional use. It is not directed at children.
11. Changes
We may update this Privacy Policy by publishing a new version on https://ifcem.com.au with a revised effective date. Material changes to pilot retention or purposes will be reflected here.