1. Information Viest accesses and processes

SMS and MMS

As an SMS/MMS messaging application, Viest accesses the messages stored through Android’s messaging system. This can include message text, sender and recipient addresses, timestamps, read state, message status, conversation information, MMS attachments such as images, audio and video, and technical information needed to send, receive, display, organize, delete, restore, or back up messages.

SMS and MMS are transmitted through Android, your mobile carrier, and the telephone network. Viest does not turn ordinary carrier SMS or MMS into end-to-end encrypted messaging.

Contacts

If you grant Contacts permission, Viest may read contact names, telephone numbers, and related contact information so it can display names, help you select recipients, and associate conversations with people in your device contacts.

Viest does not require Contacts permission for purposes unrelated to messaging.

Phone and subscription information

Viest may access Android telephony and subscription information needed to identify available mobile lines, preserve line identity, choose the appropriate subscription for sending, and maintain correct messaging behavior on devices with one or more SIMs or mobile subscriptions.

Audio and voice notes

If you use voice-note features, Viest may access the microphone to record audio at your request.

Recorded audio is processed as part of the messaging feature and may be attached to an MMS if you choose to send it.

Transcriptions

When you choose to transcribe supported media, Viest uses Android’s on-device speech-recognition facilities.

The current Viest transcription path requires an on-device recognizer rather than intentionally falling back to ordinary cloud speech recognition. Android may download speech-recognition language models when additional language support is requested.

Saved transcripts may be stored locally by Viest and may be included in a Viest backup.

Translations and language identification

When you choose to translate message or transcript text, Viest uses Google ML Kit language-identification and translation components.

Translation and language identification are performed on the device in the current implementation. Required translation models may be downloaded from Google when they are not already present on the device.

Saved translations may be stored locally by Viest and may be included in a Viest backup.

Drafts, organization, and app state

Viest may store application data needed for product features, including drafts, message organization and categories, stars or annotations, translation and transcription state, display preferences, line identity information, pending reversible actions, and other settings necessary to provide the features you use.

This information is primarily stored locally on your device.

Web links and link previews

Viest can display previews for web links contained in messages.

For outgoing messages containing a supported web URL, Viest may automatically retrieve a preview when the preview is not already available in memory.

For incoming messages, Viest presents a Preview control and retrieves the preview when you choose to preview the link.

To create a preview, Viest connects directly to the website identified by the URL. It may also connect to another host to retrieve an image referenced by that web page.

As with an ordinary web request, the destination website or image host may receive information such as your device’s public IP address, the requested URL, request headers, and other ordinary network connection information. Those websites are operated independently of Viest and are subject to their own privacy practices.

Viest does not route link-preview requests through a Viest-operated tracking or advertising server.

2. Backup & Recovery

When you use Viest Backup & Recovery, Viest may include messages, MMS attachments, conversation information, drafts, categories, read state, annotations, transcripts, translations, preferences, line information, and other supported Viest state in a backup.

Viest backup artifacts are encrypted before being retained as Viest backups.

Backup storage is selected through Android’s Storage Access Framework. Viest writes the backup to the storage destination you select or have configured for Backup & Recovery.

That destination may be local device storage, removable storage, or a storage provider that you have connected to Android. If you choose a cloud-backed storage provider, that provider may transfer and retain the encrypted backup through its own service under its own privacy policy and account terms.

Viest does not require a Viest-operated cloud account for Backup & Recovery.

The availability and operation of specific Backup & Recovery features may vary by Viest version. This Privacy Policy describes the data treatment when those features are used and does not promise that every backup mode is available in every release.

3. When information may leave your device

Information may leave the device in the following circumstances.

Viest does not sell personal information.

The current Viest release does not include advertising SDKs or behavioral advertising systems, and it does not use message content to target advertisements.

4. Third parties and platform services

Viest depends on third-party and platform infrastructure for certain features.

Android provides the operating-system messaging provider, contacts provider, telephony functions, permission system, storage framework, media services, and on-device speech-recognition interfaces used by Viest.

Mobile carriers and their partners process SMS and MMS traffic as required to provide carrier messaging.

Google ML Kit provides the on-device language-identification and translation technology used by Viest and may provide downloadable language models.

Android speech-recognition providers may provide and download the on-device recognition models used for transcription.

Websites and image hosts receive ordinary network requests when Viest retrieves link previews.

A storage provider selected by you may receive and retain an encrypted Viest backup if that provider is the destination you choose.

These third parties and platform providers operate under their own terms and privacy policies.

5. Local storage and retention

Viest does not maintain a central Viest account containing a server copy of your messages.

SMS and MMS history is generally stored in Android’s system messaging database. Those messages may remain on the device until they are deleted through messaging controls or otherwise removed by Android or the user.

Viest-owned application data is generally retained locally for as long as it is needed to provide the applicable feature, until the associated data is deleted, until application data is cleared, or until Viest is uninstalled, subject to Android’s behavior.

Uninstalling Viest does not necessarily delete SMS or MMS messages that remain in Android’s system messaging database.

Uninstalling Viest also does not necessarily delete backup files that you deliberately placed in an external or user-selected storage location.

Encrypted backups remain at the storage destination until they are deleted, replaced, removed through Backup & Recovery behavior, or removed by you or the applicable storage provider.

Third-party storage providers, mobile carriers, websites, Google services, and other platform providers may have their own retention practices for information they independently process.

6. Deleting information

You can use Viest and Android messaging controls to delete supported messages and other data where deletion controls are provided.

Translations, transcripts, drafts, organizational information, and related Viest-owned data may be removed through applicable Viest features or by removing the associated content where supported.

You may clear Viest’s application data through Android system settings or uninstall Viest to remove Viest’s app-private local storage, subject to Android’s behavior.

External backup files must be deleted from the storage location where they were saved if you want those copies removed. If the destination is managed by a cloud or storage provider, deletion and final retention are also subject to that provider’s systems and policies.

Because Viest does not maintain a central messaging account or server copy of your conversations, Viest generally cannot remotely retrieve or erase data that exists only on your device or in a storage account controlled by you.

7. Permissions and your choices

Android allows you to control permissions granted to Viest.

Depending on the features you use, Viest may request permissions relating to SMS/MMS, contacts, telephone state, notifications, microphone access, and other functions required for messaging.

You can revoke optional permissions in Android settings. Some Viest features may stop working or have reduced functionality when a permission required for that feature is not available.

Translation, transcription, voice recording, incoming-message link previews, Backup & Recovery, and similar optional features are used through their associated Viest controls.

8. Security

Viest is designed to keep Viest-owned product state primarily on the device and to minimize unnecessary external data transfer.

Viest Backup & Recovery uses encrypted backup artifacts.

However, no device, storage medium, network, carrier system, or software application can guarantee absolute security.

Ordinary SMS and MMS use carrier messaging infrastructure and should not be treated as end-to-end encrypted merely because they are viewed or managed through Viest.

9. No Viest account required

Viest does not currently require users to register a Viest account or sign in to a Viest-operated cloud service in order to use its core messaging features.

If this architecture materially changes in a future version, this Privacy Policy will be updated before or with that change.

10. Your privacy rights

Depending on where you live, privacy laws may provide rights relating to personal data, including rights to access, correct, delete, restrict, or obtain information about certain processing.

Much of the information processed by Viest exists only on your device or in storage controlled by you. You can directly exercise many of these choices through Viest, Android, your carrier, or your selected storage provider.

For questions about Viest’s handling of information or to make an applicable privacy request concerning information held by the publisher, contact us using the privacy/support contact listed above.

11. Changes to this Privacy Policy

This Privacy Policy may be updated as Viest changes, as platform requirements change, or as applicable privacy requirements change.

The current version will be published at:

https://orinfrance.com/viest-privacy/

The effective or updated date at the top of this policy will identify the current version.

For material changes, users may also be notified through an in-app notice, Galaxy Store release information, the Viest website, or another prominent notice associated with the product.

If the Privacy Policy URL changes, the Galaxy Store listing will be updated accordingly.

12. Contact

For privacy questions, data-related requests, or questions about this Privacy Policy:

Viest — Private Messaging

Website: https://orinfrance.com/viest/

Privacy contact: viest@orinfrance.com