---
title: "Data Backup and Retention"
slug: "data-backup-and-retention"
updated: 2026-09-21T17:53:16Z
published: 2026-09-21T17:53:16Z
canonical: "docs.unqork.io/data-backup-and-retention"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Backup and Retention

Unqork automatically backs up application data and critical components behind the scenes. Understanding the backup and retention schedule helps organizations plan disaster recovery (DR) and recover lost data when needed.

Backups do not guarantee data recovery in all cases. Data lost because of misconfiguration, accidental deletion, or issues outside critical infrastructure failures may not be recoverable. Use role-based permissions to limit access to Unqork environments, and follow best practices for saving and deleting data.

## Data Redundancy

Unqork uses Active-Active load balancing with at least two application instances running in at least two different availability zones (AZs). Unqork stores passive disaster recovery data in two or more AZs or regions per cloud provider. All data replicates across AZs in real time. Disaster recovery runs in the client's primary hosting location for the affected service.

## Data Backups

Unqork stores two primary types of data: database data and object storage data. Production environments have continuous backup for point-in-time restore. Unqork retains transactions for a minimum of 6 hours, or until the maximum oplog size is reached.

Any component or service with a retention limit, like service logs, is not retrievable beyond that limit. To keep records longer, change the retention setting in Unqork or set up an internal archival process. Data outside the retention window is not recoverable from a DR backup.

The default backup and retention schedule for all environment databases, including submissions and configurations, is:

| Snapshot Type | Frequency | Retention |
| --- | --- | --- |
| **Hourly Snapshot** | Every 6 hours | 2 days |
| **Daily Snapshot** | Once daily | 7 days |
| **Weekly Snapshot** | Every Saturday | 4 weeks |
| **Monthly Snapshot** | Last day of the month | 12 months |

> [!NOTE]
> The Hourly Snapshot runs every 6 hours, not every hour.

Client data stored by a cloud storage provider (CSP) requires a client request to delete, unless a customer agreement specifies otherwise. Data deleted by a Creator with client-assigned permissions is not recoverable if an administrator deletes the Creator's account before the next incremental backup. All personal and non-public data is tagged to support international compliance regulations.

## Data Storage

All data backups are stored in the same geographic region, distributed across multiple sites. Legal data holds might require additional steps. Contact the Unqork legal department before moving or deleting data subject to a hold request.

---

**Changelog**

| Date | Change |
| --- | --- |
| 2026-09-21 | Imported and updated for UnqorkAI documentation. |

An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity.

The Production environment is the final stage of the development process. Use this environment to promote tested and functioning application so your end-user can interact with it.

A CSP (cloud service provider) is a company that delivers cloud computing services like storage, databases, and infrastructure to organizations over the internet, allowing users to access computing power, data storage, and applications on demand without managing their own physical hardware, typically paying only for the resources they use.

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.