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

# Privacy

> What the Talqui chat collects and stores, to fill in the App Store and Google Play privacy forms and your cookie policy.

## What is sent to Talqui

Only what the user types or sends, and what your code passes to the chat:

| Data | When |
| - | - |
| Messages, images, files and voice messages | When the user sends them |
| Name, email and phone | When the user fills in the pre-chat form, or your code calls `identify` / `setContact` |
| Contact and conversation metadata | When your code calls `setContactMeta` / `setSessionMeta` |
| A visitor ID | Always: a random ID created by the chat, or the `userHash` from your backend |
| Push token | Only if your app calls `setPushToken`, or the user accepts browser notifications |
| Chat version and platform | Always, to deliver compatible features |

The chat doesn't read contacts, location, the advertising ID, other apps or files the user didn't pick. Camera and microphone are used only while the user takes a photo or records a voice message.

## App Store and Google Play forms

Use this as a starting point for the **App Privacy** section (App Store Connect) and the **Data safety** form (Google Play Console). Adjust it to what your app actually sends.

| Data type | Collected | Linked to the user | Purpose |
| - | - | - | - |
| Name, email address, phone number | When provided | Yes | App functionality (customer support) |
| Other user content (messages) | Yes | Yes | App functionality (customer support) |
| Photos or videos, audio | When the user sends them | Yes | App functionality (customer support) |
| User ID (visitor ID or `userHash`) | Yes | Yes | App functionality |
| Device ID (push token) | Only with push notifications | Yes | App functionality (notifications) |

* Not used for tracking or advertising, and not shared with data brokers.
* Data is encrypted in transit (HTTPS).
* Users ask for access or deletion through your own support channel, as for the rest of your app's data.

## What stays on the device

| Platform | Stored | Where |
| - | - | - |
| Website | Visitor ID, the contact details the visitor entered, cached operator names and avatars | `localStorage` of your site (keys starting with `talqui:`); the visitor ID also in the first-party cookie `talqui_shadowID` as a fallback |
| React Native | Visitor ID | AsyncStorage, owned by the SDK |
| Flutter | Visitor ID | SharedPreferences, owned by the SDK |

`reset()` (website) and `logout()` (apps) clear the contact details and replace the visitor ID with a new one, so nothing links the device to the previous user. On the website, list it in your cookie policy as a functional item: it keeps the conversation when the visitor comes back.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.