Where Does iodéOS Store Blocker and Store Data?
iodéOS keeps its blocker rules and store caches in private app data, with SeedVault for system backup.
Last updated
iodeOS ships its own system wide blocker alongside Aurora Store and F-Droid for apps. Blocker rules and per-app network choices sit in private storage for the blocker package, while each store keeps its own cache in a separate directory. Clearing a store entry leaves the blocker untouched, and clearing the blocker leaves the stores alone.
Support requests go faster with exact package names, since this layout is often confused with /e/OS and its App Lounge, which iodeOS does not include. For device moves, use the SeedVault flow under Settings System Backup to USB, Nextcloud over WebDAV or on-device storage. Restores apply during setup on the new device rather than through hand copies of private folders.
Where iodéOS stores this, by platform
/data/data/com.iode.app
Blocker rules and per-app network settings. Stores (Aurora, F-Droid) keep separate private dirs. Backup via SeedVault, not raw copy.
Frequently asked questions
How do I back up iodéOS?
Open Settings, System, Backup with SeedVault integrated. Backups go to USB, Nextcloud via WebDAV or on-device storage under .SeedVaultAndroidBackup. Restores apply during new device setup.
Where are iodéOS store and blocker data?
Aurora Store plus F-Droid ship instead of App Lounge, which belongs to /e/OS. Blocker rules live under com.iode.app. Clearing store storage never touches the blocker.
Notice an outdated path? Let us know.