You are not logged in. You do not need to log in to view and search the data

MDDB Data Policy

1. Purpose of the Database

This database exists to:
  • Store and publicly share non‑personal information about Morris dancing teams, including but not limited to:
    • Year of formation
    • Organisational affiliation
    • Dance style
    • List of dances, including creators and variations
  • Host and display photographs of morris teams.
The system is designed to promote the preservation and enjoyment of morris dancing heritage.

Name and email of team editors is stored but is only accessible by site administrators. No other personally identifiable information is collected or stored.

2. Types of Data Collected

2.1 Morris Team Information

The database stores the following non‑personal data:
  • Name
  • Web site
  • Location
  • Affiliation
  • Gender (dancers)
  • Style
  • Country
  • Own Tradition (for sides creating their own dances)
  • Year Founded
  • Ceased (year)
This information is publicly viewable by all users. In addition, the contact details and name of the editor for a side is stored but is not publicly viewable.

2.2 Photographic Content

Team editors may upload photographs relating to their own team. Database administrators and other users granted wider editorial access may upload photographs that relate to Morris teams, performances or associated cultural heritage. All photographs become publicly viewable once uploaded. Appropriate permission must be obtained before a photograph is uploaded.

3. User Responsibilities

3.1 Accuracy of Team Information

Only authenticated users with editor access may update team profiles. Editors are responsible for ensuring information is accurate, respectful, and relevant to their team. Editors must ensure that no personal data other than their own name and email is added to the database.

3.2 Permission to Upload Photographs

Before uploading, users must confirm that:
  • They own the copyright to the photograph or have explicit permission from the copyright holder.
  • The photograph does not infringe any third‑party rights.
Users must acknowledge these conditions via a clear acceptance checkbox or notice before upload.

4. Access Control

4.1 Public Access

Anyone may view all Morris team information and photographs without logging in.

4.2 Editor Access

Only authorised users with editor permissions may modify team information or upload photographs.

Editor access is granted by database administrators.

4.3 Administrative Access

Administrators have full access for:
  • Managing user permissions
  • Updating content for teams without editors
  • Removing inappropriate content
  • Maintaining system functionality

5. Data Protection and Privacy

5.1 No Personal Data

The database is intentionally designed to exclude the storage of any personal data.

Examples of prohibited data include:

  • Names of individuals
  • Contact details
  • Biographical information

5.2 Compliance with Applicable Law

Although no personal data is collected, the system adheres to best‑practice principles aligned with GDPR and general data protection standards, namely:
  • Lawfulness, fairness, and transparency
  • Purpose limitation
  • Data minimisation
  • Integrity and security

6. Copyright and Licensing

6.1 Photograph Licensing

By uploading photographs, users grant the database a non‑exclusive licence to:
  • Store
  • Display
  • Publicly share
the images for non‑commercial cultural and archival purposes.

Users retain full copyright to their images unless otherwise indicated.

6.2 Removal Requests

Team editors may remove photographs from their team's entry.

Any other user may request removal of photographs uploaded in violation of this policy.

Administrators will review and act on removal requests promptly.

7. Acceptable Use

Users must not upload:
  • Inappropriate, unlawful, or harmful content
  • Photographs without the proper permissions
  • Any material containing personal data or violating privacy
  • Content unrelated to Morris dancing
Administrators reserve the right to remove content or revoke access if this policy is breached.

8. Security

Data is stored securely and protected from unauthorised modification.

The system employs reasonable safeguards to maintain integrity and availability.

Because the database contains no PII, risk is minimal, but appropriate controls are maintained.

See also Security page for more technical details on security.

9. Changes to the Policy

This policy may be updated periodically to reflect:
  • Changes in legislation
  • Technical improvements
  • Adjustments to system design or usage
All updates will be posted clearly on the database.