Translation backups & restore
StringJet stores your canonical translation values in the cloud. Backups capture snapshots of that data so you can recover from mistakes, bad imports, or experiments — with cadence and retention that depend on your plan.
What is included
Each backup stores a snapshot of translation rows as they exist in StringJet at that point in time. Automated backups follow the schedule for your tier (for example weekly or daily); see the comparison table on pricing for retention windows.
Manual backups
When your plan allows, project owners can run a manual backup before large merges or migrations. If manual backup is disabled, upgrade or wait for the next automated snapshot.
Restore semantics
Restore replaces translation values in the project from the selected snapshot — a destructive operation by design, so confirm in the dialog. Removing a backup file only deletes that snapshot from storage; it does not roll back live strings until you explicitly restore a different snapshot.
Relation to OTA
Backups protect your editor state. After restoring, rebuild OTA bundles if you need devices to pick up reverted copy.