Data requests

1. What to know about data in SKYTAL

This page describes what data SKYTAL processes and how to contact the operator: obtain information, correct data, restrict processing, or delete data under the operator's control.

Operator: Obedinennaia Kazanskaia Biznes Gruppa LLC (ООО «Объединенная Казанская Бизнес Группа»). Contact: info@skytal.ru.

SKYTAL minimizes server-side data. Message text is not received by the server in plaintext. For service operation, encrypted packets and necessary technical metadata are processed — they are not the content of your correspondence.

2. Communication content

Messages are protected with end-to-end encryption (E2EE). The server relays encrypted packets and does not decrypt message text.

SKYTAL does not store a persistent server-side chat history. For delivery, encrypted messages are temporarily placed in a server queue. In the current service configuration, this queue is limited to 24 hours; after delivery acknowledgment — 1 hour. These values are configuration defaults and may change without updating this page.

Files are transferred through the media layer in encrypted form. The server does not receive the key required to read content. Encrypted objects have a limited server storage period; in the current configuration — up to 7 days after upload unless settings specify otherwise.

Private encryption keys are created and stored on your device. Public cryptographic material (Signal identity key, prekeys) may be stored on the server to establish an encrypted channel — this is not your private keys.

WebRTC calls use a direct path when possible; TURN relay may be used when necessary. The server processes signaling and related technical metadata but does not decrypt the media stream.

3. Service technical data

This data is not the open content of your correspondence. It is required for routing, delivery, push notifications, security, and service stability.

• Account, profile, and device identifiers (internal user_id, device_id, display name, platform, activation status, last_seen)
• Device public cryptographic keys for the Signal protocol
• Delivery metadata: chat_id, group_id, client_message_id, envelope_type, content_type, creation time, ack status
• Push notification tokens (FCM) linked to device_id — to wake the client without message text
• Invitation data: code, status, expiry, use count (technical activation mechanism)
• Call metadata: participants (device_id), media type, session state, signaling events
• HTTP/API technical logs: IP address, user-agent, request path, response code (without message content)

4. Data on your device

Message history read on the device, private keys, local media cache, and application settings are stored on your device.

A new device does not retrieve from the server message history addressed to another device_id. Only pending messages not yet acknowledged for that device_id are available.

Deleting your account on the server does not automatically erase local data. We recommend uninstalling the app and clearing application data in Android settings.

5. What you can request

• Information about how your data is processed
• Correction of inaccurate profile or contact data
• Restriction of processing — where applicable law allows
• Deletion of your account and operator-controlled data — where applicable
• Withdrawal of consent — where processing is based on consent

6. Profile and related data deletion

If you request deletion, the operator treats this as a request to delete your SKYTAL account and data processed by the operator.

The operator will take reasonable steps to delete or anonymize profile, device records, push tokens, pending relay queue entries, attachment metadata, and related technical data in active systems.

Complete removal from all backups, logs, and queues may take additional time under technical procedures.

7. Data on other participants' devices

Messages and files already delivered to another participant may remain on their device. SKYTAL does not control local storage on third-party devices and cannot remotely erase copies on other users' devices.

Deleting your profile may appear to other participants as an unavailable or deleted contact, depending on client implementation.

8. How to submit a request

As of the publication date, automatic profile deletion from the application may be limited; the primary channel is an email request.

Processing time depends on data volume and legal requirements. Technical logs may persist in rotated log files independently of profile deletion; in the current configuration, Caddy access logs rotate with retention up to 720 hours.

• Email info@skytal.ru with the subject line "SKYTAL data request"
• Include your account identifier or device_id (if known), email (if used), and the nature of your request
• The operator may request additional information to confirm control of your profile/device — not passport-based identity verification