At Save Restricted Telegram Video, we believe privacy is a fundamental human right. Our architecture is engineered around a core tenet: we do not store your media files, we do not log your private chats, and we never monetize your personal identity.
Effective & Last Updated:
Summary at a Glance
βZero Media Storage: Videos stream directly via ephemeral memory pipes; no files are kept on disk.
βZero Password Retention: We never see or store your Telegram passwords or 2FA credentials.
β2-Hour Stream Life: Direct HTTP streaming links auto-expire in 120 minutes.
βNo Ad Trackers: We do not run invasive ad networks, cross-site trackers, or behavioral profiling.
1. Introduction & Scope
This Privacy Policy governs the operation of the Save Restricted Telegram Video web platform (saverestrictedtelegramvideo.com), its companion bot (@SaveRestrictedContentReBot), and related streaming APIs (collectively, the "Service").
By accessing or interacting with the Service, you acknowledge that you have read, understood, and consented to the data handling practices outlined in this policy. If you do not agree with any aspect, please discontinue using our web downloader and companion bot immediately.
2. Data We Process (And Why)
We adhere strictly to the principle of Data Minimization under GDPR Article 5(1)(c). We process only technical telemetry and transient identifiers required to execute your requested media stream:
A. Telegram Message Links & Content Hashes
When you submit a link (e.g. https://t.me/c/1234567890/100), our MTProto gateway parses the channel ID and message ID. A one-way cryptographic SHA-256 hash is computed to check whether an active direct download stream is already alive, minimizing redundant Telegram upstream requests and preventing API FloodWait errors.
B. Transient Media Chunks (Streaming Pipeline)
Media packets fetched through the MTProto protocol are passed directly into an in-memory streaming buffer and piped directly over TLS 1.3 to your browser or download manager (IDM, Aria2, etc.). At no point is the complete video or audio file written to permanent secondary disk storage.
C. Temporary Batch States
For multi-message ranges (e.g. messages 10 to 50), our internal task manager temporarily stores message IDs, success counters, and failure flags in high-speed volatile storage. This allows interrupted batches to safely resume if a temporary network fluctuation occurs. These records automatically purge within 24 hours of task completion.
D. Operational Security & Rate-Limiting Telemetry
To safeguard the platform against distributed denial-of-service (DDoS) attacks, automated bot scraping, and credential stuffing, we record anonymized IP addresses, request timestamps, and bandwidth quotas. IP addresses are hashed after 7 days and retained solely for anti-abuse audits.
3. Information We Never Collect or Retain
To guarantee the absolute privacy of your Telegram account, we have deliberately engineered our systems to avoid collecting the following sensitive assets:
No Passwords or 2FA Keys: We never ask for, intercept, or record your Telegram two-factor authentication password.
No Private Chat Logs or Contacts: We do not parse or read message histories, contact lists, or non-requested messages from any chats.
No Financial Payment Card Numbers: All subscription transactions for our Premium tiers are processed by PCI-DSS Level 1 compliant payment gateways. We never store or handle raw credit card numbers.
No Third-Party Advertising Data: We do not sell, rent, or trade your personal data with third-party advertising brokers or data aggregators.
4. Cookies, Session Storage & Local Preferences
Our web application uses minimalist client-side storage mechanisms strictly necessary for platform functionality:
Key / Cookie
Type
Purpose
Duration
theme
localStorage
Remembers your dark or light display mode preference.
Persistent
srv_session_auth
Secure Cookie (HTTP-only)
Authenticates your web dashboard session securely via JWT.
7 Days
lang_pref
localStorage
Remembers your chosen language for interface strings.
Persistent
You can clear cookies and local storage items at any time through your browser settings without impacting your ability to use the free companion bot.
5. Direct Link Lifecycles & Expiration Policy
Any direct HTTP streaming URL generated by our server (compatible with download accelerators like IDM, Aria2, and curl) contains an ephemeral cryptographically signed token.
120-Minute (2-Hour) Expiration Window
Streaming tokens automatically expire after exactly 2 hours from the moment of generation. Once expired, the temporary buffer is instantly deallocated and the connection is closed. If a download was interrupted, you can simply request a fresh streaming link.
6. International User Rights (GDPR & CCPA / CPRA)
Regardless of where you reside, we honor full data subject rights in compliance with the General Data Protection Regulation (EU GDPR) and the California Consumer Privacy Act (CCPA):
Right to Access: You can request a summary of telemetry or subscription records tied to your account.
Right to Rectification: You can update your contact email or billing preferences at any time.
Right to Erasure ("Right to be Forgotten"): You may request the immediate deletion of all session credentials, cache records, and billing identifiers by emailing our Data Protection team.
Right to Restriction of Processing: You may object to automated rate-limiting evaluations or temporary link caching.
Right to Data Portability: You can export your active batch download histories in JSON format from the dashboard.
7. Security Architecture & Data Safeguards
We implement comprehensive technical and organizational measures to protect your session tokens from unauthorized access, loss, or alteration:
TLS 1.3 Encryption: All browser-to-server and bot-to-MTProto communications are transmitted over modern, high-grade TLS 1.3 channels.
AES-256 Encrypted Session Storage: Web session tokens are encrypted at rest with hardware-accelerated AES-256-GCM algorithms.
Automated Heartbeat Audits: Continuous automated security scanners check our code repositories for credential leaks and dependency vulnerabilities.
8. Childrenβs Privacy Protection
The Service is strictly designed for and directed to individuals who have reached the age of majority in their jurisdiction (or at least 18 years of age). We do not knowingly collect or solicit any data from children under 16. If we become aware that personal information from an underage person has been received, we will delete that data immediately.
9. Changes to this Policy
We may periodically update this Privacy Policy to reflect enhancements in our streaming infrastructure or revisions in international legal requirements. Any material changes will be announced via our official Telegram announcement channel (@A4_Bots) and highlighted on this page with an updated timestamp.
10. Contacting Our Data Privacy Team
If you have questions regarding this Privacy Policy, wish to exercise your GDPR/CCPA rights, or have feedback on our data processing practices, please reach out to us: