DEF CON Groups branding guidelines: names, messaging, and logos
Group branding should make two things clear: which local community is communicating, and who is responsible for its activities. A familiar logo must not create a misleading claim of authority or endorsement.
Names and terminology
Write DEF CON as two words in formal copy. Refer to the program as DEF CON Groups and a local community as a DEF CON Group or DCG. Use the group's confirmed public name or identifier consistently.
DEF CON Chapters are not part of the program. Do not use “chapter” to describe a group or create chapter-based titles. DEF CON Groups has no ambassador role; use the actual role you hold.
Groups should confirm naming changes with the department. Do not assign a new identifier to yourself or assume a name used in another region is available locally.
Describe the relationship accurately
A useful description identifies the local group and what it does: “[Approved group name] is a local DEF CON Group bringing people together to learn, share projects, and explore technology.”
For an organizer biography, use “POC for [approved group name]” when that is your recognized role. Do not turn a local role into a national, regional, or global appointment.
For an event, identify the organizing group. Use the meetup and event guidance to distinguish local activity from official DEF CON programming.
Logos and artwork
Use assets supplied or expressly approved for the intended purpose, and follow any instructions accompanying them. Finding a logo online does not establish permission for every use. A group's own artwork, department artwork, and DEF CON's main identity are not interchangeable evidence of authorization.
Do not create artwork that misleadingly suggests DEF CON staff status, an official event, an ambassador appointment, or a department endorsement. Keep local organizer identity clear in posters, websites, slide decks, merchandise, and social profiles.
For a proposed logo treatment, co-branding arrangement, or commercial use, send the department the mockup, intended placement, audience, and proposed distribution or sale. Confirm which permission and asset requirements apply before committing to production.
Technical specifications
Use the technical requirements supplied with the approved asset package. This page does not supply new color values, clear-space measurements, minimum sizes, font requirements, alteration permissions, or a merchandise license. If the required specification is missing, ask for it rather than inventing one.
Messaging examples
| Use | Clear wording | Avoid |
|---|---|---|
| Group description | “[Approved name], a local DEF CON Group” | “Official DEF CON chapter” |
| Local organizer | “POC for [approved name]” | “DEF CON ambassador” |
| Meetup | “[Approved name] monthly meetup” | “Official DEF CON [city] event” without authorization |
| Separately named event | “[Event], presented by [approved group name]” | Wording implying DEF CON is the producer |
| Sponsor | “[Sponsor] supports this [group name] meetup” when accurate | “DEF CON sponsor” based on local support alone |
These examples explain accurate attribution. They do not independently approve an event, sponsor, logo, or commercial arrangement.
Branding and representation · Back to FAQ · Contact the department