Where Does SwiftKey Store Learned Data?
SwiftKey learns locally by default on Android and iOS, with opt-in account sync and newer OneDrive dictionary backups. Models live on device.
Last updated
SwiftKey defaults to keeping your typing to itself. Learned language models sit on the device with nothing leaving unless an account with sync is switched on. That local-first stance is documented, not assumed.
Backup arrives in layers. Account sync carries learned data and themes across devices, with OneDrive hosting newer dictionary backups in your own storage. The data portal adds export and deletion. Exact on-disk filenames come from community teardowns and stay qualified as version-sensitive.
Where SwiftKey stores this, by platform
/data/data/com.touchtype.swiftkey
Private storage for the verified SwiftKey package with language models and prefs inside. Exact filenames come from unofficial teardowns and vary by version. Sync is opt-in through Account Backup and Sync.
/var/mobile/Containers/Data/Application/<guid>/Documents
Sandboxed container with the extension bridged through Full Access. iOS bundle paths come from third-party analyzers rather than Microsoft docs. Same local-by-default model with OneDrive backup rolling out.
Frequently asked questions
How do I sync SwiftKey to a new phone?
Use Account Backup and Sync inside the app, now rolling into OneDrive with a human-readable dictionary plus the machine model in your own storage. Default state syncs nothing at all. Deletion runs through the data portal with device removal as a separate step.
Does SwiftKey upload my typing?
Nothing leaves unless you opt in. Microsoft documents local-only learning as the default with account sync strictly voluntary. Themes and language data follow the same rule, so a signed-out install is fully offline.
How do I export my SwiftKey words?
Open the data portal for word-list snapshots, typing stats and deletion controls. Export-all captures the vocabulary while backup deletion and account removal sit beside it. Full Access on iOS only bridges the extension with the container app.
Notice an outdated path? Let us know.