FAQ

Why do some apps not allow to get backed up?

Android gives apps the option to opt-out of the system backup. Many privacy respecting apps used this option to prevent user data ending up on Google servers. Unfortunately, this also affects encrypted backups done via Seedvault as the opt-out is enforced by the system.

It is not yet widely known that backups can now be encrypted with a device key and even Google claims that it can not access backup data [audit]. Instead of opting out completely, app developers can say that their app should only get backed up, if the backup is encrypted.

So if you are annoyed that your favorite app is not included in backups, you can contact the app's developers and make them aware of this option. For example, this is how the Transportr app enabled only encrypted backups.

However, keep in mind that some security critical apps such as Signal or Briar might still have good reasons to opt-out of backup completely.

Why do apps not get backed up when not recently used?

An app that carries FLAG_STOPPED will be excluded from backups by the system.

This can happen if an app

• has been force-stopped (e.g. by the user in settings or a task killer)
• has been cleared
• has just been installed (and was not yet used)

A user can notice this by looking at the timestamp of the apps in the "App backup status" page. However, if an app gets used, it will not be stopped and thus get backed up.

Where is my backup stored?

It is saved in the .SeedVaultAndroidBackup directory in your chosen backup location. On non-Windows systems this is a hidden folder due to the . prefix. As syncing hidden files is disabled in the Nextcloud desktop clients by default, the backup data does not end up on your connected desktop clients. If you have the synchronization of hidden files enabled and use Nextcloud, it is recommend to put .SeedVaultAndroidBackup on your exclude list.