---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Data security

# Data security for ServiceNow mobile apps {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

ServiceNow mobile apps use SSL/TLS for Over-the-Air (OTA)
communication encryption for data security. The OAuth authorization endpoints are
HTTPS.

## Data stored in your mobile apps {#sg-mobile-security-data__section_ofp_hwz_ddb}

Application preference data such as favorites, home screen, and the mobile navigator items are stored and cached locally on the mobile device. ServiceNow mobile apps do not store record data such as incidents and problems on the device unless your organization has specifically enabled offline syncing for Field Service. The record data is encrypted with AES 256.  
Information stored in mobile apps

* Databases
  * User defined instances
  * Favorite application IDs
  * Push Notifications
  * Geolocation updates
  * Offline data
  {#sg-mobile-security-data__ul_ph2_fxn_dhb}
* Preferences stored in mobile apps
  * sys_id, display name, username, and initials of the current user
  * URL and name of the current instance
  * Last activity timestamp
  * Encrypted PIN code
  * Offline cache warning period
  * Server Properties
    * LOCATION_PROXIMITY
    * IS_PIN_CODE_REQUIRED
    * IS_BLURRED_IN_BACKGROUND
    * IS_BLOCK_ATTACHMENT_SHARING
    * LOCATION_TRACKED
    * IS_CLEARING_CLIPBOARD_IN_BACKGROUND
    * IS_HIDE_APPLICATIONS_SCREEN_IMAGE
    * IS_OFFLINE_ENABLED
    * LOCATION_FREQUENCY
    {#sg-mobile-security-data__ul_izc_4xn_dhb}
  * key_analytics_initial_app_launch flag
  {#sg-mobile-security-data__ul_jvg_hxn_dhb}
* Information stored in the system Account Manager
  * Login date
  * Instance URL
  * Access Token
  * Refresh Token
  {#sg-mobile-security-data__ul_rlc_wxn_dhb}
{#sg-mobile-security-data__ul_kxg_dxn_dhb}

## Data in motion {#sg-mobile-security-data__section_zzh_3wz_ddb}

Data in motion is over a secure SSL/TLS channel and encrypted with HTTPS.

## Offline access and data cache configuration {#sg-mobile-security-data__section_k4d_kwz_ddb}

Choose specific screens and actions to be enabled offline from with Mobile App Builder. On the mobile device, your users can select offline and choose to "cache data" from Settings. The offline flows that you designate are downloaded and cached to the device.

You can encrypt offline cached data by using native encryption. This encryption expires at
a specified period of time. The default is 48 hours or when a user signs out of the mobile
app.

Offline data is protected by local-auth and the app PIN that can be optionally enabled by
administrators. When enabled, users are required to enter a PIN on login, or when the
application is inactive for five minutes.

## Disabling mobile attachments {#sg-mobile-security-data__section_vvb_gvw_njb}

You can disable attachments for mobile apps by using access control rules. For more details
on this process see [Disable attachments in mobile
apps](https://servicenow-prod.fluidtopics.net/4rBYHf6BVfQ3vTsasX_VoA "Disable attachments for mobile apps by using access control rules.").