Retention and deletion — ifCEM B2B guided pilot
Effective date: 15 November 2026.
Entity: DataMPowered Pty Ltd (ABN 49 632 702 768).
Product: ifCEM.
This schedule sets out how long DataMPowered Pty Ltd keeps, and how it disposes of, data collected through the initial public and pilot-access parts of ifCEM, namely the website, guided pilot requests, enrolment and the operator desk. It is operative policy for those parts.
In this schedule, a guided pilot is scoped to the use case for which the enrolment invite or code was issued (see Enrolment and product access). The end of the guided pilot means the end of that use-case-scoped pilot, including withdrawal. It does not mean the end of any broader organisational relationship, unless a separate commercial agreement says otherwise.
In this schedule, de-identify means to irreversibly alter personal information so that it is no longer about an identifiable individual or an individual who is reasonably identifiable, and delete means to permanently destroy the information so that it cannot be recovered in the ordinary course.
1. Retention table
| Data category | Retention | Disposal |
|---|---|---|
| Public explore turns (prompts/readings) when the visitor does not progress to a pilot request | Not retained as a durable record. Held only in short-lived session memory (see note below) | Automatic purge from session store |
| Explore-related content when the visitor does send a pilot request | Explore prompts and readings included in the consented summary: 30 days from the request (see note below) | Delete or de-identify |
| Consented pilot request and general-question intakes (summary + email + consents) | 6 months after last contact, or if a pilot request is declined, 30 days from decline (see note below) | Delete or de-identify |
| Unused enrolment invites / codes | Until invite expiry + 30 days (see note below) | Delete |
| Completed commercial organisation / buyer records for pilot product access | Duration of the guided pilot (use case on the invite) + 6 months after the end of that guided pilot (see note below) | Delete or de-identify; migrate only under a new commercial agreement |
| Operator Cognito accounts | While the person holds an active operator role + 30 days | Disable/delete account materials as configured |
| Security / access logs | 90 days from creation of each entry (see note below) | Delete, or rotate so older entries are permanently removed |
Session memory is temporary storage that holds a visitor’s explore prompts and readings during a visit. It is purged automatically after a period of inactivity, currently on the order of 2 hours. That period is an operating setting and may change, and explore sessions are never written to the commercial database (see Section 4).
For consented pilot request and general-question intakes, the retention period is 6 months after last contact (as defined in Section 3). If a pilot request is declined, the 30 days from decline applies instead of the 6-month period.
When a visitor sends a pilot request, the explore prompts and readings included in the consented summary are kept for 30 days from the date of the request and are then deleted or de-identified. The intake record itself (summary, email and consents) is not deleted at that point and continues under the consented pilot request and general-question intakes rule.
An enrolment invite or code is unused until it has been used to complete enrolment. Unused invites and codes are kept until the invite expires, plus 30 days, and are then deleted. Once enrolment is completed, the resulting organisation and buyer record follows the rule for completed commercial records.
Completed commercial organisation and buyer records for pilot product access are kept for the duration of the guided pilot for the use case on the enrolment invite, plus 6 months after that pilot ends, and are then deleted or de-identified. This period applies instead of the 30-day period in Section 2. If a new commercial agreement is signed, migration and retention follow that agreement, and migration is permitted only under it.
Operator Cognito accounts are the sign-in accounts held in the Amazon Cognito user directory for DataMPowered personnel who work on the operator desk. Account materials means the account’s profile details and credentials held in that directory.
Security and access logs are kept for 90 days from the date each log entry is created. After that period they are deleted, or rotated in a way that permanently removes entries older than 90 days. Automated log traffic does not count as “last contact” (see Section 3).
Where more than one row or rule in this schedule could apply to the same personal information, the more specific category row for that information applies. Where section 2 and a table row both apply, any longer period stated in the table continues for that category as described in section 2(1), unless law requires longer retention or a new commercial agreement provides otherwise.
2. Pilot end and withdrawal
When a guided pilot ends or the organisation withdraws:
(1) Within 30 days of that end or withdrawal, we delete or de-identify personal information collected for that pilot, except where a longer period in the table above still applies (for example, completed commercial records until pilot end + 6 months) or where law requires longer retention.
(2) If the organisation later enters a separate commercial agreement, any continued use or migration of pilot data, including that personal information, happens only under that agreement; pilot retention does not automatically become a seven-year archive.
3. Meaning of “last contact”
In this schedule, last contact means the most recent substantive communication about the intake or pilot between DataMPowered and the organisation’s nominated contact. It includes operator outreach and the organisation’s reply. It does not include automated log traffic.
4. Engineering alignment
The following operational commitments support this schedule. In this section, custody ledger means the separate record system that holds institutional custody credentials and records, which is kept apart from commercial storage. These commitments bind how DataMPowered configures and operates the initial public and pilot-access parts of ifCEM:
- Explore sessions must not be written to the commercial database or custody ledger.
- Consented sends write to commercial intake storage only.
- Enrolment codes and completed organisation/buyer rows live in commercial storage, separate from institutional custody credentials.
- Deletion jobs and operator procedures must be able to give effect to this schedule; gaps are operational defects, not silent policy exceptions.
5. Contact
For questions about this retention and deletion schedule, or about how personal information is retained or deleted, contact DataMPowered Pty Ltd at privacy@datampowered.com.au.