What you're trusting us with, in plain terms.
You hand this platform Telegram sessions and conversations. Here is who we are, how that data is handled, and what we commit to — with links to the full policies.
Who is behind this
TelegramOS is built and operated by the Orv Team. Before you sign up, you can reach a real person on Telegram for presales or diligence questions; after signup, the in-app support desk is staffed by the same team that runs the platform.
Security overview
Sessions are stored encrypted, workspace access is protected by two-factor authentication, team access is role-based, and actions are recorded in audit logs. The security page documents the model in full, and the responsible-disclosure route is public.
Data flow and retention
The privacy policy describes what is stored for accounts, inbox messages, bots, and analytics — and how deletion works. A data-processing agreement is available for teams that need one.
Reliability
We operate to a 99.5% monthly uptime target, documented in our policies. Every shipped change is public on the changelog — that history is the most honest picture of how actively the platform is maintained.
Acceptable use
The platform supports operating your own communities, outreach with pacing and opt-out respect, and client work under clear roles. Spam, harassment, and deceptive use are prohibited and enforced — the abuse policy spells out the line, and account-health limits back it up in the product.
Product maturity
TelegramOS is a young product under active development. We would rather show you the changelog and the docs than claim scale we don't have: no invented customer counts, no fabricated testimonials. What the marketing pages describe is what the product does today.