Purpose

The AIR platform infrastructure continuously collects data at an increasing rate, necessitating periodic data clearance to maintain optimal performance and system maintenance. As datasets grow larger, the time required for AIR operations to complete can increase.

This policy serves as a standard document applicable to all clients, outlining the data lifecycle policies for the platform's data-intensive components. It also clarifies that Eagle Eye reserves the right to purge data after a specified period, although this action may not always occur within the defined timelines.

Additionally, other data objects may be considered for purging in the future.

Definitions

Purging

Purging data within the platform refers to the process of permanently deleting data that is no longer actively used. Although an offline copy is retained in backups for 15 months, this data will no longer be accessible through the platform.

Transactional data is purged according to the data lifecycle rules outlined in this document. This process is essential for several reasons, including compliance with regulations and improving system performance to help ensure we meet our Service Level Agreements (SLAs).

Purged Data

The following list contains all of the data objects that we purge at times within the AIR platform.

Expired Promotion Accounts.
Promotion Accounts (all statuses).
Campaigns (including Schemes).
Wallet Transaction Baskets.
Wallet Transactions.
Hermes 1 Event Notifications.
File Uploads.

Each data type has a specified minimum purge age, but data may be purged at any time after reaching this age, rather than exactly at the specified age. For example, expired promotion accounts in the PROD-UK environment may be purged after 365 days, rather than precisely at 56 days.

All reporting will remain unaffected by this policy.

Included Clients

This policy applies to all clients and can vary between clients.

Data Lifecycle Rules

Data Object	Include Related	Exclude Related	Purge Reason	Client Impact	Minimum Purge Age
Expired Promotion Accounts e.g. A Coupon that has never been redeemed, and is past its expiry date.	Account Metadata. Account Overrides.	Removal from Wallet Transactions.	Expired Promotion Accounts don't have any transactions and become defunct after their expiry. Note: Accounts that have been used in a return process and had budgeting associated with them will be excluded from the filter.	Purged data will not be accessible via the Dashboard, and will not return in custom scheduled reports.	183 days (after account expiry).
Promotion Accounts (all statuses)	Account Metadata. Account Overrides. Account Transactions. Tokens.	Removal from Transaction Relationships.	The Transactions and Accounts are moved to a data warehouse for reporting (or client data lakes) and therefore do not need to be in the transactional databases indefinitely.	Purged data will not be accessible via the Dashboard, and will not return in custom scheduled reports.	731 days (after Account valid to date, regardless of status column.
Campaigns Campaigns Schemes Programmes	Properties of the Campaigns.	Links to objects outside the Campaign data object will be orphaned.	The data is only required while there is still a valid Account linked to the Campaign.	Purged data will not be accessible via the Dashboard, and will not return in custom scheduled reports.	731 days (after Campaign expiry).
Wallet Transaction Baskets	Only Basket data.	N/A		Purged data will not be accessible via the Dashboard, and will not return in custom scheduled reports.	183 days (after creation). This is a general rule, and it is possible to request shorter client-specific rules. However, AIR may still be removed after this time.
Wallet Transactions	Wallet Transaction details. -Wallet Transaction histories and Account Id's impacted by the transaction.	Anything in the “Account” object domain.	The transactions are no longer relevant after the purge period	Purged data will not be accessible via the Dashboard, and will not return in custom scheduled reports.	731 days (after creation).
Wallet Stats	Wallet Statistics.	N/A	The data is only required for a short time after the Wallet event has occurred, and any underlying object will remain in the data centre.	Purged data will not be accessible via the dashboard, and will not return in custom scheduled reports.	100 days (after creation).
V1 Event Notifications	Only v1 Events.	N/A	The data is only required for a short time as a backup for event delivery failures. Clients should be processing these in as close to real-time as possible.	Purged data will no longer be available on the Event queues, and it will not be able to replay them.	31 days.
MFT File Uploads	Files uploaded to all MFT file locations.	N/A	Once uploaded files are no longer required again after the file's age reaches the limit. Nb: The purge policy will apply across all folders within the Google bucket and not specific file locations.	Purged files will be deleted and no longer remain in the original MFT file location.	Sandbox - 10 days (after processing). Production - 31 days (after processing).
SFTP File Uploads	Files uploaded to all SFTP file locations.	N/A	Once uploaded files are no longer required again after the file's age reaches the limit. Nb: The purge policy will apply across all folders within the Google bucket and not specific file locations.	Purged files will be deleted and no longer remain in the original SFTP file location.	Sandbox - 10 days (after processing). Production - 31 days (after processing).
Recommendation Catalogues	N/A	N/A	Once the Catalogue has expired, the data should no longer be required.	Expired Recommendation data will not be accessible within AIR.	10 days (after expiry).

*Note: 731 days equates to 2 years + 1 day (to cover leap years)