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]

[imagen] tophee: People are only confirming that they have read those documents. There is not hint that they are consenting to something by ticking that check-box, let alone that this “something” regards personal data… You’re correct, thanks. I’m not sure what’s the perfect wording to not ann…

[imagen] dnsmichi: If you scroll down on https://monitoring-portal.org , you’ll recognise the footer. I’ve added this as German law requires your to have an URL to your legal notice (“impressum” in German) on every single page. This lists personal details such as name and address where the owner…

[imagen] Mittineague: Not needed, the onus is on the member Terms of Service - Discourse Meta CDCK reserves the right, at its sole discretion, to modify or replace any part of this Agreement. It is your responsibility to check this Agreement periodically for changes. This definitely will no…

Usually when fees go up I have been required to click to accept fee increases like with Netflix for example. I got email notices before that. Click to accept changes in tos at sign in would be smart. Along with notices to members prior to that.

I’m thinking another case with SSO. User A logged in Discourse, some day user A revokes consent from, say passport (if we have a passport site, i.e. passport.example.org ), how would we handle it? I can think of a way to handle this, to add a javascript to check with passport site whether current us…

Discourse currently has ability to “Deactivate account” via Admin panel. I am wondering if we could use it to implement “Voluntary consent” required by GDPR for existing users. Something like mass deactivation with custom activation email text explaining why existing users need to give consent by c…

No, “activation” is only “prove you own this email” and unactivated accounts (with no posts, because of admins doing this kind of thing) are deleted after 7 days.

Yes I know that, but I was just thinking about easy method to do what original poster asked about, i.e. make existing users to give explicit voluntary consent to process their data via clear affirmative action. Under GDPR you need to collect such consent from existing users and be able to demonstrat…

This plugin may be helpful: [imagen] Custom Wizard Plugin mage plugin tada It is now much easier to subscribe for the advanced features tada Now all you have to do is hit ‘Subscribe’ from the admin page of the installed Custom Wizard Plugin and follow the prompts, and Au…

One important thing that is missing in requesting GDPR consent as “user field” is that changing user fields does not generate any entry in Users “Action logs”. Under GDPR it is important to be able to demonstrate when consent was given. For this Discourse should log such event in the user’s “Action …

Cómo hacer que los usuarios acepten explícitamente los ToS

Soporte

ChrisBeach (Chris) 26 Abril, 2018 22:30 58

This plugin may be helpful:

It’d be useful to know if anyone has used it for GDPR purposes, and if they could share their wording and config?

Tema		Respuestas	Vistas
GDPR and anonymizing personal data Community Building gdpr , privacy	75	19628	1 Diciembre 2018
Cookie compliance under GDPR Community Building gdpr	63	12194	5 Mayo 2023
GDPR countdown and compliance Community Building gdpr	90	15223	19 Junio 2018
Providing data for GDPR Community Building gdpr , privacy	81	12911	20 Diciembre 2018
Cookie Consent, GDPR, and Discourse Site Management explanation	1	3792	10 Octubre 2025

Cómo hacer que los usuarios acepten explícitamente los ToS

Temas relacionados