An anonymous OTT Navigator backup can be restored using its generated access information. Treat the code like private configuration access, and use the supported protection options. A code posted in a public group can expose a backup to people who were never intended to receive it. Keep access information out of support screenshots and public messages. A backup code is a restoration credential for saved configuration, so anyone allowed to use it should be someone authorised to receive the information that restoration contains.
Recognise what the code represents
It is a route to a configuration backup, not a harmless app-version number. The restored configuration can contain information related to provider setup. Label the code by purpose and creation date in your private records so it is not confused with a harmless download shortcut. Check what configuration the chosen backup includes and whether a supported protection option is enabled. A generated code should not be posted just to demonstrate that backup creation succeeded; describe that result without distributing the means of restoration.
Use appropriate protection
Where the app offers password protection, use it and keep the password separately from a public link. Do not assume obscurity of the code is equivalent to controlled sharing. Use an appropriate private password if the installed version offers protection, and communicate any authorised transfer through a controlled route. Storing a code and its password together in a public post defeats their separate roles. Before moving a complex configuration, verify how the destination asks for the code and password so a typing error is not mistaken for a missing or expired backup.
Limit retained copies
After transferring to a replacement device, review the backup’s lifetime and any supported deletion controls. Keep only the private recovery copies you actually need. Review the app's current retention and deletion controls after the move, including any supported automatic removal option. Delete temporary message or clipboard copies you no longer need, but retain a private recovery route appropriate to the household. If the code was exposed, use the available backup-management controls and review whether credential-bearing configuration may have been restored by someone else.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A backup code pasted into a public troubleshooting chat can give other people access to the same configuration. Share a redacted screenshot of the backup result instead of its restoration code. If an authorised transfer is needed, use a private route, apply supported protection and review the backup's lifetime once the destination is working.
Questions about this topic
Is a backup code the same as the Downloader code?
No. A backup code can access personal configuration; a Downloader code points to software.
Can I safely publish the code because it is not a password?
No. Treat its access function as sensitive.
