Event Management

Event teams hold three sensitive things at once. Attendee contact records, payment details and unannounced program content all sit in the same workspace. An assistant that drafts attendee messages touches every one of them in a single week.

The masking patterns match contract, agreement and statement of work reference numbers. They do not match card numbers, and no payment detection ships in this starter. Keep cardholder data out of prompts, and keep your payment flow inside the environment that PCI DSS v4.0.1 already covers.

Three phrases stop a request before it reaches the model: unreleased script, private key and rights agreement. A venue contract or an embargoed lineup pasted for summary is refused. Injection screening sits ahead of that block, so hidden wording in a pasted document cannot lift it.

Returned text must reach a combined 0.80, with accuracy at 0.80 and relevance at 0.78, and it must run past 120 characters and two sentences. Source checking records grounding and flags a weak result without stopping it. Someone still confirms a date, a price and an accessibility claim.

Consent for attendee contact, refund terms and venue obligations are handled in your registration platform. The review point is empty here, so no approval is enforced by the gateway. Audit marking shows that a request was evaluated and keeps nothing on its own.