This page covers privacy issues concerning material presented in the HeyPressto! conference and privacy and data protection issues for this, the HeyPressto! conference website.
Who we are
Hey Pressto! is organised by people with an interest in WordPress, ClassicPress, website development and the web. We are not affiliated with WordPress, ClassicPress or any other group involved in supporting WordPress. We welcome participation from anyone who is interested in the use of WordPress and ClassicPress for content development and delivery on the web, and we are very happy for anyone interested in those topics and their wider effects to join our discussions.
Our website address is: https://heypresstoconf.org, you can contact us via email@example.com . If you would like to know more about the individuals involved, here is information about the two lead organizers.
Privacy regarding HeyPresto! conference presentations
You should be aware that all conference tweets and post-conference discussions on Twitter are public. Tweets tagged #HeyPresstoConf20 or #HeyPresstoConf will be archived by us and maybe re-published on the HeyPressto! website or curated via Twitter moments etc. so that others who have missed the discussion or particular conference sessions can review the presentations and associated conversations.
Please be aware that as tweets are public it is possible that they may be used for research purposes without your individual consent. If those who are leading the conference plan to do any research on the chats then we will endeavour to make participants aware of the research protocol. It may be however, that others will access our archives or curate their own archives and use them for research purposes without making us aware. We would encourage any individual undertaking research on the community hashtag to alert us to their plans so that we can help support their work.
Please remember that if you are presenting your work as part of HeyPressto! it is not acceptable to breach the confidentiality of individuals such as users, clients or colleagues, please make sure you have consent to share any identifiable data that is not in the public domain. The moderators will endeavour to ensure that this confidentiality is respected by contacting those who may be sharing information inappropriately if we are aware of breaches. We ask all participants to help others address this issue sensitively. However, you must be aware that archives will exist of deleted tweets and that it may not be possible to delete tweets from these. Even if deleted from an individual’s timeline or an archive, a tweet may still have been manually retweeted or captured as an image.
What personal data we collect and why we collect it
We really don’t want to be collecting data about you. If you are presenting we will need some means of contacting you with information relating to the running of the conference, such as presentation times, but otherwise we don’t think we have much use for your data.
Anything submitted via a contact form will be deleted once we have dealt with the reason for you contacting us.
When submitting a presentation and using the contact form, we will set a cookie for security purposes.
Embedded content from other websites
We may embed Twitter moments and this may result in Twitter setting cookies and other trackers on your device. We will aim to alert people to this before the page loads.
We use no analytics at all.
Who we share your data with
No one at all.
How long we retain your data
Your tweets may be on Twitter for as long as you choose them to be so. We may add them to Twitter moments and display them via this site. We won’t keep them, that’s a relationship between you and Twitter.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data