CDR · Data lifecycle

Data Retention & Deletion Policy

Last updated 9 July 2026

This policy governs how otosheets retains, deletes, and destroys data — including CDR data handled under the Consumer Data Right (CDR) regime. otosheets acts as a CDR Representative of Fiskil, our CDR Representative Principal and an Accredited Data Recipient. It sets specific retention periods by data category, our deletion and verification processes, and our CDR-specific deletion obligations under CDR Rules 7.12, 7.13, and 1.10AA(4)(e). It is a standalone operational policy and does not rely on our general Privacy Policy to satisfy these obligations.

1. Scope and Definitions

  • CDR data — consumer data received via the CDR regime through Fiskil, including account details, balances, and transaction data, and any data directly or indirectly derived from it (e.g. categorisations, insights).
  • Redundant data — CDR data that is no longer needed for any purpose for which it was collected or is permitted to be used or disclosed, and that the consumer has not elected to have retained.
  • Principal — Fiskil, our CDR Representative Principal and the Accredited Data Recipient responsible for the CDR arrangement under which we operate.
  • Deletion — irreversible removal of data from all production stores, caches, and backups such that it can no longer be accessed or reconstructed.
  • De-identification — where permitted, modifying data so that it is no longer about an identifiable, or reasonably identifiable, consumer, in line with the CDR de-identification requirements.

2. Retention Periods by Data Category

We retain each category of data only for as long as necessary for its stated purpose or as required by law. CDR data is held to the shortest permissible period and is deleted or de-identified once redundant.

Data categoryRetention periodBasis
CDR data (accounts, balances, transactions)Only while needed for the consented purpose; deleted or de-identified when redundant, and within 2 business days of a deletion trigger (see §4)CDR Rules 7.12, 7.13
CDR-derived data (categorisations, insights)Same as the CDR data it derives from; deleted or de-identified with itCDR Rule 7.12
Account & identity data (name, email, business, ABN)Life of the account; deleted within 30 days of verified account closurePrivacy Act 1988 (APP 11.2)
Business financial records (invoices, receipts, GST/tax data you create)7 years from creationATO record-keeping requirements
OAuth tokens (Google, Microsoft, Meta, Xero, Stripe)Deleted immediately on disconnection or account closureData minimisation
CDR audit logs (access to / processing of CDR data)7 years (exceeds the 6-year minimum)CDR Rule 9.3(2)(l)
Operational / usage logs30 daysSecurity & debugging
BackupsRolling window; deleted data purged from backups within the backup cycle (max 35 days)Operational resilience

3. Deletion and Destruction Processes

Deletion propagates across every place data is held. When a deletion trigger occurs, we:

  • Mark the records for deletion and immediately remove them from serving paths (soft-delete), then permanently delete them from our primary store (Neon Postgres).
  • Delete associated objects from file storage (Amazon S3) and purge any cached copies.
  • Remove the data from search/index structures and any downstream derived datasets.
  • Ensure deleted data is purged from backups within the backup cycle (no restore reintroduces deleted CDR data without re-deletion).
  • Where the CDR Rules permit retention in de-identified form instead of deletion, apply irreversible de-identification rather than raw deletion.

3.1 How deletion is verified

  • Each deletion runs as an idempotent job that returns a completion record confirming the record no longer exists in each store.
  • A deletion log (retained with our CDR audit logs) records what was deleted, when, the trigger, and confirmation of removal across stores — without retaining the deleted CDR data itself.
  • We run periodic reconciliation checks to confirm that records flagged for deletion are absent from production stores and backups past the backup cycle.
  • On request, we can provide the Principal (Fiskil) with confirmation that a deletion instruction has been carried out.

4. CDR-Specific Deletion Obligations

In addition to the periods above, we delete (or, where permitted, de-identify) CDR data on any of the following triggers, acting within 2 business days of becoming aware of the trigger:

4.1 Withdrawal or expiry of consumer consent

When a consumer withdraws their consent, or their consent expires, the CDR data collected under that consent becomes redundant. We delete or de-identify it unless the consumer has elected for us to retain it, and unless we are required by law to keep it (in which case retention is limited to that legal requirement). (CDR Rule 7.12 — deletion of redundant data.)

4.2 Deletion on consumer election

A consumer may, at any time, elect to have their CDR data deleted. We honour such elections and delete the relevant CDR data (and data derived from it) upon receiving the election, whether made directly to us or relayed through Fiskil. (CDR Rule 7.13 — consumer's election to delete CDR data.)

4.3 Deletion on direction from Fiskil (our Principal)

As a CDR Representative, we handle CDR data under the direction of Fiskil, our CDR Representative Principal. Where Fiskil directs us to delete or de-identify CDR data — including on termination of our representative arrangement — we do so promptly and confirm completion to Fiskil. (CDR Rule 1.10AA(4)(e) — CDR Representative obligations to the Principal.)

5. Roles and Responsibilities

  • The person responsible for privacy/data protection at otosheets owns this policy and oversees deletion requests and Principal directions.
  • Engineering maintains the automated deletion and verification pipeline and the CDR audit log.
  • Deletion triggers relayed by Fiskil are actioned as a priority and confirmed back to Fiskil.

6. Review

This policy is reviewed at least annually, and whenever the CDR Rules, our arrangement with Fiskil, or our data flows change materially.

7. Contact

For questions about this policy, data retention, or to make a deletion request, contact: