# Using Events for Discourse 3.0 webinar?

**URL:** <https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540>\
**Category:** Site feedback\
**Created:** [January 18, 2023, 10:25pm UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540 "2023-01-18T22:25:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nathank](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nathank/32/290039_2.png) [@nathank](https://meta.discourse.org/u/nathank)\
**Post date:** [January 19, 2023, 11:09pm UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540/3 "2023-01-19T23:09:39Z")

</div>

> [@HAWK](#):
>
> We haven’t ever sought permission to use details from Meta accounts for other things

I guess the key is whether this event is arranged by [meta.discourse.org](http://meta.discourse.org) or by CDCK itself (if those entities are truly separate).

Personally, if I RSVP’d within [meta.discourse.org](http://meta.discourse.org) I’d expect my data to be utilised for something like this. Ditto for a [zoom.org](http://zoom.org) webinar ‘owned’ by CDCK.

In my domain (health) ‘privacy’ is often used as an inappropriate excuse by those who don’t want to go to the trouble to safely share data in ways that benefit the user (in our case the patient). And patients generally suffer as a result while the corporate butt is covered. Not cool.

---

_[View the full topic](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540)._