Privacy information

What Veilcord handles

Last updated: 30 August 2026. Contact: [email protected].

Messages, calls and files

Message content, call media and files are encrypted on user devices. Veilcord's rendezvous service does not store application content. The hosted application relay can forward encrypted message frames in memory when a direct path is unavailable; it cannot decrypt their contents and does not retain message history. Hosted relay for calls and files is not currently offered.

Connection data

Direct peer-to-peer connections expose the network addresses needed to connect to the other participant. The rendezvous service, relay operator and Cloudflare may process transport metadata such as IP address, time, connection state and traffic volume as part of delivering and protecting the service. This metadata is not message content.

Accounts and local data

Veilcord does not require a central account for the free communicator. Profiles, keys, contacts and vault data are stored on the user's device. Optional device unlock uses Android Keystore or Windows user protection and never provides account recovery.

Permissions

The Android app requests network access and, only when used, camera and microphone access for calls. Biometric permission is used only for optional device unlock. Veilcord does not request contacts, location, advertising ID, storage-library or background-location permission.

Analytics, advertising and payments

The public site and communicator include no analytics, advertising or third-party browser scripts. Paid relay features and payment processing are not enabled in the current release.

Deletion and control

Users can remove local Veilcord profiles and vault data from their device. Because the free service has no central user account or retained message history, there is no corresponding server-side message archive to delete. Infrastructure security or abuse records, if introduced in a future release, will require this notice to be updated before that release.

Open-source notice

Veilcord components are distributed under the GNU Affero General Public License version 3 or later. Download the corresponding source and use the release manifest to verify its SHA-256 hash.