Cookie Policy
Last Updated: October 28, 2026
This Cookie Policy explains how VAIF STUDIO LLC ("VAIF Studio," "we," "us," or "our") uses cookies on our website and platform. We are committed to transparency about the technologies we use.
What Are Cookies
Cookies are small text files stored on your device (computer, tablet, or mobile) when you visit a website. They are widely used to make websites function properly, provide security features, and remember user preferences. Cookies can be "session" cookies (deleted when you close your browser) or "persistent" cookies (remain on your device until they expire or you delete them).
How We Use Cookies
VAIF Studio uses essential cookies only. These are strictly necessary for the Service to function and cannot be disabled without breaking core functionality:
- Session cookie (
__Host-vaif_session): keeps you signed in to the console without re-entering your credentials. It holds a random session code, not your password, and only our servers can read it: your browser sends it only over a secure connection and never lets a web page's scripts see it. Cross-site request forgery is prevented with a token the console keeps in the page's memory and sends as a request header, not as a cookie. - Known-device cookie (
__Host-vaif_known_device): set when you sign in to the console, reset your password or confirm your email address from this browser, so that if someone else keeps entering wrong passwords for your account, this browser can still sign you in with the right one. It holds a code our servers sign that names your account; it does not contain your password, and changing your password makes every such code stop working. Like the session cookie it travels only over a secure connection and no web page's scripts can read it. It expires 90 days after it was last set. - Sign-up device cookie (
__Host-vaif_signup_device): set the first time this browser asks to create an account, so that one browser cannot open account after account: at most five sign-ups a day are accepted from it. It holds a random code our servers sign; it does not name you or your account, and nothing else reads it. Like the session cookie it travels only over a secure connection and no web page's scripts can read it. It expires 365 days after it was set. - Sign-in check (
vaif_oauth_…): set only while you sign in with Google, GitHub or Microsoft, or connect one of those accounts to your VAIF account, so that the step can finish only in the browser that started it. It expires after 10 minutes. - Older sign-in cookie (
refresh_token): a browser that signed in before we introduced the session cookie may still hold this one. The console swaps it for the session cookie on your next visit, and new sign-ins no longer set it. - Device identifier (local storage,
vaif_device_id, console only): a random code, not derived from anything about you or your device, that our console stores in your browser's local storage only when it is needed for referral fraud checks: when you create an organization with a creator's referral code, or when you sign in as a creator in our referral program. It is sent to us only at those moments. Because it is unique to your browser, we treat it as personal data. We use it only to spot referral fraud, such as a creator referring themselves from their own browser; we never use it for analytics or advertising, and we never share it with the creator. Clearing your browser's site data for the console removes it, and we delete our copy on the schedule in section 7 of our Privacy Policy. - Your work and your settings (local storage, console only): the console also keeps things in your browser's local storage so they survive a reload: copies of your own work (generated project files, your SQL and terminal history, your notifications); the plan, billing period and promotional code in the link that brought you to sign up, which stay until sign-up hands them to checkout or you clear the console's site data, and a creator's referral code from such a link, until it is used or expires; and your choices and layout (whether your data may be used for training, the cookie notice, editor settings, and sidebar and panel state). None of it is a tracking identifier, none of it is used for analytics or advertising, and it stays in your browser. Signing out does not remove the copies of your work; clearing your browser's site data for the console removes all of it, which matters on a shared computer.
No Analytics or Advertising Cookies
We do not use analytics, advertising, or behavioral tracking cookies. We do not track you across other websites, build advertising profiles, or share cookie data with ad networks. Your browsing activity on VAIF Studio is not monetized or sold.
Third-Party Cookies
VAIF Studio does not currently set any third-party cookies. Our payment processor may set cookies on its own domain during checkout, but these are not set on the VAIF Studio domain.
Managing Cookies
You can control cookies through your browser settings. Most browsers allow you to block or delete cookies. However, please note that disabling essential cookies will prevent you from logging in to the VAIF Studio platform, as the session authentication cookie is required for account access.
Instructions for managing cookies in popular browsers:
- Chrome: Settings > Privacy and security > Cookies and other site data
- Firefox: Settings > Privacy & Security > Cookies and Site Data
- Safari: Preferences > Privacy > Manage Website Data
- Edge: Settings > Cookies and site permissions > Cookies and site data
Cookie Consent
Because the cookies we set are strictly necessary for the Service to function — your session and, while you sign in with or connect a Google, GitHub or Microsoft account, the sign-in check — explicit consent is not required under GDPR (Article 5(3) of the ePrivacy Directive). Article 5(3) governs storing information on your device generally, not only cookies: vaif.studio also writes a promotional code to your browser's local storage if you arrive with one in the URL, so that it survives to checkout. That is storage you initiated by following the link, and it is not used for advertising or to follow you across other websites. We do not use tracking, advertising, or third-party marketing cookies. The console's device identifier (section 2) is stored without a consent banner for the same reason: it serves only to protect the Service and our referral program against fraud, a security purpose, and it is used for nothing else. If we ever introduce non-essential cookies in the future, we will add an explicit consent banner to this site before they're set.
Contact
If you have questions about our use of cookies, contact us at:
VAIF STUDIO LLC
Detroit, Michigan, United States
Email: legal@vaif.studio