§ 15 — Code of Conduct

A room worth being in
is built on the same terms for everyone.

The compact between everyone in the hall.
This is what we expect of one another — speakers, sponsors, organisers, attendees, staff. It is short. It is binding. It applies on-site, in chat, and on stage. Reports go to a confidential committee staffed independently of programme leads.

Article I · The compact

A room is the people who choose to be in it.

The OpenSSL Conference exists because cryptography is a craft — and crafts are taught and improved in rooms full of people who trust each other enough to disagree out loud.

This Code is the floor of that trust. It is not a list of slogans. It is the agreement we make with one another the moment we walk in the door, log into the chat, or step on stage.

It applies to everyone — attendees, speakers, sponsors, organisers, volunteers, contractors, members of the press. There are no carve-outs for keynote speakers, no exemptions for diamond sponsors, and no exceptions for the people who wrote the policy.

Article II · What we expect

Be the colleague you wish you had.

  • Assume good intent — in others, and in yourself. People come to this conference from 30+ countries, often speaking their second or third language. Read generously.
  • Disagree on the work, not the person. Hard technical critique is welcome — expected, even. Personal attacks are not.
  • Make room for the quieter voice. If you have spoken twice in a Q&A, let someone else go third. If you ran the last two BoFs, let someone else propose the next.
  • Credit the work you stand on. Cite collaborators, prior art, the maintainer who reviewed your patch at midnight, the intern who wrote the test case.
  • Use people's stated names and pronouns. Badges have them for a reason.
  • Mind the on-call. Some attendees are reachable for security incidents during the conference. If someone steps out, that is the work, not rudeness.
Article III · What is unacceptable

A short list, plainly stated.

We don't write this list because we expect trouble. We write it because the absence of a written list is what lets harassment travel from one conference to the next.

  • Harassment of any kind — including but not limited to comments or behaviour related to gender, gender identity, sexual orientation, disability, neurotype, physical appearance, body size, race, ethnicity, age, nationality, immigration status, or religion.
  • Sexualised language, imagery, or attention in talks, slides, swag, social spaces, or one-on-one conversation.
  • Deliberate intimidation, stalking, or following — in person or online, including persistent unwanted contact via DMs, e-mail, or LinkedIn after the conference.
  • Sustained disruption of talks, workshops, or other events.
  • Photographing or recording a person without their consent.
  • Threats of violence or doxxing, on-site or online, against any attendee, speaker, or staff member.
  • Retaliation against anyone who reports a Code of Conduct issue in good faith, or who participates in an investigation.
Welcome
  • "Your patch breaks ABI on macOS — here's the diff."
  • Asking a speaker to clarify a slide after the talk.
  • Telling someone you'd rather not be photographed.
  • Inviting a small group out for coffee, and accepting "no".
Not
  • "Your patch is the kind of thing only X would write."
  • Cornering a speaker to insist they're wrong, after they've left the room.
  • Posting a candid photo of someone over their objection.
  • Repeating an invitation after the first "no".
Article IV · Where it applies

In the hall, and the spaces around it.

This Code applies to the conference floor, the workshop rooms, the hallway track, the sponsor hall, the host dinners, the official social events, and the conference shuttle. It applies in the conference Slack and Discord during the event window. It applies to anything published from the conference — talk recordings, BoF notes, the conference Mastodon.

It does not police what attendees say to each other privately, in unrelated venues, after the conference is over — with one exception: retaliation against a reporter is in scope, wherever and whenever it happens.

Article V · If something happens

You have three doors.

Pick whichever feels safest. We'd rather hear about something small than learn about something large, late.

You don't need to know what to call what happened. You don't need to be sure it "qualifies". You don't need to use the word harassment. If something on or around this conference made you feel unsafe, tell us.

№ 06 · Reporting Confidential · Staffed independently of programme leads

Three channels. Pick the one that feels safest.

All three reach the Code of Conduct Committee — a small, named group rotated for each edition, none of whom sit on the programme committee or report into a sponsor.

Door 01 · In person

Find a steward.

Stewards wear a black sash with a single gilt band. They're at the registration desk, at the back of every room, and in the sponsor hall. They will take you somewhere quiet, listen, and — if you want — fetch a committee member.

Where to find them →
Door 02 · By message

conduct@openssl-conference.org

Reaches the four committee members directly. PGP key on the conference site. Replied to within 12 hours during the event, 48 hours otherwise. You may use a pseudonymous address; we won't ask you to verify.

Open mail →
Door 03 · By phone

+420 · 222 · 313 · 200

The conference duty phone, answered live by the on-call committee member during venue hours (08:00–23:00 CET, 12–15 October). Voicemail outside those hours is checked hourly.

Call →

The 2026 committee: Adriana Čermáková (chair, independent), Yuki Tanaka (cryptographer, ETH Zürich), Femi Adebayo (lawyer, EFF Brussels), Mira Hoffman (community lead, OpenSSL Foundation). Names are published so you know whom you are reaching. Conflicts are declared and rotated out of any matter that touches them.

Article VI · Consequences

A ladder, not a switch.

  1. 01 A private word For one-off behaviour the committee believes is unintended. The person is told what was reported and what to change. Stays inside the committee.
  2. 02 A formal warning Recorded against the registration. Carries a named restriction — e.g. "no further attendance at the host dinner" or "no further interaction with the reporter".
  3. 03 Removal from a session From a specific room, track, or social event — for the rest of that day, or the rest of the conference. No refund.
  4. 04 Removal from the conference Badge revoked. Access withdrawn from the venue, online channels, and remaining social events. No refund. Sponsors lose their booth; speakers lose their slot.
  5. 05 Ban from future editions For one or more future editions, or permanently. The committee publishes the count of bans each year, never the names — unless the person has chosen, themselves, to make the matter public.
Article VII · Confidentiality

Reports stay with the committee.

The committee discusses reports only with the people directly involved and — if a sanction crosses level 04 — the conference chair. Reports are not shared with employers, programme committees, sponsors, the press, or other attendees. The reporter's identity is not shared with the subject of the report unless the reporter explicitly consents.

We publish a redacted summary after the conference — counts only, no names — so the community can see that the process was used and how. The first edition's summary is at openssl-conference.org/2025/coc-report.

Adopted · 09 January 2026 · Edition № 02 For the OpenSSL Conference Committee Revised every edition · Diffs published
§ 16 — The Official Text

The editorial chapter above is how we read the compact aloud.
What follows is the adopted instrument — verbatim, in its registered form.

OpenSSL Conference Code of Conduct

Last Updated: 12 March 2026

1Introduction

The OpenSSL Conference 2026 is dedicated to creating a professional, inclusive, and respectful environment for all participants. This Code of Conduct establishes the standards of behaviour expected from attendees, speakers, sponsors, and volunteers to ensure a welcoming and harassment-free experience for everyone.

2Our Commitment

We are committed to fostering a respectful and harassment-free conference experience for everyone, regardless of:

  • Age
  • Gender identity or expression
  • Sexual orientation
  • Disability
  • Physical appearance
  • Body size
  • Race or ethnicity
  • Nationality
  • Religion or lack thereof
  • Political affiliation
  • Technology choices

3Expected Behaviour

All participants are expected to:

  • Be Respectful: Treat everyone with courtesy and consideration.
  • Communicate Appropriately: Use welcoming and inclusive language. Be mindful of your speech and actions.
  • Collaborate: Encourage a spirit of cooperation and understanding.
  • Respect Privacy: Obtain permission before sharing photographs or recordings of others.
  • Follow Instructions: Comply with the directives of conference staff and venue personnel.
  • Participate Authentically: Contribute positively to discussions and activities.

4Unacceptable Behaviour

The following behaviours are considered unacceptable and will not be tolerated:

  • Harassment: Includes offensive verbal comments, intimidation, stalking, unwanted photography/ recording, sustained disruption, inappropriate physical contact, or unwelcome sexual attention.
  • Discrimination: Prejudicial treatment based on the protected characteristics listed above.
  • Hate Speech: Incitement to violence or hatred against individuals or groups.
  • Physical or Verbal Abuse: Aggressive behaviour, threats, or any form of violence.
  • Sexual Harassment: Unwelcome advances, requests for sexual favours, or inappropriate sexual conduct.
  • Inappropriate Use of Imagery: Displaying sexualized or violent images in public spaces.
  • Disruption: Interrupting presentations, events, or activities without an appropriate cause.
  • Retaliation: Any form of retaliation against individuals who report misconduct or participate in an investigation.

5Reporting Incidents

  • If you experience or witness unacceptable behaviour, please report it immediately:
  • On-Site: Visit the Information Desk and ask for the Code of Conduct Officer
  • Email: conduct@openssl-conference.org
  • Phone/Text: +45 20899609

All reports will be handled with confidentiality and discretion.

6Investigation Process

Upon receiving a report, the conference organisers will:

  • Acknowledge Receipt: Confirm that the report has been received.
  • Investigate Promptly: Conduct a thorough and impartial investigation.
  • Maintain Confidentiality: Protect the identity of the reporter and any involved parties.
  • Take Appropriate Action: This may include warnings, expulsion from the conference without refund, or notification of local law enforcement.

7Consequences of Unacceptable Behaviour

Participants asked to stop any unacceptable behaviour are expected to comply immediately. Consequences may include:

  • Minor violations (e.g., inappropriate language, disrespectful behaviour) → Warning.
  • Major violations (e.g., harassment, threats, serious disruptions) → Immediate expulsion.
  • Severe violations (e.g., physical violence, legal infractions) → Law enforcement involvement.

8Appeals Process

If you believe you have been unfairly accused or disciplined, you may appeal by contacting conduct@openssl-conference.org within seven days of the incident. Appeals will be reviewed by the OpenSSL Conference Organising Committee within seven days, in accordance with the Code of Conduct guidelines and all available evidence. The committee's decision will be final.

9Scope

This Code of Conduct applies to all conference-related activities, including:

  • Conference sessions and workshops
  • Social events and networking gatherings
  • Online forums and social media interactions related to the conference
  • Communications via conference-provided channels, such as email and messaging platforms

10Social Media Policy

We encourage respectful and constructive engagement on social media. Please:

  • Be Mindful: Respect others' privacy and preferences when sharing content.
  • Avoid Harassment: Do not use social media to harass or demean others.
  • Use Hashtags Responsibly: When using conference-related hashtags, ensure your content aligns with this Code of Conduct.
  • Do Not Misrepresent: When engaging on social media about the conference, do not misrepresent discussions, sessions, or individuals. Ensure that shared content aligns with the values of inclusivity and professionalism.

11Inclusivity and Accessibility

We strive to make the conference accessible to all participants. If you have any specific needs or require accommodations, please contact us at conduct@openssl-conference.org.

12Anti-Retaliation Policy

We will not tolerate any form of retaliation against individuals who report misconduct or participate in investigations. Any participant engaging in retaliatory behavior will face consequences as outlined above.

13Acknowledgment

By attending the OpenSSL Conference 2026, you agree to abide by this Code of Conduct. We appreciate your cooperation in creating a safe and enjoyable experience for everyone.

14Contact Information

Email: conduct@openssl-conference.org