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

# Coming next

> What the next two Veriqa releases are preparing: pseudonymized channel identifiers, anomaly detection, sign-in with Google, Apple and Huawei as a separate service, and device binding levels.

<Note>
  These are plans, not a commitment to dates: what each release contains may change.
</Note>

## Next release: privacy and risk signals

**Pseudonymized channel identifiers.** Today `channel_user_id` is the platform's native identifier:
a Telegram ID, a WhatsApp ID, an email address. A new tenant mode replaces it below the channel
adapter with a deterministic pseudonym under a key Veriqa does not store, and trims the set of
stored claims. A database leak no longer links a person to the address that reaches them in a
messenger.

**Anomaly detection for the initiator context.** Veriqa remembers derived, non-personal signals of
confirmed sign-ins — the country and the device type — and flags a sign-in that does not match
them. IP, User-Agent and city are not stored. It is opt-in: until you turn it on, nothing
changes.

## The release after: new ways to sign in and device binding

**Sign-in with Google, Apple and Huawei as a separate service.** A container next to Veriqa,
connected by configuration through the HTTP channel: the sign-in device shows a QR code, the user
signs in to their account on the phone and confirms on a "Yes / No" page. It helps on devices with
no keyboard and for people who do not use any messenger.

**Binding levels between the initiator and the confirmer.** Levels of trust between the device where
the sign-in started and the device where it is confirmed — from the base level up to a "same device"
policy for scenarios where confirming from someone else's phone must not be possible.


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