Skip to content

Consents and terms — prepare your event documents

Prepare the privacy policy, terms and marketing consent, publish the right version and check who accepted what.

Hi Events editorial team27 October 2026 · 6 min read

In Consents you prepare the documents a person sees when signing up for your event. You write the content, save a draft, publish a version and then check who accepted what.

Step 1. Open the documents

Go to Admin → Consents in your event. The Event documents and consent screen has five documents. Each has its own draft, published version and history.

DocumentWhat it's for
Event privacy policyInforms about data processing. It's information, not consent.
Event termsRules for attending. A person accepts them when signing up.
Reception staff termsFor people who take on a reception staff role.
Ticket sales termsShown when buying a paid ticket.
Marketing consentAn optional choice. Declining doesn't prevent attendance.

The panel currently marks documents as test documents. Before a real event, prepare content that fits your event.

Leadership Forum 2026 documents and consent: five document types with separate publication states. The visible content and publications are test documents.
Leadership Forum 2026 documents and consent: five document types with separate publication states. The visible content and publications are test documents.

Step 2. Write the content and save a draft

Expand a document. Fill in the fields:

FieldRules
Document title2–160 characters. A name people will recognise next to the link.
Organizer sectionOptional, up to 20,000 characters. Shown above the fixed Hi Events section.
Message beside the document3–1,000 characters. Depending on the document, the field is called Information text, Terms acceptance text or Optional consent text.

Click Save draft. A draft is a working version. People still see the previous published version.

The privacy policy editor: title, organizer section and information text. The fixed Hi Events section is read only and contains test content.
The privacy policy editor: title, organizer section and information text. The fixed Hi Events section is read only and contains test content.
Event terms have a saved draft and a separate acceptance message. Save draft and Publish new version are two successive actions.
Event terms have a saved draft and a separate acceptance message. Save draft and Publish new version are two successive actions.

Step 3. Check the full preview

Click Full document preview. You'll see everything: the title, the data controller's details, your section, the Hi Events section and the message.

The controller's details (name, tax ID, KRS, address, e-mail) come from the organization profile. Missing fields are marked Not provided. Click Complete in the organization profile to add them.

Important:

  • On publication, the organization details are saved in that version. Changing the profile later won't fix old versions. Publish a new one.
  • A document has its own language, currently Polish. Switching the app to English doesn't translate its content.
The full preview shows Good Meetings Foundation with fictional demo details, including all-zero NIP and KRS, and a PL badge. This demonstrates the feature; it is not a legal document template.
The full preview shows Good Meetings Foundation with fictional demo details, including all-zero NIP and KRS, and a PL badge. This demonstrates the feature; it is not a legal document template.

Step 4. Publish a new version

Click Publish new version. In the Publish test version window, answer Who should the new version apply to?:

  • Only new people in the relevant process — the new version reaches only new people.
  • The second option depends on the document, e.g. Ask existing participants to accept again for the event terms or Also inform existing participants for the privacy policy.

Hi Events assigns the version number.

Publishing a document:

  • doesn't publish the event,
  • doesn't send any messages,
  • doesn't record anyone's acceptance.
The event terms publication window: only new people, or asking existing participants to accept again. The choice shown here has not yet been confirmed as a publication.
The event terms publication window: only new people, or asking existing participants to accept again. The choice shown here has not yet been confirmed as a publication.

Step 5. Check the history and acceptances

What was published? In the document, open Version history and click Open version. You'll see the content, the controller's details on the publication date, the author and the date.

What did a specific person accept? Go to Admin → Participants, open the person's card and the Consents and documents section. You'll see e.g. "terms version 1 accepted" and "privacy policy version 1 shown".

  • Showing the privacy policy doesn't mean someone read it.
  • A new version doesn't change old acceptances.
The local demo history shows test versions 2 and 1. An opened version keeps the text and data controller details recorded at publication.
The local demo history shows test versions 2 and 1. An opened version keeps the text and data controller details recorded at publication.
Anna Zielińska in the fictional demo: event terms version 1 accepted and privacy policy version 1 shown on 16 October 2026. Later test publications do not rewrite these records.
Anna Zielińska in the fictional demo: event terms version 1 accepted and privacy policy version 1 shown on 16 October 2026. Later test publications do not rewrite these records.

Step 6. See sign-up as a participant

Go through the sign-up form as a new person. Check that:

  • The terms acceptance box is empty. The person ticks it themselves.
  • The links to the terms and privacy policy open the right documents.
  • If a document changes while the form is being filled in, the person sees the new version and decides again.
Ola Nowak’s complete free registration form from the Registration guide: personal and company details, terms, privacy information and a separate profile visibility choice. The screenshot was taken before collecting the ticket.
Ola Nowak’s complete free registration form from the Registration guide: personal and company details, terms, privacy information and a separate profile visibility choice. The screenshot was taken before collecting the ticket.

Step 7. Changing a document for existing people

If you choose existing people for the privacy policy or event terms, they'll see a notice about new documents in the app.

  • The terms are accepted by the person.
  • The privacy policy is only shown.
  • Remind me later postpones it. The reminder doesn't block access to the event.

This isn't an e-mail. If you want to write to people about the change, prepare a message in Emails.

The privacy policy publication dialog includes Also inform existing participants. This shows the choice before confirmation, rather than a participant’s reminder; this publication was not confirmed.
The privacy policy publication dialog includes Also inform existing participants. This shows the choice before confirmation, rather than a participant’s reminder; this publication was not confirmed.

When documents are required

ActionRequired published documents
Inviting a speaker or company managerPrivacy policy and event terms
Free sign-upPrivacy policy and event terms
Paid ticketTicket sales terms as well

A saved draft isn't enough. The document must be published.

Event documents are separate from the Hi Events terms you accept when creating your account.

The Ticket sales terms editor in Consents. This screenshot shows document preparation, not a payment step or a confirmed purchase.
The Ticket sales terms editor in Consents. This screenshot shows document preparation, not a payment step or a confirmed purchase.

Marketing is a separate matter

  • Marketing consent is optional. Declining doesn't prevent attendance.
  • Signing up, buying a ticket or publishing a document doesn't sign anyone up for marketing.
  • Messages from the organizer and messages from Hi Events are two separate choices.
  • Mailings from Emails reach only people who can receive them. A group may have more people than the number of e-mails sent.
  • A new version of the marketing document doesn't carry old consent over to the new terms.
The Marketing consent editor shows the optional choice text and explains that publication does not create consent. This prepares a document; it is not a message subscription form.
The Marketing consent editor shows the optional choice text and explains that publication does not create consent. This prepares a document; it is not a message subscription form.

What accepting a Hi Events offer does

Accepting an offer saves the data controller details in the organization profile. For events in the offer, it prepares and publishes the privacy policy and event terms from templates; a marketing document is included only where you enable Collect. Existing published documents are not replaced. Open each event afterwards to check the versions and complete text.

Collect prepares a voluntary choice for participants. It does not consent on their behalf or subscribe you to Hi Events messages.

Limits to keep in mind

  • This module still publishes test documents in Polish. The event's second content language does not translate them.
  • Publishing reception terms does not activate reception or staff invitations.
  • For a paid order, the buyer's document evidence is recorded after successful test payment. Entering another person's details does not prove that person's own acceptance.
  • Marketing requires a separate voluntary subscription. An unconfirmed address needs confirmation; opening the link alone does not complete it. Someone signed in with their own confirmed address can complete it immediately.

Before you open sign-up

  • The chosen documents have complete, checked content.
  • The controller's details in the organization profile are filled in.
  • The needed versions are published.
  • The new-person form shows the right links.
  • Your team knows where to check history and acceptances.

Frequently asked questions

Is Save draft enough for participants to see the corrected terms?

No. Click Publish new version and choose who it applies to.

Does a published document mean everyone accepted it?

No. Acceptance exists only when a specific person ticks it.

Will the English version of the app translate the terms?

No. A document has its own language, currently Polish.

Will changing the organization details fix old versions?

No. Publish a new version with the new details.

What if a save or publication isn't confirmed?

Click Retry saving draft or Retry the same publication. Don't start a new publication straight away.

Why can a participant postpone accepting again?

The reminder doesn't block attendance. Remind me later doesn't record acceptance.

Your community
starts with a meetup.

Join the beta and get your first event free

  • 1
    Sign up for the beta

    Leave your details in a short form and join the waiting list.

  • 2
    Get your invitation

    We'll let you know when we open Hi Events for you.

  • 3
    Build your first event

    Once you have access, you'll prepare your event website and explore what the platform can do.

Join the beta

Leave your details and join the waiting list. We'll get in touch when we open access for you.

Hi Events Terms (PL). Information about processing your data: Hi Events Privacy Policy (PL).

I have an account — sign in