RubyConf 2021 is dedicated to providing a harassment-free conference experience for everyone, regardless of gender identity, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form. Sexual language and imagery is not deemed appropriate for any conference venue, including talks. Conference participants violating any of these rules may be sanctioned or expelled from the conference, at the discretion of the conference organizers.
Harassment includes, but is not limited to: offensive verbal comments related to gender identity, sexual orientation, disability, physical appearance, body size, race, or religion; sexual images in public spaces; deliberate intimidation; stalking; following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and any unwelcome sexual attention. Participants asked to stop any harassing behavior are expected to comply immediately.
If a participant engages in harassing behavior, conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference. If you are being harassed, notice that someone else is being harassed, or have any other concerns regarding violations of this policy, please contact a member of conference staff immediately.
Having a safe environment for our conference participants -- in a physical or in a virtual setting -- is of paramount importance to us, and we value your help towards creating this space.
Ruby Central, Inc. and all associated members of the RubyConf 2021 planning team are dedicated to providing an environment for our community that is accessible, welcoming, and inclusive. While we try to seek these places of inclusivity as much as we can, we're also aware that we don't always see what might be an obstacle to attendance for those interested in RubyConf.
As such, we encourage anyone who has questions about whether RubyConf would be the right conference for them and suggestions about how to increase our event's accessibility to email us at firstname.lastname@example.org -- while we can't promise the ability to accommodate each individual situation, we absolutely commit to listening to every concern and request with an open ear.
Any changes to your registered ticket must be requested through the Ticket Change Request Form.In-Person Registrants
If you've purchased an in-person ticket and decide not to attend, you have the option of doing the following by Monday, Oct. 18th:
- A refund, minus a $30 processing fee.
- Request a voucher for the 2022 RubyConf. This voucher can only be applied for in-person attendance at the RubyConf 2022.
- Switching to a virtual ticket and being refunded the difference in price.
Virtual ticket refunds will not be given for this event. However, virtual ticket holders can expect to receive online access to the recorded sessions.
If you're interested in switching to an in-person ticket you may submit your request by completeing the Ticket Change Request Form. Ruby Central will process your request within 48 hours. A payment invoice will be emailed to you and your in-person ticket will be confirmed once the difference is paid.
If RubyConf cancels the in-person portion of our event due to circumstances beyond our control, we reserve the right to
- Issue vouchers for future conferences in lieu of refunds
- Transfer in-person tickets to virtual tickets and refund the difference in ticket prices minus the $30 processing fee.
Attendee Data and Privacy
All individual Attendee data collected by Ruby Central, Inc. is used for only two purposes. The first is to plan, manage, and execute the event for which the Attendee registered, in this case, RubyConf 2021. This includes emailing the Attendee with RubyConf 2021 details.
The second is — if the Attendee opts in only — to send emails with details of Ruby Central conferences (RailsConf and RubyConf) in the next year. Attendees who do not wish to receive emails about our conferences in the next year should not opt in when registering for RubyConf 2021. Alternately, Attendees who opt in, but then decide they do not wish to receive these emails will be able to unsubscribe to emails once they’re received. For Attendees who opt in, we will only keep those email addresses for one year.
Attendees may request to view a copy of their own data, to correct their data, or to delete their data at any point. All requests can be made via email to email@example.com and must come from the same email that is on file. Requests will be responded to within 30 days. When Ruby Central, Inc. provides copies of Attendee data, it will be in .csv format unless otherwise requested.
Attendee data is shared with third-party conference vendors only as necessary, e.g., Attendee addresses are shared with our swag bag fulfillment vendor for the purpose of sending RubyConf 2021 swag bags. This data is shared via secured .xls files. Ruby Central, Inc. requires all vendors we work with to be GDPR-compliant. Attendee data may also be exposed to Ruby Central, Inc. staff and onsite volunteers.
Some aggregated Attendee data is shared with conference Sponsors; however, any questions asking for this shared data are 1. optional, 2. marked clearly as shared with Sponsors, and 3. shared only as aggregated percentages. Ruby Central, Inc. never shares individual Attendee data with Sponsors.
If the Attendee data we’re keeping for our conferences is breached, we will notify affected Attendees within 72 hours.
Additionally, Attendees can separately opt into directly receiving information from RubyConf 2021 Sponsors. Terms and conditions for this opt-in are regulated specifically by each Sponsor and Ruby Central is not responsible for oversight over this usage; however, we do set the expectation with our Sponsors that they act in good faith regarding Attendee information.
Any questions regarding this policy can be directed to firstname.lastname@example.org.