Consent, Handled
Every message to a guest has to clear a wall of rules — texts and email each have their own, they change by country, and a deletion request overrides all of them. Guestcount folds it into one automatic check. Set a guest's situation and watch the layer decide.
Try it — toggle what the guest chose, watch the layer react
Behind each check sits the real rule — TCPA for texts, CAN-SPAM for email, plus GDPR & UK, right to be forgotten, carrier and opt-out law. You never see it fire.
Every consent event writes one immutable row — the receipt behind every send. This is what an auditor, or your lawyer, sees.
What We Handle
An invite only goes out on a channel the guest opted into. Text consent and email consent are tracked separately — a STOP on texts never touches their email.
Email is opt-in in the EU and UK, opt-out in the US, and Canada's CASL is stricter still. Texts need an opt-in everywhere. The layer applies the right standard for wherever each guest is — and defaults to the strictest when it isn't sure.
When a guest asks to be deleted, their data is purged and every channel goes dark at once — no message, no recognition, nothing recoverable. It overrides every other rule.
Reply STOP, QUIT, UNSUBSCRIBE — any reasonable word — and that channel goes quiet across every one of your events, instantly and automatically.
A confirmation the guest is waiting for and a marketing blast are held to different rules. The layer tells them apart so the strict rules only bind where they should.
One brand's guests are never shared with another — on any plan. Comparisons only ever use de-identified, aggregated numbers that point to no one.
What You Do
Send the invite. The layer picks a channel they opted into.
Confirmations, reminders, day-of changes. Cleared automatically.
Recognize returning guests, use your own audience. Handled.
That's the entire list. Everything else happens before anything leaves the building — you never configure a rule, read a regulation, or track down a consent record.
This page explains how Guestcount's consent layer works. It isn't the legal agreement itself, and specific rules are set with counsel. The point it makes is simple: the safest thing you can do with guest messaging is nothing extra — because it's already built in.