Noticia

Signal blog post details its calls, data and storage design

A Signal blog post describes the app’s stated data-collection policy, RingRTC calling library, adaptive video quality and Android storage controls.

Imagen editorial de demostración con smartphones en una mesa de pruebas de radio
Las imágenes de demostración se identifican y nunca sustituyen las pruebas del producto.

A post on Signal’s official blog describes several design choices across data handling, calling and storage. It identifies Signal’s stated approach to usage data, names the library used for voice and video calls, and outlines a storage-management function available on Android.

On data, Signal says it does not collect “user analytics” or other finely detailed data about how the application is used. That is a specific statement about usage information, rather than a broad description without detail. The post places this claim alongside technical explanations of how Signal handles calls and files.

For voice and video calls, Signal says it developed RingRTC, a custom open-source library. Signal configures RingRTC so calls work better when network coverage is irregular or available data is limited. The company also says its video calls dynamically adapt video quality to the conditions of the connection. Together, these details describe how Signal’s calling system is designed to respond to changing network conditions.

Audio transmission follows a separate rule. During voice and video calls, Signal transmits audio using constant-bitrate encoding, or CBR, instead of variable-bitrate encoding, or VBR. The post identifies this encoding choice as part of the way audio is transmitted during calls, alongside the use of RingRTC and dynamic video-quality adjustment.

The post also documents a storage-management function on Android. It lets users view files received across all conversations in one place, with those files sorted by size and by type. The description therefore identifies both the scope of the view—all conversations—and the two ways its contents can be organized: file size and file type.

These points provide a concise, verifiable account of Signal’s documented design choices: its position on finely detailed usage analytics, its custom open-source call library, network-aware video quality, constant-bitrate audio and an Android file-management view. The claims are presented as Signal’s own descriptions of its service, based on the company’s official blog.

Official sources

Official source: signal.org

Related reading

Guides

Reviews

Fuentes y pruebas

Official source: signal.org (se abre en una pestaña nueva)