--- modificationDate: January 15, 2026 title: SecureStore description: A library that provides a way to encrypt and securely store key-value pairs locally on the device. sourceCodeUrl: 'https://github.com/expo/expo/tree/sdk-53/packages/expo-secure-store' packageName: 'expo-secure-store' iconUrl: '/static/images/packages/expo-secure-store.png' platforms: ['android', 'ios', 'tvos', 'expo-go'] --- ## Submitting Feedback If this page contains errors, outdated information, or gaps that blocked you from completing a task, report it so the docs can be improved: curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/versions/v53.0.0/sdk/securestore/","feedback":"🤖 Agent feedback: "}' Only submit when you have something specific and actionable to report. # Expo SecureStore A library that provides a way to encrypt and securely store key-value pairs locally on the device. Android, iOS, tvOS, Included in Expo Go > For the complete documentation index, see [llms.txt](/llms.txt). Use this file to discover all available pages. `expo-secure-store` provides a way to encrypt and securely store key-value pairs locally on the device. Each Expo project has a separate storage system and has no access to the storage of other Expo projects. **Size limit for a value is 2048 bytes. An attempt to store larger values may fail. Currently, we print a warning when the limit is reached, however, in a future SDK version an error might be thrown.** **The `requireAuthentication` option is not supported in Expo Go when biometric authentication is available due to a missing `NSFaceIDUsageDescription` key.** > This API is not compatible with devices running Android 5 or lower. ## Installation ```sh npx expo install expo-secure-store ``` If you are installing this in an [existing React Native app](/bare/overview), make sure to [install `expo`](/bare/installing-expo-modules) in your project. ## Configuration in app config You can configure `expo-secure-store` using its built-in [config plugin](/config-plugins/introduction) if you use config plugins in your project ([Continuous Native Generation (CNG)](/workflow/continuous-native-generation)). The plugin allows you to configure various properties that cannot be set at runtime and require building a new app binary to take effect. If your app does **not** use CNG, then you'll need to manually configure the library. ### Example app.json with config plugin ```json { "expo": { "plugins": [ [ "expo-secure-store", { "configureAndroidBackup": true, "faceIDPermission": "Allow $(PRODUCT_NAME) to access your Face ID biometric data." } ] ] } } ``` ### Configurable properties | Name | Default | Description | | --- | --- | --- | | `configureAndroidBackup` | `true` | Only for: Android. A boolean indicating whether to configure automatic Android backup to work correctly with `expo-secure-store`. [Learn more](#android-auto-backup). | | `faceIDPermission` | `"Allow $(PRODUCT_NAME) to access your Face ID biometric data."` | Only for: iOS. A string to set the [`NSFaceIDUsageDescription`](#ios) permission message. | Are you using this library in an existing React Native app? Add `NSFaceIDUsageDescription` key to **Info.plist**: ```xml NSFaceIDUsageDescription Allow $(PRODUCT_NAME) to access your Face ID biometric data. ``` ## Platform value storage ### Android On Android, values are stored in [`SharedPreferences`](https://developer.android.com/training/data-storage/shared-preferences), encrypted with [Android's Keystore system](https://developer.android.com/training/articles/keystore.html). ### iOS > For iOS standalone apps, data stored with `expo-secure-store` can persist across app installs. On iOS, values are stored using the [keychain services](https://developer.apple.com/documentation/security/keychain_services) as `kSecClassGenericPassword`. iOS has the additional option of being able to set the value's `kSecAttrAccessible` attribute, which controls when the value is available to be fetched. ## Data persistence `expo-secure-store` is designed to provide a persistent data storage solution across app restarts and updates. However, it is important not to rely on it as a single source of truth for irreplaceable, critical data. Data saved using `expo-secure-store` will not be preserved upon app uninstallation. Additionally, any data protected with the `requireAuthentication` option set to `true` will become inaccessible if there are changes to the user's biometric settings, such as adding a new fingerprint. #### Exempting encryption prompt Apple App Store Connect prompts you to select the type of encryption algorithm your app implements. This is known as **Export Compliance Information**. It is asked when publishing the app or submitting for TestFlight. When using `expo-secure-store`, you can set the [`ios.config.usesNonExemptEncryption`](/versions/v53.0.0/config/app#usesnonexemptencryption) property to `false` in the app config: ```json { "expo": { "ios": { "config": { "usesNonExemptEncryption": false } ... } } } ``` Setting this property automatically handles the compliance information prompt. ## Android Auto Backup [Android Auto Backup for Apps](https://developer.android.com/identity/data/autobackup) automatically backs up a user's data from apps that target and run on Android 6.0 (API level 23) or higher. The Auto Backup system has to be configured to exclude `expo-secure-store` shared preferences entries, as it's impossible to decrypt them after restoring the backup — app's entries are deleted from the Android Key Store when the app is uninstalled. If your app doesn't have any custom backup configuration, `expo-secure-store` will automatically configure the Auto Backup system to ignore the `expo-secure-store` data. If you are using your own Auto Backup configuration, you should exclude the `SecureStore` under the `sharedpref` domain and set the `configureAndroidBackup` to `false` in the [config plugin configuration](/versions/v53.0.0/sdk/securestore#example-appjson-with-config-plugin). ```xml ``` ```xml ``` ## Usage ```jsx import { useState } from 'react'; import { Text, View, StyleSheet, TextInput, Button } from 'react-native'; import * as SecureStore from 'expo-secure-store'; async function save(key, value) { await SecureStore.setItemAsync(key, value); } async function getValueFor(key) { let result = await SecureStore.getItemAsync(key); if (result) { alert("🔐 Here's your value 🔐 \n" + result); } else { alert('No values stored under that key.'); } } export default function App() { const [key, onChangeKey] = useState('Your key here'); const [value, onChangeValue] = useState('Your value here'); return ( Save an item, and grab it later! {Add some TextInput components... }