VLSTUDIO ← Back to site
// Legal

Terms Versioning
Policy

Last updated: July 1, 2026  ·  Effective: July 1, 2026
// This policy explains how we announce changes to any VLStudio legal document. Today, acceptance is captured by continued use rather than a fresh click, because the signup checkboxes are not yet clickable links to the documents they name, and this page says so plainly.

Contents

1. What This Policy Covers

2. How Material Changes Are Announced

3. How Acceptance Works Today

4. The Signup Checkbox Gap

5. Where We Are Going: Logged, Versioned Acceptance

6. Changes to This Policy

7. Contact

1. What This Policy Covers

This policy explains how VLStudio announces changes to any of its legal documents (Terms of Service, Privacy Policy, and the other policies linked from our legal documents index), and how your acceptance of those documents, and of updates to them, is captured today. It is referenced from our Terms of Service, Section 16 and our Privacy Policy, Section 18, both of which point here rather than restating this mechanism themselves.

2. How Material Changes Are Announced

When we make a material change to any VLStudio legal document, we do the following:

A non-material change (a clarification, a typo fix, a formatting update) may be made without the notice period above, but we still update the "Last updated" date so the change is visible.

3. How Acceptance Works Today

Today, your acceptance of a VLStudio legal document, and of a material update to one, is captured by continued use of the Service after the effective date of that document or update. If you keep using VLStudio after a change takes effect, that continued use is treated as your acceptance of the updated terms.

We say plainly that this is a weaker form of consent than a fresh, affirmative click on the specific updated document. It relies on your continued use as a proxy for agreement, rather than recording a discrete, timestamped action tied to the exact version you accepted. Where a change is significant enough that we judge continued-use consent to be insufficient, we will require a fresh acceptance action before you can keep using the affected feature; today, that judgment is made case by case rather than through a systematic versioned-consent mechanism.

4. The Signup Checkbox Gap

The signup flow displays text referring to our Terms of Service and Privacy Policy, but today that text is non-clickable: it is not a real hyperlink to the documents it names, and no timestamped, versioned acceptance event is recorded when you complete signup. This means we cannot currently produce an audit trail showing that a specific user clicked through to, and affirmatively accepted, a specific version of the Terms or Privacy Policy at signup. This is a product gap, not a design choice, and we are flagging it here rather than describing signup as capturing a real, provable acceptance event.

Until this is fixed, the acceptance basis for a new signup is the same continued-use standard described in Section 3: using the Service after creating your account is treated as your acceptance of the Terms of Service and Privacy Policy in effect at that time, even though the signup screen itself does not yet capture a clickable, provable version of that acceptance.

5. Where We Are Going: Logged, Versioned Acceptance

We intend to close the gap in Section 4 by replacing the non-clickable signup text with real links to the current version of each document, and by recording a versioned, timestamped acceptance event, tying a specific user, to a specific document version, at a specific time, for both the initial signup and any future material update that requires a fresh acceptance. Once that ships, this section will describe the working mechanism and the audit trail it produces, rather than a stated intent.

6. Changes to This Policy

We will update this policy once the versioned acceptance mechanism described in Section 5 ships. Until then, changes to this policy itself follow the same continued-use acceptance standard described in Section 3.

7. Contact