Guidelines

1 Preamble

1.1 All persons participating in CLASS events and interacting with the CLASS Ireland through the website, FetLife group or FetLife profile are subject to the FetLife terms of use as well as any applicable local laws and regulations.  

1.2 While the FetLife terms of use and local laws and regulations take precedence in their respective domains, all participants in CLASS events are additionally expected to adhere to the the FetLife community guidelines and the CLASS principles below.

1.3 While this is not a legal document and these principles are non-binding, failure to adhere to these principles may result in exclusion from future CLASS events, at the discretion of the Board of Trustees (BOT).

2 Roles and Responsibilities

2.1 Owner

2.1.1 The owner is the primary individual in charge of the CLASS FetLife profile and website and is also listed as the owner of the CLASS Ireland FetLife group. 

2.1.2 Responsibilities of the owner include:

  • 2.1.2.1 Posting content to the CLASS profile and website, including obtaining required permissions as outlined in the photography and writing sections below, and managing relationships as outlined in the relationship section below.
  • 2.1.2.2 Maintaining database of posted content and individuals with rights to request removal of each post.
  • 2.1.2.3 Maintaining a list of individuals on the Board of Trustees (BOT), as well as individuals currently serving as organisers, moderators, and custodians. The owner is responsible for disseminating this information as necessary for the functioning of the group.
  • 2.1.2.4 Posting of CLASS events organised by approved organisers.
  • 2.1.2.5 Managing communication through the CLASS profile and email address, including directing potential participants to the applicable event organiser or munch moderator and responding to requests made by individuals for a copy of their personal data stored by CLASS as per the personal data section below.
  • 2.1.2.6 Maintaining list of individuals banned by the BOT
  • 2.1.2.7 Ensuring CLASS organisers are aware of individuals currently banned by the BOT as appropriate.
  • 2.1.2.8 Naming one or more backup owner(s) and providing access to the named individual(s), particularly in advance of prolonged periods of absence/inactivity.
  • 2.1.2.9 Providing backup owner(s) and successor with access to lists and databases listed above.
  • 2.1.2.10 Serving on the BOT.
  • 2.1.2.11 Management of BOT, organisers, custodians, and munch moderators. The owner is also responsible for maintaining lists of individuals in each of these roles, and for directing enquiries to the appropriate individuals as required.
  • 2.1.2.12 Maintenance of the CLASS website.

2.1.3 The owner is appointed for a term of up to one year, typically transitioning ownership on 20 July. This term may be extended by unanimous vote of the BOT after each year of service for a period of up to an additional year. Owners may serve multiple terms.

2.1.4 The owner must nominate a successor from the BOT upon assuming group ownership. This successor may be changed at any time up to one month prior to the end of the owner’s term. At the conclusion of the term, the former owner may remain on the BOT or step down at their discretion. This decision is to be communicated in writing to the new owner.

2.1.5 In the event the owner is unable or unwilling to continue through the full one-year term of group ownership, ownership of the group will transfer to the nominated successor when the current owner steps down.  The new owner must nominate a new successor and will serve until the next transition date, at which time the BOT may vote to allow the new owner to serve a subsequent full-year term or the newly appointed successor will assume ownership.

2.2 Board of Trustees

2.2.1 The board of trustees (BOT) serves as the voluntary governing body of CLASS.  

2.2.2 Responsibilities of the BOT include:

  • 2.2.2.1 Approval of CLASS organisers by unanimous vote of current trustees.  
  • 2.2.2.2 Decisions to exclude participants. CLASS prefers to work with participants to correct problematic behaviours where possible. In the unfortunate circumstance when a ban is considered, the BOT will endeavour to reach consensus before imposing the exclusion.  However, if the BOT is unable to reach consensus, a decision will be reached by majority vote of the current trustees.
  • 2.2.2.3 Review of any recorded incidents at CLASS events, including communication of lessons learned/best practices to the organisers and the group at large as deemed prudent.
  • 2.2.2.4 Approval of changes to these guidelines by majority vote of current trustees.  
    • 2.2.2.4.1 The owner may make emergency changes to these guidelines as needed. In the event emergency changes are made, it is the responsibility of the owner to notify the trustees and to seek a formal approval and/or additional revision of the guidelines within one month of the emergency change.
  • 2.2.2.5 Provide assistance to owner as requested.
  • 2.2.2.6 Trustees serve as moderators for the CLASS Ireland FetLife group and/or administrators for the website.
  • 2.2.2.7 Trustees approve changes to the FetLife group rules by majority vote.
  • 2.2.2.8 Trustees meet minimally once per year to discuss current issues, appointment of new trustees, and ownership transition.

2.2.3 Appointment of trustees

  • 2.2.3.1 CLASS will attempt to maintain 5-10 trustees at all times.  
  • 2.2.3.2 CLASS will make efforts to include in the trustees at least one top, one bottom, one woman, one man, and one trans individual.
  • 2.2.3.3 CLASS will aim to appoint a new trustee minimally every six months.  
  • 2.2.3.4 Approval of new trustees is by unanimous vote of current trustees.  
  • 2.2.3.5 After approval, a potential new trustee may join the BOT within six months. If more than six months elapse before the individual can join the BOT, another approval vote must be taken if the individual wishes to join the BOT.
  • 2.2.3.6 Trustees may resign at any time via written message to CLASS. Once a trustee resigns, that individual must wait a minimum of six months before applying to re-join the board.  
  • 2.2.3.7 In the event that trustees are unable to actively participate in discussions and voting, trustees may name a proxy from among the other BOT members for voting purposes in advance. Proxies are designated by written message to the owner, and may be designated for periods not exceeding two months.
  • 2.2.3.8 Trustees are considered inactive if three consecutive requests for a vote go unanswered for one week or longer, unless a proxy has been nominated in advance.
  • 2.2.3.9 Inactive trustees are not counted for voting purposes; the vote of an inactive trustee is not required for a majority or unanimous ruling. Inactive trustees may become active again by message to the owner within six months. Trustees inactive for six months or longer will be removed from the BOT and considered to be trustees emeriti.
  • 2.2.3.10 Trustees have one week to respond to all requests for a vote- either personally or by proxy.  Trustees who have yet to vote must be contacted a minimum of three times within five days of the initial request for the vote, using a minimum of two communication channels, if the trustee’s vote is required to reach either majority or unanimity as required by the matter at hand.  If no response has been received after one week, the trustee is considered inactive for the purpose of the vote in question; the vote of an inactive trustee is not required for a majority or unanimous ruling.  
  • 2.2.3.11 A trustee (including the owner) may be removed by majority vote of remaining trustees. Any trustee may initiate this voting process.

2.3 Trustees Emeriti

2.3.1 Trustees who resign or become inactive may choose to become trustees emeriti. These individuals may re-join the BOT after a minimum of six months if desired, and must be approved by majority vote of the current BOT. Trustees emeriti retain their rights as organisers and moderators and may serve as custodians.  Trustees emeriti may be removed by majority vote of remaining trustees.

2.4 Organisers

2.4.1 Organisers are individuals who coordinate CLASS events. Organisers must be approved by a unanimous vote of the BOT. Appointment to the BOT also qualifies an individual as an organiser. After approval, a potential new organiser may accept the role in writing within six months. If more than six months elapse, another approval vote must be taken if the individual still wishes to become an organiser. Once approved, an organiser may be removed by a majority vote of the BOT.

2.4.2 Responsibilities* of organisers, for the events they are organising, include:

  • 2.4.2.1 Selection and booking of venue.
  • 2.4.2.2 Selection of participants.
  • 2.4.2.3 Providing owner with text and other required details for event posting.
  • 2.4.2.4 Making every effort to ensure individuals banned by the BOT do not attend events.
  • 2.4.2.5 In addition to individuals banned by the BOT, organisers may refuse admission to any additional individuals at their discretion. The owner should be informed of anyone refused admission to the event and should be notified if the organiser wishes for the BOT to consider banning the individual(s) from all CLASS events.
  • 2.4.2.6 Establishing and communicating safety protocols for the event, including the use of safewords, monitoring staff, first aiders, and emergency procedures.
  • 2.4.2.7 Communicating the CLASS Code of Conduct to all participants, as well as any additional policies and procedures in place for the event.
  • 2.4.2.8 Establishing event photography policy in alignment with the photography selection below and communicating this policy to all participants.  
  • 2.4.2.9 Selection and training of monitoring staff for events.
  • 2.4.2.10 Delegation of responsibilities to other participants may be performed at the discretion of the organiser. However, the organiser is responsible for ensuring these individuals perform delegated responsibilities effectively.
  • 2.4.2.11 Soliciting feedback from all participants after each event.  It is recommended to delegate this duty to a BOT member not in attendance to provide a fresh perspective.

2.4.2. 12 *CLASS events may vary widely in size and nature, consisting of anything from a small group in a private home to larger group events in public venues to virtual events and others. Therefore, certain responsibilities listed above may or may not apply to specific events.  

2.4.3 Organisers are only required to serve the role of organiser at events for which they volunteer to organise and are listed as the official organiser. Additional organisers in attendance may assist the official organiser on a voluntary basis as agreed with the official organiser, but this is not to be expected or required.

2.5 Munch Moderators

2.5.1 Munch moderators are individuals who coordinate CLASS munch events. Moderators must be approved by a unanimous vote of the BOT. Appointment to the BOT or as an organiser also qualifies an individual as munch moderator. After approval, a potential new moderator may accept the role in writing within six months. If more than six months elapse, another approval vote must be taken if the individual still wishes to become a munch moderator. Once approved, a munch moderator may be removed by a majority vote of the BOT.

2.5.2 Responsibilities of munch moderators, for the munches they moderate, include:

  • 2.5.2.1 Securing venue for the munch and pre-meet, including making bookings as appropriate.
  • 2.5.2.2 Selection of participants. Generally, any individual in good standing who has previously attended a munch is free to attend.  New participants may be asked to attend a pre-meet prior to attending their first CLASS munch. However, each munch moderator may adjust these general policies at their discretion for munches they organise.
  • 2.5.2.3 Informing participants of venue for munch and/or pre-meet as appropriate.
  • 2.5.2.4 Providing owner with text and other required details for the munch event posting.
  • 2.5.2.5 Making every effort to ensure individuals banned by the BOT do not attend CLASS munches.
  • 2.5.2.6 In addition to individuals banned by the BOT, munch moderators may refuse admission to any additional individuals at their discretion. The owner should be informed of anyone refused admission to the munch, and should be notified if the moderator(s) wish for the BOT to consider banning the individual(s) from all CLASS events.
  • 2.5.2.7 Communicating and enforcing munch guidelines for the munch.
  • 2.5.2.8 Selection and training of assistant moderators for the munch, if necessary. Assistant moderators do not require approval of the BOT but may only assist the primary moderator in enforcing the code of conduct or in other administrative duties at the discretion of the primary moderator. Assistant moderators may not organise CLASS munches independently; any assistant moderator wishing to do so should contact the owner and express a desire to be approved as a primary moderator.
  • 2.5.2.9 Reporting to the owner any conduct at the munch which may indicate an individual is not suitable for participation in CLASS events.

2.5.3 Munch moderators are only required to serve the role of moderator at events for which they volunteer to moderate and are the official moderator or assistant moderator. Additional moderators in attendance may assist the official moderator on a voluntary basis, but this is not to be expected or required.

2.6 Hosts

2.6.1 Hosts are individuals providing or organising the hiring of a venue for CLASS events. The host and organiser of an event may be a single individual. Otherwise, the host is approved by the event organiser.  

2.7 Monitors

2.7.1 Monitors are CLASS-affiliated individuals appointed by an event organiser to help ensure events run smoothly. The duties of monitors vary by event and will be specified by the event organiser. In general, monitors may be asked to:

  • 2.7.1.1 Assist with timekeeping and logistics
  • 2.7.1.2 Listen for safewords and help ensure they are heard and respected
  • 2.7.1.3 Remind event participants of event and venue rules
  • 2.7.1.4 Provide aftercare and/or direct participants seeking aftercare to  the organiser
  • 2.7.1.5 Contact the organiser with any questions on procedures or if situations arise in which the monitor is uncomfortable or unsure of how to handle.

2.8 Custodians

2.8.1 Custodians are appointed by the owner to document and manage CLASS group supplies and equipment. If a custodian is not a member of the BOT, the appointment must be approved by majority vote of the BOT.  Once approved, a custodian may be removed by a majority vote of the BOT, after which the owner must designate a temporary custodian to serve in this role until a new custodian is identified.

2.8.2 Responsibilities of the custodians include:

  • 2.8.2.1 Maintenance of the CLASS equipment and supply inventory, including items owned by CLASS and items on loan to the group.
  • 2.8.2.2 Facilitating transportation of CLASS supplies and equipment, including negotiation of loan of items between regions as required.

2.9 Participants

2.9.1 Participants are individuals who physically attend CLASS events.  Participants are selected and approved at the discretion of the organiser for each individual event. Participants are advised that each organiser and event may have different criteria for selection and approval of participants.

2.10 Friends

(aka CLASSmates)

2.10.1 Friends are individuals listed as friends on the CLASS Ireland profile. Friends are accepted and rejected at the discretion of the owner. Potential friends are advised that a brief, polite note of introduction stating their reasons for interest in the group will greatly increase the chance of friend requests being accepted. Please note that acceptance of a friend request does not have any bearing on selection for participation in events.

2.11 Relationships

2.11.1 Only individuals who participate in CLASS events will be listed as teachers/students on the CLASS profile.  Written permission will be sought from each individual prior to adding the relationship.

2.11.2 However, any friend of the CLASS profile is permitted to add relationship(s) to their own profile at their discretion. Please note that relationship status does not have any bearing on selection for participation in events.

2.12 Group Members

2.12.1 Group members are individuals listed as members of the CLASS Ireland FetLife group. Group members may be banned at the discretion of the BOT. Note that group membership is not generally required for participation in events.

2.12.1.2 Group members participating in group discussions are asked to adhere to the group rules

3 Communication

3.1 CLASS Postings

3.1.1 The owner is responsible for maintaining the CLASS profile and website, and may reject or remove any content at any time, with or without warning. Friends and participants are welcome and encouraged to submit material for posting. Submissions are subject to the FetLife content guidelines. In addition, the following guidelines shall be followed when posting submitted material.

3.1.2  Photography

3.1.2.1 Photography is only permitted at CLASS events with prior permission from the organiser, host, and all participants in the photograph (including those in the background).  The organiser may also designate a house photographer(s) responsible for all photography, including obtaining prior permission from all applicable individuals and ensuring the photographs are taken in a suitable location.

3.1.2.2 Photographs from CLASS events may be submitted for posting to the CLASS profile and/or website. To submit a photograph, send the file to CLASS (class.ireland@gmail.com). The following information must be included with each submission:

  • 3.1.2.2.1 Explicit, written permission from the submitter to post the photograph on the CLASS profile and/or website.
  • 3.1.2.2.2 Desired caption
  • 3.1.2.2.3 FetLife usernames for (as applicable):
    • 3.1.2.2.3.1 Submitter
    • 3.1.2.2.3.2 All participants visible in the photograph (including those partially visible and those in the background)
    • 3.1.2.2.3.3 Photographer
    • 3.1.2.2.3.4 Event organiser
    • 3.1.2.2.3.5 Event host
    • 3.1.2.2.3.6 Any others with a creative interest in the photograph as applicable (i.e., costumes, lighting).

3.1.2.3 If any of these individuals does not have a FetLife username, alternate contact information should be provided. Written permission (via email or PM) will be obtained by CLASS from each of these individuals prior to posting the photograph. Additionally, any of these individuals may request for the photograph to be removed at any time. CLASS will attempt to honour all requests for removal as soon as possible, typically within 24 hours

3.1.2.4 Photographs of documents used in the context of role play events (i.e. punishment logs, timetables, etc), may be posted with permission from the organiser only. Inclusion of one’s role play name in these documents is optional; the organiser is responsible for communicating to participants which documents will be posted and providing participants a mechanism to opt out of inclusion in these documents.  

3.1.2.5 All accepted photographs will be uploaded as visible to all FetLifers and publicly posted to the website as applicable. CLASS will not transmit photographs to a third party at any point in this process. However, those submitting and giving authorisation for the posting of photographs are reminded that, once posted, CLASS is not able to guarantee that the photograph will not be disseminated by third parties viewing the photograph from the CLASS profile and/or website.

3.1.2.6 Posting of video content will be managed under the same principles as photography. Note that consent must be sought from all individuals visible and audible in the clip before posting. 

3.1.3 Writing
  • 3.1.3.1 Participants and friends are welcome and encouraged to submit original written work for posting to the CLASS profile and/or website. When submitting written material, the following must be included:
    • 3.1.3.1.1 Explicit, written permission from the submitter to post the photograph on the CLASS profile and/or website.
    • 3.1.3.1.2 FetLife-compatible formating (if desired)
    • 3.1.3.1.3 FetLife usernames for (as applicable):
      • 3.1.3.1.3.1 Submitter
      • 3.1.3.1.3.2 Author
      • 3.1.3.1.3.3 Any others with a creative interest in the writing
      • 3.1.3.1.3.4 For non-fiction accounts of CLASS events:
        • 3.1.3.1.3.4.1 All participants featured in the writing
        • 3.1.3.1.3.4.2 Event organiser
        • 3.1.3.1.3.4.3 Event host

3.1.3.2 If any of these individuals does not have a FetLife username, alternate contact information should be provided. Written permission (via email or PM) will be obtained by CLASS from each of these individuals prior to posting the writing. Additionally, any of these individuals may request for the writing to be removed at any time. CLASS will attempt to honour all requests for removal as soon as possible, typically within 24 hours.

3.1.3.3 All accepted writings will be uploaded as visible to all FetLifers and publicly posted to the website as applicable. CLASS will not transmit writings to a third party at any point in this process. However, those submitting and giving authorisation for the posting of writings are reminded that, once posted, CLASS is not able to guarantee that the writing will not be disseminated by third parties viewing the writing from the CLASS profile and/or website.

3.1.4 Tags

The CLASS profile may be tagged only in posts directly related to CLASS events (e.g. a participant’s writing about their experience at a CLASS event or a picture of the outfit a participant plans to wear to a CLASS event). Other attempts to tag the CLASS profile will be rejected. 

3.2 Conflict Resolution

3.2.1 It is understood that conflicts will arise between CLASS members.  Members of CLASS are encouraged to resolve issues among themselves, or to contact the appropriate authorities as necessary for serious issues.  

3.2.2 However, members may also contact any member of the BOT if assistance is required in resolving conflicts. 

3.2.2.1 If the conflict warrants discussion of potential exclusion, the BOT member receiving the report shall request permission to share the information provided with the rest of the BOT for discussion. The BOT shall additionally seek permission from the individual who raised the concern prior to approaching other individuals involved in the issue during the conflict resolution process. 

3.2.2.2 The BOT will endeavour to resolve the matter to the satisfaction of all parties where feasible, but the primary goal of the BOT will be to support the continuing function and harmony of the CLASS group.  

3.3 Public Relations

3.3.1 CLASS Ireland is an inclusive group for adults with an interest in school role play, and maintains a public website (class-ireland.com) to allow such individuals to discover the group. Any interested parties should be directed to our website. The contact page of the website provides a means to communicate with the group owner for further information. We ask that no content from this website be reproduced without prior written consent from the group owner.

3.3.2 While CLASS Ireland does not actively seek media coverage, members of the media (journalists, podcasters, etc.) seeking information on the group are asked to use the contact page of the website to contact the owner. The owner (or delegate) may give further general information about the group if requested as they feel appropriate, but will at no time reveal personal information about group members.

3.4 Personal Data

3.4.1 CLASS collects and maintains the minimum necessary personal data for the legitimate interests of the group. Personal data (such as CLASS attendance records) is recorded in CLASS records using an individual’s FetLife profile, or, for individuals who do not have a FetLife account,  by the email address used to contact CLASS. CLASS will not share the personal data it holds with third parties.

3.4.2 While individuals are encouraged to talk about their own direct experiences with CLASS if they choose, CLASS participants are asked to use suitable discretion with personal information to respect the privacy of other group members.

3.4.3 Individuals may request a copy of their personal data held by CLASS by sending a PM to the CLASS_Irl FetLife profile or by email to class.ireland@gmail.com from the account for which information is being requested.

4 Revisioning

4.1 This is a living document and will be updated periodically as described above. Latest update: 20 Jan 2025