Backup and continuity policy

1. Scope

This policy applies to the production environment of UWOD. Test and development environments may have different or uncovered backup routines and are not protected by the SLA.

2. Backup routines

• AppByte maintains regular backup routines of the productive Platform, per the capabilities of the database provider (MongoDB Atlas) and file storage provider (Cloudinary).
• Backups are periodically verified to confirm they can be used in the events that require them.
• Backup retention follows the Privacy policy: typically 30 to 90 days, with overwrite under the normal cycle subject to legal retention.

3. Restoration

• Production restoration after an incident affecting data integrity is initiated by AppByte per its internal procedures.
• Full or partial restoration upon Customer request (for example, recovery of data deleted by the Customer or of a specific historical version) may carry a cost depending on complexity and availability and is handled case by case.
• AppByte does not guarantee that data deleted by the Customer can be recovered, especially outside the backup retention window.

4. RPO / RTO

By default, AppByte does not guarantee specific RPO (recovery point objective) or RTO (recovery time objective) values. AppByte makes commercially reasonable efforts to minimize data loss and restoration time. Quantitative commitments may be agreed in writing through specific proposals or annexes.

5. Service continuity

• AppByte works with established cloud providers (Contabo, MongoDB Atlas, Cloudinary, Cloudflare, Sentry, Resend) that provide their own operational resilience.
• Scheduled maintenance runs in low-traffic windows with reasonable notice; emergency maintenance may occur without prior notice when a security or stability risk exists.
• For major events beyond AppByte's reasonable control (force majeure, fortuitous events, cloud or connectivity provider failures), AppByte will coordinate the recovery actions within its reach.

6. Customer responsibilities

• Technical backups maintained by AppByte do not replace the Customer's accounting, tax or legal obligations to keep its own backups.
• The Customer may export its operational data from the Platform at any time (CSV, Excel or JSON depending on the module) and should do so with the frequency its operation requires.
• After contract termination, the 30-calendar-day export window described in the Terms of service applies.
• The Customer is responsible for keeping its own backups of information it needs to meet legal, accounting or audit obligations.

7. Limitations

This policy does not constitute a guarantee of uninterrupted continuity, absence of data loss or immediate recovery. The liability limitations in the Terms of service apply fully to this policy.