GDPR, Cookie Consent and Terms Acceptance in Osclass
A practical way to separate cookie consent, user privacy and terms acceptance in an Osclass marketplace.
Separate consent from contractual acceptance
Cookie consent and terms acceptance are different interactions. Cookie controls determine whether optional browser-side storage or scripts may run. Terms acceptance records that a user agreed to rules associated with a form or action. Combining them into one checkbox creates unclear behavior and makes later changes harder to manage.
- Keep necessary site functions separate from optional categories.
- Load analytics or marketing scripts only after the matching consent where required.
- Record terms acceptance only on the forms where that agreement is relevant.
Give visitors a real preference control
A cookie banner should not be only decorative. Visitors need a way to make a choice and later revisit it. The site should consistently apply the saved preference when scripts are loaded on subsequent pages.
- Use clear category names.
- Keep the choice interface understandable on mobile.
- Provide a persistent way to reopen preferences.
Use terms acceptance where an action needs it
A marketplace may require acceptance during registration, listing publication or another defined workflow. The wording should match the action being performed, and the checkbox should not be pre-selected. If the terms change materially, the site may need a fresh acceptance according to its own legal process.
TTB components for the separate jobs
TTB GDPR & Cookies manages consent categories and consent-aware script loading. TTB Terms handles configurable acceptance on selected Osclass forms. Using separate components keeps the technical behavior easier to audit and maintain.