Meetings in Action
Trust centre

Corporate event data deserves procurement-grade controls

Event managers hold client budgets, VIP guest lists, supplier banking details and signed contracts. This page sets out exactly how that information is protected inside the workspace, and what you stay in control of.

Access enforced in the database

Every table uses row-level security. Owner, editor and viewer roles are checked server-side, so hiding a button is never the only thing standing between a viewer and your data.

Activity trail on every event

Brief edits, RFQ dispatches, quote intake, approvals and budget changes are written to an append-only activity log — nobody can delete or rewrite history.

Encrypted, isolated storage

Data is held in a managed Postgres database with encryption in transit and at rest. Uploaded supporting documents live in access-controlled storage, not public links.

Portable by design

Budgets, payments, guest lists, schedules and reports export to Excel, accounting ledgers, calendar feeds and PDF. Your records never become hostage to the tool.

Built for multi-region teams

Multi-currency reporting, venue timezones, per-user date formats and six interface languages, so a team spread across regions reads the same event the same way.

Supplier compliance on file

Tax clearance, B-BBEE, insurance and COIDA expiry dates are tracked per supplier, with automated alerts before documents lapse.

Operating practices

  • Authentication is required for every workspace route — there is no anonymous access.
  • Invitations are explicit: a new email address has no access until an owner adds it.
  • Sensitive tables (guests, payments, budgets, suppliers, profile) are restricted to authenticated workspace members only.
  • Sending an RFQ records who sent it, to whom, and a snapshot of exactly what was sent.
  • AI assistance runs on your event data only and is never used to train third-party models.

Questions from your IT or risk team?

We answer security questionnaires and data-processing queries directly.

See also our privacy statement.