Knowing archiving policy and data retention times

These rules apply to:

• Data stored and processed in the Splio platform.

• Data made available through standard product surfaces (Contact page, segmentation, exports, delivery, reporting dashboards).

These rules do not replace contractual obligations or legal requirements. When legal or contractual constraints differ, those constraints take precedence.

• Client data ("push" data): data uploaded or synchronised by the client, such as contacts, orders, and stores or other.

• Event data: behavioural and delivery-related events produced by channel activity (for example: message delivered, bounced, unsubscribed, opened, clicked).

• Aggregated analytics: data that has been processed into statistics and dashboards, and is not stored as raw event-level logs.

• Mirror page: hosted page used to display a message in a web view.

General rules

1) Client data (contacts, orders, stores)

• Retention: no platform retention limit

• Responsibility: clients are responsible for deleting data that is no longer relevant

This category covers data ingested into Splio as “source of truth” business data. Because this data is client-owned, retention is governed primarily by the client’s own policies and requirements.

.

2) Event data (delivery and reactivity)

• Retention: 13 months

• Applies to: segmentation, exports, delivery, and the Contact page

This includes channel event streams used to power targeting, operational views, and user-facing activity histories.

.

3) Aggregated analytics

• Retention: 49 months

• Typical outputs: campaign statistics, dashboards, revenue metrics, delivery breakdowns (including by domain and unsubscribe reason)

Aggregated analytics provides long-term reporting without keeping raw event-level data beyond its retention period.