Cookie Policy
Last updated 2 November 2026
Vidiicast uses one cookie, to keep you signed in, and stores a few settings in your browser so the studio works. There are no advertising, analytics or tracking cookies, and nothing from other companies follows you around the web. Because everything here is needed for the service to work, we don’t show a cookie banner.
Cookies
| Name | What it’s for | How long |
|---|---|---|
__Secure-vidii.session_token | Keeps you signed in. It holds a random code that matches a session in our database. Pages can’t read it, and it’s only sent over secure connections. | 30 days, renewed each day you use Vidiicast. Removed when you sign out. |
__cf_bm | Set by Cloudflare, only if it needs to check whether traffic is coming from a bot. Not used for tracking. | 30 minutes |
Other things stored in your browser
| Name | What it’s for | How long |
|---|---|---|
vidii_name | The name you last used in a studio, so you don’t have to type it again. | Until you clear your browser data |
vidii_prompter_speed, vidii_prompter_size | Your teleprompter speed and text size. | Until you clear your browser data |
vidii_admit_… | Lets you back into a studio after a host has let you in, if your page reloads. | Until you close the tab |
vidii (browser database) | Holds your recording on your own device while it uploads, so nothing is lost if your connection drops. Each piece is deleted once we confirm it has arrived. | Until the upload finishes |
Turning them off
You can block or delete cookies and site data in your browser settings. If you block the sign-in cookie you won’t be able to sign in, and if you clear site data during a recording, any part that hasn’t uploaded yet will be lost.
Changes
If we ever add cookies that aren’t needed to run Vidiicast, such as analytics, we’ll update this page and ask for your permission first.
Questions: hello@vidiicast.com. More about how we handle data is in the Privacy Policy.