Privacy
Pages like Home, How it works, and this Privacy page are open to read without signing in. The studio—dashboard, projects, uploads, and exports—is password-protected. You unlock it with your Google account; there is no separate ClipoStack password. Google handles that sign-in step under Google's privacy policy. What happens to your actual video files—where they are stored, how long they are kept, and who on the operations team can reach them—still depends on the video-processing service this app is connected to for you. This page is orientation, not a substitute for your host's rules or your workplace policies.
What this website keeps on your device
After you sign in, the site uses normal session cookies so you stay signed in until you sign out. The browser may also store small preferences—such as which project you last opened or plan-related choices—using everyday browser storage.
When the studio talks to the video service, it sends a stable id so usage and billing can line up with the right person: after you unlock the studio, that id is tied to your Google account identifier; while you are only browsing public pages, a random id may be created and kept locally until you sign in or clear site data.
What usually happens on the server
When you upload a clip, the connected service typically stores the file, any text generated from speech, edit plans, optional stock footage you added, and the finished export. Backups, retention, and who may administer that system are controlled by whoever runs it—not by this help text alone.
For sensitive footage, use a connection you trust (in production, that usually means HTTPS) and follow your organization's rules for confidential video.
Outside services
Speech-to-text, smart suggestions, stock search, billing, and similar features may call other companies' systems. Each has its own privacy terms. Access keys for those services belong in the secure configuration of the backend—not in public pages or casual messages.
This is a plain summary to help you ask the right questions of whoever hosts your deployment. For regulated or high-risk data, involve counsel or your security team, not just product docs.