How RecBaba Share Links Stay Private
RecBaba share tokens are long and random, pages are noindex, and you can password, expire, or revoke a link. There is no public directory of recordings.
On this page
A share is a link you send, not a listing. RecBaba does not publish a directory. robots.txt still disallows /share/* for search crawlers, and the page sends noindex. Preview crawlers (the ones that build a link card in chat) are allowed to fetch the page so the card can render.
Creating the link is the upload. Password, expiry, and revoke live on that object.
Controls that actually exist
- Unlisted by default: anyone with the URL can watch.
- Password on Pro: same private link plus a password you set (minimum eight characters).
- Optional expiry. Hosted share links are on Pro and Max.
- Download on or off.
- Revoke: immediate. The next request fails.
Tokens are 16 random bytes, about 95 bits. They are not sequential recording ids. Owner tools reconstruct the public URL from an encrypted mapping so a guessable id never becomes the token. If you pasted the link in a public Slack, rotate it — unlisted is a courtesy to search engines, not a lock.
What we log
Share-access logs use hashed identifiers, not raw IP addresses. Pro shows who opened the link. Max adds a 30-day views trend. That is analytics on the share, not a public view count on the marketing site.
Password shares stay gated until the viewer unlocks. AI and transcript JSON for that token follow the same gate — hiding insights on the link does not leak the payload. Revoke is still the hard stop if the URL escaped the thread.
AI on the page does not make the link indexable. You can hide insights per link.
Record the next take locally
4K, mic and system audio, no watermark. The file stays on this computer until you choose to share.
Start recording