Data Retention Policy

Data transferred through the system is kept for a specific period of time. See what's the binding policy.

This document functions as a guide to our organizational Data Retention Policy, outlining the Time to Live (TTL) of data within the systems we use.

Orchestration Engine data limitations and storage

	TTL	Description
Webhook events	7 days	The duration within which Emporix stores events data sent to the Event-Receiver Endpoint. All events are stored including the unprocessed ones or those failing authentication.
Process context	No TTL for lifetime of Tenant	The duration within which you can access data stored inside a process context. Data is deleted when the corresponding digital process is deleted.
Submission data	No TTL for lifetime of Tenant	The duration within which you can access submitted form data. Data is deleted when the corresponding magic link is deleted.
User audit logs	No TTL	The duration in which Emporix maintains audit logging information.

Make data limitations and storage

	TTL / Limits	Description
Make scenarios history log storage	60 days	The duration within which you can access detailed logs for each execution in the Make scenario history.
Make scenarios audit logs storage	12 months	The time during which the platform retains audit logs for Make scenarios.
Maximum Make scenario execution time	60 min	The maximum time for which a single Make scenario can run. If the elapsed time surpasses this limit, the Make scenario will result in a failure with a timeout error.
Webhook queue size	10k executions	Incoming webhooks are accumulated in a Webhook queue. The queue may experience accumulation when the corresponding Make scenario, responsible for handling the webhooks, is either disabled (e.g., due to an error) or processes the webhooks at a rate slower than their incoming pace.
Outbound Emails	No limit	Make scenarios do not impose restrictions on the quantity of outbound emails sent. However, keep in mind that some limitations may be set by your setup or infrastructure, such as infrastructure / throughput availability, 3rd party API limits, or a limit related to the account used for a specific application.