Skip to main content

Adding Terms and Conditions to your Dapple Submission Form

Here's how to setup your Terms and Conditions and why they are very important

Written by Oz Osbaldeston

Add Terms and Conditions to your submission form by inserting a Text or an Accordion field titled 'Terms and Conditions' followed by a Required Checkbox creators tick to confirm they've read and agree. The Accordion keeps the form clean; the Checkbox creates an auditable record of agreement. This is good legal hygiene for any project handling submitted work.

Why T&Cs matter for submissions

  • Legal protection — defines the rights and responsibilities of both parties.

  • Transparency — creators know how their data and work will be used before they submit.

  • Accountability — creators can't claim they didn't know the rules.

  • Compliance — helps you meet data protection laws like GDPR.

How to add Terms and Conditions

  1. Open the project → Form Builder.

  2. Click Add Item → Accordion or Text.

  3. Title the field 'Terms and Conditions'.

  4. Paste your full T&Cs into the body.

  5. Save.

  6. Add a Checkbox field below the Accordion. Label it 'I have read and agree to the Terms and Conditions'.

  7. Mark the Checkbox as Required.

  8. Click Save new version.

What should the T&Cs cover?

Section

What to include

Legal disclaimers

Liability, jurisdiction, dispute resolution.

Data usage and privacy

How you'll store and use creator data. Link to your privacy policy.

Responsibilities

What you commit to (e.g. review timelines, confidentiality) and what creators agree to (e.g. originality, rights to submit).

Rules for this specific project

Anything project-specific — e.g. AI use, multi-submission rules, exclusivity windows.

Rights and ownership

Who owns the work; rights granted to your organisation; what happens if work is selected vs not.

Best practice for T&Cs

  • Use plain language wherever possible. T&Cs creators can actually read are T&Cs that hold up.

  • Include a Last Updated date at the top so creators (and you) know which version they accepted.

  • Seek legal advice for project-specific clauses, especially around rights, licensing, and data handling.

  • Keep T&Cs and Submission Guidelines as separate fields — they serve different purposes. T&Cs are legal; guidelines are practical.

Where to go next

Did this answer your question?