What we store, and who sees it

• Your account. Email address and name from the Google account you sign in with, plus your GitHub username once you connect it.
• Repository context, not your source code.We read a repository's README, its language statistics, and the list of file paths. We do not read the contents of your source files. For private repositories this runs through a GitHub App you install on the specific repos you pick, requesting only metadata and contents read access.
• The clips you record. Video you film in the browser, stored so the renderer can cut it. Your voice is transcribed to place captions and time the edit.
• Screenshots and logos you upload. Kept with the brief they belong to, and read once by a vision model so the editor knows what each one shows.
• The finished video, plus the brief and the per-scene review notes behind it.

We are one person and a handful of services. Nothing is sold, and nothing is shared with anyone beyond the companies that run the product:

• OpenAI: writes the brief and the scenes, transcribes your voice, and reviews rendered frames. Your clips, transcript and uploaded images pass through it.
• Supabase: the database and file storage.
• Railway: runs the rendering service.
• Vercel: hosts the website.
• Google and GitHub: sign-in and repository access.

Uploaded images sit at public URLs. Screenshots you attach are stored at long, random, unguessable addresses, but anyone holding one of those links can open the file without signing in. Deleting an image from a brief deletes the file itself, so the link stops working. Do not upload a screenshot containing something you would not want seen if the link leaked.

Your finished video is not private by default. It is stored the same way, so treat its link as shareable. That is the point of the product, but it should not be a surprise.

You can delete a video from the studio, and removing an image from a brief removes the stored file too. For everything else, email abhishek.vulla@gmail.com and ask for your account and its data to be deleted. There is no form and no waiting period. It is a person reading the message.

You can also disconnect the GitHub App at any time from your GitHub settings, which cuts off repository access immediately.

Recordings, uploads and finished videos stay until you delete them or ask for the account to be removed. Recordings attached to a finished brief may be cleared automatically when you re-render it, to keep storage from growing without bound.

Proof is built and run by Abhishek Vulla, a student at the Singapore University of Technology and Design. It is early software with a small number of users. If something here matters to you and is not covered, ask and you will get a straight answer.