A cloud recorder removes the need to keep a phone or desktop capture running, but it also creates a few responsibilities. You need to verify the public source, protect the Telegram account receiving the result and understand which data belongs to SOOP, Telegram and SoopRec.
This checklist is written for SoopRec's public-live workflow. It is not a substitute for SOOP's current rules or for legal advice in your jurisdiction.
1. Never submit a SOOP Live password
SoopRec needs a public creator ID or an official SOOP Live share link. It does not need your SOOP account password, session cookie, one-time code or recovery key.
If a page or message claiming to be SoopRec asks for those credentials, stop. Use the verified @sooprec_bot username and the official soopliverec.com domain instead of a copied lookalike link.
2. Confirm that the source is public
A creator profile can exist even when no public live is playing. Before a one-time recording, open the official SOOP Live page and confirm that the stream is publicly viewable without bypassing a login, password, age gate or room restriction.
SoopRec validates the source again on the server. If the public player disappears or the live becomes unavailable, the recorder should stop or report that no usable public stream was found rather than attempting to circumvent the restriction.
3. Use the stable creator ID
Display names are poor security boundaries. They can change, contain unusual characters or resemble another creator's name. A stable creator ID reduces the risk of watching or recording the wrong channel.
When you add a watchlist entry, open the official profile or share link first. Check the profile image and channel details, then save the stable ID. Review the bot's confirmation before leaving automatic monitoring enabled.
4. Protect the Telegram delivery account
The completed recording is delivered to the Telegram chat that requested it or qualified through the watchlist. Protect that account with Telegram's two-step verification, keep active sessions under review and avoid forwarding sensitive media into a public group by mistake.
The SoopRec bot never needs your Telegram login code. Telegram authentication is handled by Telegram itself; bot commands run inside your existing chat.
5. Understand archive-first delivery
SoopRec's media pipeline publishes the completed video or ordered parts, player cover and contact sheet as one album in a private product archive. The main bot then copies the archived album to current eligible recipients.
This design avoids repeatedly uploading the same large file for every recipient and keeps delivery idempotent during retries. It also means the archive must remain private and accessible only to the configured SoopRec bot and globally leased Saga sender helpers.
The public website does not expose delivery credentials or turn a private recording into a public object. A recording page can hand the request to the authenticated Telegram flow, where the bot verifies the requesting chat before delivery.
6. Review retention and deletion expectations
Temporary capture media and completed delivery files have different lifetimes. Working media is retained only long enough to verify and prepare the recording; successful temporary evidence is removed after durable handoff. Recoverable failures can be kept briefly for retry, while storage lifecycle rules provide a final expiry.
Telegram copies follow Telegram's own message and account behavior. Removing an item from your chat does not automatically change a creator's SOOP replay or every other recipient's independently delivered copy.
7. Respect creator rights and platform rules
Publicly viewable does not mean free of copyright, personality or contractual rights. Use a recording only where you have permission or another valid basis. Do not use SoopRec to harass creators, republish paid material or evade access controls.
SOOP publishes an official privacy policy, service terms and operations policy. Read the current official versions because platform policies can change after this guide is published.
8. Recognize safe error behavior
A trustworthy recorder fails closed. Examples include rejecting an unsupported hostname, refusing a malformed creator ID, stopping when a refreshed media source is not valid and not creating an empty recording for an offline creator.
Temporary errors should not silently add duplicate watchlist entries or create multiple recordings for the same live. Delivery retries should reuse stored delivery identifiers so a network timeout does not create duplicate albums.
Pre-recording checklist
- I am using
soopliverec.comor@sooprec_bot. - I supplied a stable public creator ID or official SOOP Live share link.
- I did not provide a SOOP or Telegram password, session or login code.
- I confirmed that the source is public and that I may record it.
- I checked the bot confirmation for the correct creator.
- My Telegram account and destination chat are private enough for the media.
- I understand that availability and maximum quality depend on the source SOOP publishes.
Frequently asked questions
Does SoopRec log in to my SOOP account?
No. The supported workflow resolves public creator and live information without collecting your SOOP password.
Can SoopRec unlock a private room?
No. It is designed to reject sources that are not publicly playable.
Is every public stream automatically lawful to redistribute?
No. Public access and redistribution rights are different questions. Follow the creator's permissions, applicable law and SOOP's current rules.