We can't read your messages.
That's the whole policy.

UVChat may use a phone number during registration or account verification only to send an OTP and confirm that the user controls that number.

After verification, UVChat uses a UVID-based identity and routing system for normal service operation. A UVID is designed to be privacy-preserving and non-reversible, so normal messaging does not depend on exposing the user's phone number as the public account identity.

UVChat does not use phone numbers for advertising, profiling, contact discovery, social-graph building, or behavioural analysis. UVChat does not expose a user's phone number to other users as part of normal messaging.

UVChat does not perform automatic contact discovery.

UVChat does not upload your address book to match it against other users. UVChat does not build a social graph from your contacts and does not learn who you know from your phone's contact list.

You connect with people through UVID-based connection flows, not by silently turning your address book into a discovery database.

When a user triggers SOS, alert information is sent only to the trusted contacts selected by the user, except where law or emergency obligations require otherwise.

SOS data may include:

• Sender UVID and incident identifier
• Emergency status, delivery and acknowledgement state
• Location context where permission is granted and required for the alert
• Battery or device-safety context where supported
• Optional safety-profile information configured by the user

Location is used only for emergency, safety, routing, and reliability purposes. It is not used for advertising, profiling, or unrelated marketing.

SOS information is not sold. It is not broadcast publicly. It is not used to train AI models.

UVChat does not show read receipts to the sender. UVChat does not show last-seen or online status in a way that allows other users to monitor a person's daily activity patterns.

The sender may see delivery state where needed to confirm whether a message reached the recipient's device. Delivery state is used for reliability — not behavioural visibility.

Nivio helps users understand saved family records, notes, prescriptions, receipts, and important documents.

Nivio is designed around visible source grounding. It shows what it is using as source material and avoids invisible guessing.

Nivio records are private user content. They are not sent to cloud AI, online LLMs, or external AI systems for analysis, transcription, profiling, or training.

UVChat supports multilingual communication.

Translation is designed to run on the user's device using downloaded language packs where supported. Private messages are not sent to cloud translation services as part of the UVChat translation flow.

UVChat does not send private messages, voice, documents, or family data to online LLMs, external AI systems, or cloud translation services.

Voice-to-text transcription is not currently a UVChat feature.

UVChat does not provide server-side transcription of private voice content.

UVChat does not send private voice content to cloud transcription services, online LLMs, or external AI systems.

If transcription is introduced in the future, it must run within UVChat's privacy boundary and must not send private voice content outside the user's device.

UVChat is designed to hold as little as possible, for as little time as possible. Different categories follow different windows:

• Encrypted message blobs in transit — held only until the recipient device acknowledges delivery, then dropped.
• Routing metadata — retained for a defined operational window for delivery, abuse-prevention, and reliability, then aggregated or purged.
• Account record (username + public key) — held while the account is active. Deleting the account removes both.
• Aggregated, de-identified telemetry — may be retained without an expiry, because it is not personal.

Account deletion is available from inside the app and removes your username, public key, and any routing metadata still tied to you, within applicable retention windows. Conversations on the other devices in a thread are not under our control to delete.

UVChat does not sell data, does not rent data, and does not share user activity with advertisers, ad networks, or data brokers. Ever.

The only parties that touch UVChat operations are:

• Our infrastructure providers — for hosting, secure storage of encrypted blobs, and routing, under standard data-processing agreements.
• Lawful authorities — only when required by valid legal process, and only for the narrow scope demanded. The honest list of what is and isn't producible is in the section above.

UVChat does not have a B2B "data product." There is no API for advertisers, no segmentation tooling, and no dashboard a third party could buy access to.

UVChat is built so that most user-rights questions are short to answer — because the data set we hold about you is small by design.

• The right to access the account record we hold for you (username, public key, recent routing metadata).
• The right to correct your username or public key, where applicable.
• The right to delete your UVChat account in-app, at any time.
• The right to contact a real human on the privacy team and receive an answer.

Identity verification for these requests is handled in-app via your account credentials, scoped to the minimum needed to confirm the request is yours.

Permissions. UVChat asks for permissions only when a user-requested feature needs them — location for SOS context, microphone for voice messages, notifications for delivery and alerts, contacts only when the user explicitly initiates a connection flow. Permissions can be revoked from the device's system settings at any time.

Local storage, export & deletion. Conversation history is stored on your device. You can export your local data and delete your UVChat account in-app. Deleting the account removes your UVID, account record, and any routing metadata still tied to you within applicable retention windows.

Service providers & operational processing. UVChat uses infrastructure providers for hosting, secure storage of encrypted payloads, and routing, under standard data-processing agreements. None of these providers are used as cloud-AI, LLM, or transcription endpoints for private user content.

Security. UVChat uses end-to-end encryption for private messages, transport-layer encryption for everything in transit, and standard hardening for accounts, sessions, and infrastructure. Security disclosures are welcomed at the contact address below.

Children & family use. UVChat is intended for use by family members of appropriate age under the laws of the user's jurisdiction. Trusted-circle setups for older relatives or younger family members should be configured by an adult guardian.

Changes to this policy. Material changes are dated and announced in-app and on this page. The current version is shown in the header above. Changes that affect what UVChat holds or how it routes private content will not be buried in a settings menu.

Contact. Privacy questions, security disclosures, regulatory queries, and research requests are read by a real person on the UVChat team. Use the contact link below.