---
title: "Encrypted mobile push"
slug: "encrypted-mobile-push"
updated: 2026-06-08T21:25:19Z
published: 2026-06-08T21:25:19Z
canonical: "docs.xtremepush.com/encrypted-mobile-push"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Encrypted mobile push

Encrypt push messages to devices

> [!TIP]
> Enterprise Push Package
> 
> Encrypted mobile push is part of the Xtremepush Enterprise Push package, which is a paid feature. Please review our dedicated [guide](/documentation/docs/enterprise-push-package) for more details.

Once encrypted mobile push messages are enabled for a project, all messages will be sent as encrypted if possible, but will fall back to unencrypted where the device cannot receive the encrypted message.

If a particular campaign *requires* the message to be encrypted, then it can be enforced via the **Segment** tab for a single-stage campaign by selecting the option **Enforce encryption**.

![](https://cdn.document360.io/b056e88b-f6c1-4bd2-b5b8-08e9336a17c9/Images/Documentation/76d1ace-Screenshot_2022-10-14_at_14.59.52(1).png)

When encryption is enforced, the campaign will not be sent to devices which cannot receive encrypted messages – the [**Notifications Log**](/documentation/docs/notifications-log) will display the reason why the send failed.

> [!TIP]
> SDK versions
> 
> For a device to receive encrypted push messages, your mobile app must be using at least [Android SDK v8.1.0](/documentation/docs/android-sdk-releases) or [iOS SDK v4.1.11](/documentation/docs/ios-sdk-releases).

> [!NOTE]
> API triggered campaigns
> 
> If you are using the [Campaign Execute](ref:api-campaign#campaign-execute) API method, your requests must include the encrypted parameter. See the `encryption` parameter in the [campaign create](ref:campaign-create) endpoint guide.