// FAQ

Frequently Asked Questions

Plan the route and fallbacks, publish a public page or carefully configured form for each station, test its responder link while signed out, generate a labeled URL QR Code, and rehearse the complete hunt.

Response validation can reject answers that do not follow a rule, and a customized confirmation message can show after submission. These are separate settings and should be tested with realistic answer variants.

Not necessarily. Access depends on the form's publishing, audience, sign-in, response-limit, and email-collection settings. Test with a participant account and avoid requiring sign-in unless the activity genuinely needs it.

Provide an equivalent no-phone route, clear text instructions, labeled form fields, accessible locations, text alternatives and captions, sufficient contrast, and staffed help. Do not make scanning the only way to receive essential information.

Use supervised or controlled locations, event-branded cards, mounting that exposes overlays, a pre-event inspection, a master destination list, spare cards, and instructions to report unexpected domains, downloads, sign-ins, or payment requests.

They can be if you control the destinations. Use pages you built and tested, avoid collecting personal data, and consider printed clue cards for young children. In the US, COPPA protects children under 13 and treats photos and voice as personal information, so check with your school or organization first.

Keep a master list with each station's URL, answer, next clue and a spare card. Assign a monitor who can pause the hunt, replace a card and send a neutral bypass clue without revealing later answers. Inspect every station immediately before play and at set times during the hunt.

No. A code can be photographed, shared or scanned from elsewhere, and answers can be passed along. If a visit must be verified, use a staffed checkpoint or a task that needs the physical location, and design the hunt for fun and learning instead of strict anti-cheating.