Help
Frequently asked questions
Answers are based on verified claims about the current SKYTAL implementation.
Security
1:1 E2EE is confirmed on the Android client. Group chats and attachments do not use E2EE yet — we do not claim otherwise.
The server stores and relays encrypted packets (ciphertext) only. It cannot decrypt message content. It may process delivery metadata such as routing, timing, and chat participation.
Private keys are generated and stored on your device. Only public keys required for exchange are sent to the server.
Access
Leaders, closed teams, lawyers, consultants, and organizations with heightened requirements for communication confidentiality.
Submit a request through the form on the Access page or email info@skytal.ru. After terms are agreed, you will receive the required invitations.
A technical mechanism for participant activation. It is not a standalone product and does not verify identity or employer.
Connection pricing is determined individually and depends on the scenario, number of participants, term, and support terms.
No. An invitation grants activation rights but does not verify identity, job title, or organizational membership.
Application
The Android build is listed on the Download page. Other platforms are on the roadmap.
P2P and architecture
No. SKYTAL is a P2P-first messenger with E2EE. Calls connect directly between devices when possible, with relay fallback. Messages are currently delivered through an encrypted server delivery layer. Direct P2P delivery for messages is the next architecture stage.
Calls use WebRTC with priority on a direct P2P connection between devices. If a direct route is unavailable, traffic uses a protected relay.
Not yet. Attachments go through the server media layer in encrypted form. Direct device-to-device file transfer is being developed separately.
Payment
A voluntary payment for infrastructure and client development. It is not a subscription and does not change messenger features.
Support
For security and access questions — info@skytal.ru