Backup policy

Note: This is the June 2026 version of the Betty Blocks backup policy. This policy will be reviewed regularly and may be amended from time to time.

This document outlines our procedures and guidelines for backing up critical data and ensuring its recoverability in the event of a data loss event. Our backup policy is an essential part of our IT risk management strategy and provides a framework for ensuring the continuity of our operations.

Backup scheme

Betty Blocks distinguishes between two types of data that are included in its backup scheme:

Databases: All structural data stored in the Betty Blocks–managed databases that support its services.
Assets: All files uploaded by users (both developers and end users) of applications hosted on Betty Blocks, as well as files generated through the use of those applications.

Betty Blocks adheres to the following principles regarding backups:

Type	Frequency	Backup	Retention
Database	Daily	One backup per day to an off-site location	Stored for at least 30 days
Database	Weekly	One backup per week to an off-site location	Stored for at least 8 weeks (after the retention of the daily backups)
Database	Monthly	One backup per month to an off-site location	Stored for at least 4 months (after the retention of the daily backups)
Assets	Continuous	Replication to an off-site location	All file updates (n.b. changes and/or removals) are recorded for a period of 120 days, allowing for restoration of file versions during this period.

At what time does Betty Blocks make a backup?

Database retention across all Betty Blocks hosted zones, covering both data and metadata databases.

Zone	Meta database*	Data database*	Timezone	Location
NL3	03:00 AM	03:00 AM	CET	West-Europe
US2	03.00 AM	03.00 AM	ET	US-West
CA3	03.00 AM	03.00 AM	ET	Canada Central

Note: It is possible that although the backup process may begin at a specific time, individual backups for databases may not start until a couple of hours after the starting time due to the time required to create backups for each database.

What does the data restore process look like?

Data restore

Backup restoration can be requested. An official request needs to be submitted by the client to the Betty Blocks support team. It will be a backup restore of the complete data and not of specific parts.
Costs for restoring a backup are charged to the client subsequently.
Restoring a daily backup will take about approximately 4 hours. Response times are based on the SLA.
Restoring a specific backup from a point in time is possible for the last 7 days. This will take approximately 24 hours. Response times are based on the SLA.

Metadata restore

Backup restoration can be requested. An official request needs to be submitted by the client to the Betty Blocks support team. It will be a backup restore of the complete data and not of specific parts.
Costs for restoring a backup are charged to the client subsequently.
Restoring a daily backup will take about approximately 4 hours. Response times are based on the SLA.
Restoring a specific backup from a point in time is possible for the last 7 days. This will take approximately 24 hours. Response times are based on the SLA.
Replacing a metadata backup is more complex and therefore not advised.

Storage

For Azure environments, the database backups are stored in Azure storage accounts (under File Shares) via SMB. They are only accessible from whitelisted IP addresses (office and VPN) with required access rights.

Response times

Response times are based on the agreed Platform SLA.
Response times based on the standard Platform SLA, are based on ‘best effort’ with a support window based on office hours between 09:00 AM and 05:00 PM (CET). Outside office hours there will be no response.

Response times follow the agreed Platform SLA. For the standard Platform SLA, response is provided on a best-effort basis during office hours from 09:00 AM to 05:00 PM (CET); there is no response outside these hours.

This policy is reviewed on a regular basis and may be updated periodically.