It’s one of the GDPR requirements in Europe - the ToS acceptance must be an explicit act (like marking a checkbox), not an effect of a separate action (like pressing the sign up). Is it possible with the SSO?

You can add a mandatory checkbox to the sign-up form. [07%20PM] [56%20PM]

Would you be compliant with the GDRP requirements if users agreed to your forum’s ToS on the SSO Provider site? If so, it would be fairly easy to build it into your SSO provider code.

I’m also a fan of this behavior. Some sites do this by “pinned banner” type notices that must be accepted to clear. I do not have an sso provider to that wouldn’t be an option for me but I agree should work with several sso provider

That’s a decent solution! I’ll use something like “I have read and agree to the terms of service” If the whole install is login only, I will have to use an alternate hosted tos and privacy policy for the links on signup page yes?

[immagine] usulrasolas: Some sites do this by “pinned banner” type notices that must be accepted to clear. You’re too late then, you’ll already have stored information at that point. Just having an ‘I accept the TOS’ is not enough for the GDPR though. This is a good read. Some highlights: …

So they have to write some words into a text field like “I consent to blah blah” and then tick a checkbox? Also… oral statement… like at a notary public… for a website? wow.

I don’t know about that interpretation of that being exactly right. A couple sites I use with a million plus users have been recently overhauled for gdpr compliance and once uses a banner and the other it a tick box on a captive tos page before you sign up. I’m not a lawyer tho

[immagine] neil: So they have to write some words into a text field like “I consent to blah blah” and then tick a checkbox? No - it just says that the text next to the checkbox should be clear and specific. So ‘I understand and agree that this website is going to use my name and e-mail addres…

[immagine] RGJ: No - it just says that the text next to the checkbox should be clear and specific. Ok I was just showing an example of adding a checkbox to the signup form. Some standard wording will probably become common that everyone can use.

So, Is the check box next to the sign up compliant? I feel like it should be as long as the tos are clearly accessible from sign up. Especially in the case of a private users only install. But I’m trying to just cover bases and be compliant. Is it a wording issue with the sign up check box, or an i…

I read the enitire article and I understand the law conceptually but I don’t understand how it relates to (my) deployment of Discourse and how to comply.

Come fare in modo che gli utenti accettino esplicitamente i ToS

Supporto

neil (Neil Lalonde) 21 Marzo 2018, 6:37pm 4

You can add a mandatory checkbox to the sign-up form.

GDPR countdown and compliance

Discourse: Google Play user-generated content policy violation

Site_setting.tos_url doesn't work

Argomento		Risposte	Visualizzazioni
GDPR and anonymizing personal data Community Building gdpr , privacy	74	19951	Dicembre 1, 2018
Cookie compliance under GDPR Community Building gdpr	63	12598	Maggio 5, 2023
GDPR countdown and compliance Community Building gdpr	89	15617	Giugno 18, 2018
Providing data for GDPR Community Building gdpr , privacy	81	13366	Dicembre 20, 2018
Cookie Consent, GDPR, and Discourse Site Management explanation	1	3983	Ottobre 10, 2025

Come fare in modo che gli utenti accettino esplicitamente i ToS

Argomenti correlati