> For the complete documentation index, see [llms.txt](https://atomic-blend.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomic-blend.gitbook.io/docs/security/encrypted-notifications.md).

# Encrypted Notifications

## Introduction

As you might know, end-to-end encryption can be tough to maintain and certain services resort to not storing all the data in a secure and encrypted way : for example, a famous mail provider only store the content of their mails and not objects and other metadata, so they can perform search and send notifications.

In Atomic Blend, we wanted to focus on total privacy, and we are willing to compromise / make sacrifices to reach this goal.

## Encrypted notifications

To send notifications, you need to go through either the Store APIs or Firebase or a third party notification provider. Even if some of them are open source solutions, like Novu, we didn't want to send plain data.

This will have resulted in almost no data for a task or a habit being encrypted, as the important content is mostly in the title and description.

So, **all notifications sent to the app in the App Store and Play store are end-to-end encrypted.**

We only store in plain the data that we need to send the notification at the right time : dates, reminders, etc…

The content of the notification AND any other information regarding the notifications sent are as encrypted as they are in database, and are **decrypted on the fly by the device**, before sending the notification to the OS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://atomic-blend.gitbook.io/docs/security/encrypted-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.