<!-- source: https://www.photorobot.com/security/disaster-recovery | Generated 2026-11-19 from the rendered pages of the website; language: en. -->

# PhotoRobot Disaster Recovery Policy

> The PhotoRobot Disaster Recovery Policy describes how PhotoRobot recovers platform functionality during large-scale disruptions.

[PhotoRobot Security - Overview](https://www.photorobot.com/security/security-overview)

[PhotoRobot Architecture & Data Flow](https://www.photorobot.com/security/architecture)

[PhotoRobot Security Measures Summary](https://www.photorobot.com/security/security-measures)

[PhotoRobot Business Continuity & DR Overview](https://www.photorobot.com/security/business-continuity-dr)

[PhotoRobot AI Governance Summary](https://www.photorobot.com/security/ai-governance)

[PhotoRobot Information Security Policy](https://www.photorobot.com/security/information-security)

[PhotoRobot Access Control Policy](https://www.photorobot.com/security/access-control)

[PhotoRobot Incident Response Policy](https://www.photorobot.com/security/incident-response)

[PhotoRobot Backup Policy](https://www.photorobot.com/security/backup)

[PhotoRobot Disaster Recovery Policy](https://www.photorobot.com/security/disaster-recovery)

[PhotoRobot SDLC Security Policy](https://www.photorobot.com/security/sdlc-security)

[PhotoRobot Change Management Policy](https://www.photorobot.com/security/change-management)

[PhotoRobot Logging & Monitoring Standard](https://www.photorobot.com/security/logging-monitoring)

[PhotoRobot Technical and Organizational Measures (TOMs)](https://www.photorobot.com/security/toms)

Last edited: Dec 29, 2025

# PhotoRobot Disaster Recovery Policy

This document defines the PhotoRobot Disaster Recovery Policy. It describes how PhotoRobot recovers platform functionality during large-scale disruptions, and supports compliance with PhotoRobot’s contractual obligations under the DPA and SLA.

## Purpose

- Ensure controlled, timely recovery of services

- Minimize downtime

- Prevent data loss

## Scope

Applies to:

- Complete service outage

- Regional service interruption

- Critical infrastructure failures

## DR Strategy

- **Single-region** GCP deployment (europe-west4)

- Recovery based on restoring backups

- Engineering-driven recovery workflow

- No multi-region failover at this stage

## Recovery Priorities

1. Core infrastructure

2. Database and metadata

3. Processing pipelines

4. Public APIs

5. UI / account access

## DR Procedures

- Incident commander activates DR plan

- Systems restored in priority order

- Verification of integrity and functionality

- Communication to stakeholders when required

## Recovery Testing

- DR procedures reviewed periodically

- Tabletop exercises conducted when appropriate
