Data retention

Nuntly keeps the data produced by your sending activity for a bounded retention window. This page explains how long each kind of data is kept, when it disappears from the API and dashboard, and how the inbox differs from sending.

​

Retention windows

Every organization has a retention window that applies to its email records: The default window is 30 days. Extended windows of 180 or 365 days are available on Enterprise plans and are configured by our team. There is no self-serve retention setting. To discuss an extended window, contact support@nuntly.com. If your organization’s window changes, the new window applies to emails sent after the change. Existing records keep the window they were written with, unless you ask us to shorten them immediately.

​

Retention is record-level, measured from the send

Retention applies per email record, not as a rolling account-wide cutoff. When an email is sent, its record gets an expiry of the send time plus your organization’s window. Everything that belongs to that record shares the same expiry:

• the message content and metadata,
• the delivery and engagement events (delivered, bounced, opened, clicked, complained, and so on),
• the stored copy used by the dashboard and the API.

​

Events inherit their email’s window

An event does not get its own window. It expires with its parent email. This means a late event has a shorter remaining lifetime: on the 30-day window, an open recorded on day 25 of an email’s life is kept for the remaining 5 days, not for a fresh 30 days. Once an email record reaches the end of its window, the record and its events are gone.

​

What happens after the window

Once an email record passes the end of its window:

• it no longer appears in email or event lists, in the API or in the dashboard,
• fetching it directly returns 404 Not Found,
• the underlying data is permanently deleted.

If you need email data beyond your retention window, export it while it is live, for example by consuming webhooks and storing events on your side.

​

Scheduled emails

An email can be scheduled at most 30 days in advance. A scheduled email’s retention window starts when the email is actually sent, not when you made the API call, so a scheduled email is never expired before it sends. The maximum lifetime of a message in Nuntly is therefore the scheduling delay (up to 30 days) plus your retention window.

​

API request logs

The request log shown on the observability API view follows a flat 30-day platform retention for all plans. It is operational logging, separate from your email records, and does not follow extended retention windows. The webhook delivery log (the delivery attempts shown on the webhooks observability view) is also an operational record with a bounded retention of its own, independent of your retention window. Webhook payloads already delivered to your endpoint are your own copies. See the Data Processing Agreement for the per-category periods.

​

The inbox is different

The inbox is a transactional mailbox. Its stored messages are bounded by a storage quota, not by time: a received message stays in your inbox until you delete it, within the mailbox storage quota. Time-based retention does not purge inbox messages. Sending from the inbox (a reply, a forward, or a new message) goes through the regular sending pipeline, so it also produces an outbound email record. That record follows your organization’s retention window like any other send, while the inbox keeps its own copy of the message for display. The two copies have independent lifetimes: the outbound record can expire while the inbox copy remains in your mailbox.

​

Account deletion

Deleting your account deletes all your data, on every store, regardless of the remaining retention window. This includes inbox messages, which have no time-based retention of their own. Residual encrypted backup copies age out within 7 days. See the Data Processing Agreement for the full retention and deletion commitments.

​

Learn more