Skip to document
Perka
All documentsContactBack to Perka
Drafts for review

These documents are not yet effective. Perka's trading details have been supplied; the contracting legal person and remaining privacy arrangements still need confirmation before final publication.

Organiser terms

Event publishing, visitor information, and organiser responsibilities.

Draft updated 28 October 2026 · No effective date

Version: perka-legal-draft-2026-10-28/organiser-terms

On this page

  1. Authority and service scope
  2. Event and content responsibilities
  3. Visitor information and exports
  4. Accounts, incidents, and support
  5. Fees, cancellation, and end of service
  6. Legal enquiries and agreement status

Authority and service scope

The organiser must have authority to manage the event and appoint users. Access is limited to assigned events and enabled modules. A completed order or agreement must identify the parties, event, service period, enabled features, fees if any, and applicable schedules.

The current app supports event content, vendor approval, maps, programmes, notices, registrations, and optional offers. Module availability is not a promise of ticketing, payment collection, marketing delivery, or future features.

Event and content responsibilities

The organiser is responsible for event operations, permissions, admission conditions, venue arrangements, accurate visitor information, vendor assignments, and timely changes or cancellation notices.

Only publish material you have authority to use. Review vendor submissions and promotions for accuracy and legality. The proposed content permission allows Perka and its service providers to host, reproduce, resize, and display supplied materials as needed to provide the event service; ownership stays with the rights holder.

Visitor information and exports

Use visitor information only for disclosed, lawful purposes. Restrict workspace and export access to authorised staff. Do not treat an all-registrations CSV as a marketing list or share visitor information with vendors without a justified, disclosed basis.

Secure downloaded files, restrict onward sharing, honour corrections/withdrawals, and delete or otherwise handle copies under the agreed retention schedule. The app does not remotely update or erase downloaded files. The organiser must have a process for withdrawals affecting earlier exports before using them for marketing.

The final agreement must identify each party's processing responsibilities and incorporate an applicable data-processing schedule. Merely describing a party as an operator does not settle every purpose.

  • Draft data-processing schedule

Accounts, incidents, and support

Use individual assigned accounts, protect credentials, and promptly request removal of departed staff. Report suspected unauthorised access, disclosures, or misdirected exports to the legal contact and relevant organiser lead without undue delay.

The final agreement must allocate incident assessment, notification and cooperation duties, request handling, and support channels. It must not promise a service level or response deadline that has not been agreed and staffed.

Fees, cancellation, and end of service

Perka sells digital software packages once off for one event edition or as annual subscriptions paid upfront with 6, 12 or 24 published editions per subscription year. New annual subscriptions renew yearly until cancelled. Existing monthly agreements retain their original terms. Active prices, included modules and capacity appear on Pricing and in checkout. All charges are in ZAR. Perka is not VAT registered and does not charge VAT. Purchase, refund and delivery conditions are shown with the total and require acknowledgement.

Agree how content, access, records, exports, and any return/deletion obligations are handled when an event ends or the relationship closes. An event end date does not currently delete its registrations automatically. Any suspension and liability clauses must preserve mandatory legal rights.

  • Purchase terms
  • Refunds and cancellations
  • Digital delivery

Legal enquiries and agreement status

Use legal@joinperka.com for contract or data-handling enquiries. Organisers accept these terms before using the workspace, and Perka records the account, terms version and time. Finalisation still requires the parties' particulars, completed schedules and legal review.

To complete before publication

  • Contracting entity, organiser particulars, effective date and signed order/scope. Organisers accept a versioned copy in the workspace; the version must change when the final text is published.
  • Final effective date, liability provisions and agreed data-processing schedule. Purchase policies describe the current billing and support arrangements.
Back to all legal documents
Perka legal documentsEvents · People · Experiences1 Kingfisher Drive, Randfontein, Gauteng, 1755, South Africalegal@joinperka.com