SceneRiot
Privacy Policy
Last updated 29 October 2026
SceneRiot (www.sceneriot.com, "we") is a site of short animated comedy sketches, written with AI and performed in your browser, some of which we also publish as videos on YouTube. This policy says what information the site handles, why, and what you can do about it.
Watching, liking and commenting
You do not need an account to watch. To count each view, like and share once per viewer, and to let you delete your own comments, your browser makes up a random viewer ID and keeps it in its local storage. We store only a keyed hash of that ID, never the ID itself, and it is not linked to your name, email or device.
If you comment, we store the name and text you enter, which are shown publicly with the scene. Comments are kept until you or we delete them.
Your browser also keeps a few settings for you (sound on or off, how the feed plays, and an access code if you enter one). They stay on your device; the access code is sent to us only with the requests that need it.
Analytics
We use Vercel Web Analytics to count page views and a few moments, such as a scene being watched to the end or shared, together with the scene's title and genre. It uses no cookies and does not identify you, and nothing you type (a comment, a premise) is sent to it.
Making scenes
People with a creator access code can make scenes. The premise they type is sent to Anthropic (Claude) to write the script, and the lines are voiced by a text-to-speech provider (Inworld, ElevenLabs or Google). Finished scenes are stored with us and may be shown publicly on the site and published on our channels. Please do not put personal information in a premise.
YouTube and Google data
The site has a private Studio, used only by its owner, which can connect a YouTube channel through Google sign-in in order to upload SceneRiot's own videos to it. SceneRiot uses YouTube API Services. When the channel is connected, we ask Google for two permissions:
youtube.upload, to upload the videos the owner chooses, with the title, description and settings the owner enters;youtube.readonly, to read the connected channel's name, handle and picture, so the Studio can show which channel it posts to.
We store the channel's ID, name, handle and picture address, and Google's access token, which is encrypted and kept in private storage. It is used only to upload videos the owner asks us to upload. We do not read, store or use any other YouTube or Google data, we do not sell it or use it for advertising, and we do not share it with anyone. SceneRiot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Access can be removed at any time with Disconnect in the Studio, which deletes the stored token and revokes it with Google, or from your Google account's third-party access page. By using these features you also agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.
Who processes data for us
We use these services to run the site, and share with them only what each needs: Vercel (hosting, storage and analytics; it processes IP addresses and request logs to serve the site and keep it secure), Anthropic (writing scripts), Inworld, ElevenLabs and Google (voices), and Google/YouTube (uploads, when connected). We do not sell personal information.
How long we keep it
Viewer marks and comments are kept while the scene is on the site. A YouTube connection is kept until it is disconnected. Server logs are kept by Vercel for a limited time under its own policies.
Children
SceneRiot is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has left a comment, tell us and we will remove it.
Your choices and requests
You can delete your own comments from the site, and clear your browser's storage to reset your viewer ID and settings. To ask what we hold about you, or for anything to be corrected or deleted, email faustofonseca@gmail.com.
Changes
If this policy changes, we will post the new version here with a new date.