Trust earned by design, not by claims

When attendees pay for a ticket, the card is processed — our regulated payment partner — and the funds settle directly in the organiser's merchant account. There is no Konecto wallet, no escrow, no platform balance.

This means Konecto cannot block, delay, or redirect ticket payments. The organiser receives the money the same way they receive any card payment from any source.

Only people who actually booked and paid for a ticket can leave a review. Reviews link back to a real booking row in the database — they cannot be created by anonymous visitors, by the organiser, or by Konecto staff.

This is the trust signal Konecto provides. Not a badge. A real attendee who showed up, with a real review.

Konecto does not independently verify that organisations are who they claim to be. Organiser type (school, public-sector, non-profit, business) is self-declared at signup.

We rely on attendee reviews and post-event reports to surface organiser quality, not pre-flight gatekeeping.

Each organiser's Pok merchant credentials (Merchant ID, Key ID, Key Secret) are encrypted with AES-256-GCM before being written to the database. The master key never reaches the browser, the build, or any logs.

A leaked database snapshot reveals zero usable Pok credentials. They're only ever decrypted in memory in the API/worker process for the duration of one Pok call.

Attendees can manage email preferences, opt out, and request data deletion through tokenised links — no Konecto login required.

Resend webhook events flip consent off automatically on bounce, complaint, or unsubscribe. We don't keep emailing people who told us to stop.

Pok credential changes, plan changes, team invitations, attendee exports, campaign publishes, organiser suspensions — all written to an audit log keyed on user + organisation, with IP hashes (not raw IPs) for forensic reconstruction.

You can review your organisation's full action history from the dashboard at any time.