Add an acknowledgement gate before a QR destination
Ask scanners to confirm 18+, 21+, terms, a content warning, a disclaimer, or your own message before an eligible dynamic QR opens its destination.
Selected QR Code Type
QRLynx Access Consent adds an acknowledgement screen before an eligible dynamic QR destination. It includes built-in 18+ and 21+ confirmations, sensitive-content and terms messages, confidential, medical, and financial disclaimers, plus custom per-QR wording. Custom mode can set the title, message, continue-button label, icon, and optional report-link label. Access Consent is included with Pro, Business, and Enterprise.
The visitor actively chooses the continue button before the destination opens. The current screen then remembers that acknowledgement for 30 days on that browser and QR. This is self-confirmation, not an identity, date-of-birth, or legal-age check. QRLynx does not record an acceptance or rejection audit trail, so use a dedicated verification or consent-record system when your policy or law requires stronger proof.
What you can control on the acknowledgement screen
Choose a ready-made message or write a concise gate for one QR code.
18+ and 21+ Confirmations
Show a preset that asks the visitor to confirm they meet the stated age before continuing.
Sensitive Content Warning
Place a clear viewer-discretion message before material that some scanners may prefer not to open.
Terms Link and Agreement
Show the terms preset and, when configured, give visitors a separate link to read the terms before continuing.
Built-in Disclaimers
Choose confidential, medical, or financial wording as a starting point, then confirm that it fits your own use and jurisdiction.
Custom Per-QR Wording
Set a title, message, continue-button label, icon style, and optional report-link label for one saved QR.
Edit Without Reprinting
Change the configured gate on the saved dynamic QR while the printed code continues to use the same managed route.
Choose the gate that matches the job
Access Consent asks for an acknowledgement. Other controls solve different access and data-collection needs.
| Need | QRLynx option | What the visitor does |
|---|---|---|
| Acknowledge an age statement, warning, terms, or disclaimer | Access Consent | Reads the message and chooses one continue button |
| Enter a shared secret before the destination opens | Password Protection | Provides the password defined by the QR owner |
| Submit contact details before continuing | Lead Form | Completes the fields selected by the QR owner |
| Prove identity, birth date, or eligibility | Destination verification system | Completes the verification required by the destination provider |
How to add Access Consent in QRLynx
Build the dynamic QR, configure its message, and test the complete visitor path before printing.
Choose an eligible dynamic QR type
Sign in to QRLynx and begin a standard dynamic-capable QR. Access Consent is not available for GS1 Digital Link or directly encoded static payloads.
Add the destination or hosted content
Complete the selected QR type and confirm that the final destination has any authentication, privacy, or legal controls it needs independently of the QR gate.
Open Access Consent
Open the generator settings and choose Access Consent. If the account does not include the feature, review the Pro plan or a higher plan.
Choose a preset or write your own
Select 18+, 21+, sensitive content, terms, confidential, medical, financial, or Custom. Custom mode lets you set the title, message, button label, icon, and optional report-link label.
Review the exact visitor wording
Keep the message direct and accurate. For the terms preset, add the destination where visitors can read the applicable terms.
Save and test the QR
Save the dynamic QR, scan the downloaded file, confirm the acknowledgement screen appears, open any terms link, and verify that the continue button reaches the intended destination.
Edit the gate when the message changes
Open the saved QR or Account Access Consent, update the configuration, save, and scan the existing printed code again to verify the new flow.
Message and destination ready
Create the dynamic QR, then add its acknowledgement gate
Build the destination first, choose Access Consent in the QR settings, and test the gate on a phone before printing.
An acknowledgement is different from verification
The QRLynx screen records no identity document, birth date, signature, or per-visitor acceptance entry. It also cannot prevent someone who already has the direct destination URL from opening that destination. Use the destination's own verification, authentication, and recordkeeping when those controls are required.
Practical uses for an acknowledgement gate
Use the gate to set an expectation before opening, while keeping any required verification at the destination.
Age-Related Campaign Notice
Ask a visitor to self-confirm 18+ or 21+ before opening a campaign page, with the destination responsible for any stronger age check.
Content Warning
Give scanners a clear warning before opening a video, image collection, report, or story with sensitive material.
Terms Acknowledgement
Present a short terms message and link to the full terms before the visitor chooses to continue.
Educational Disclaimer
Set expectations before informational medical or financial material without presenting the gate as professional advice or verified consent.
Confidentiality Reminder
Remind an intended audience that the destination is confidential, while relying on real destination permissions for access control.
Custom Campaign Notice
Write a campaign-specific message when none of the built-in presets describes the visitor decision clearly enough.
Behavior and limits to know before launch
These boundaries affect testing, reporting, and the visitor experience.
| Area | Current behavior | Planning note |
|---|---|---|
| Plan access | Pro at $14 per month, Business, and Enterprise | Pro includes 300 active dynamic QR codes and all plans keep unlimited scans |
| Visitor decision | One continue action | There is no separate decline button or decline destination |
| Remembered acknowledgement | A per-QR browser cookie is stored for 30 days after continuing | A different browser, device, or QR requires its own acknowledgement |
| Consent records | No acceptance or rejection log | Use a dedicated recordkeeping system when evidence of consent is required |
| QR analytics | Standard QR scan analytics are separate from consent records | Do not use scan totals as proof that a specific person accepted a message |
| Search indexing | The QRLynx acknowledgement page is noindex and nofollow | The destination follows its own indexing settings and remains reachable by its direct URL |
| QR compatibility | Eligible standard dynamic QR flows such as Website or PDF | GS1 Digital Link and directly encoded static payloads do not use Access Consent |
QRLynx Access Consent questions
Answers about setup, visitor behavior, editing, and the feature boundary.
Can QRLynx add an 18+ or 21+ age gate to a QR code?
Yes. On Pro, Business, and Enterprise, Access Consent can show a built-in 18+ or 21+ self-confirmation screen before an eligible dynamic QR destination opens. The visitor chooses the continue button to confirm the statement. The screen does not inspect identity documents, date of birth, or actual age.
Is the QRLynx age gate the same as age verification?
No. It is a self-attestation gate. It asks the scanner to confirm an age statement but does not verify identity or age. Connect the destination to a suitable age-verification provider when verified proof is required.
Which Access Consent messages are available?
QRLynx includes presets for age 18+, age 21+, sensitive content, terms and conditions, confidential material, a medical disclaimer, and a financial disclaimer. Custom mode lets the QR owner set the title, message, continue-button label, icon style, and optional report-link label.
Can I link to the full terms from the acknowledgement screen?
Yes. The terms preset can show a separate Read Terms & Conditions link when a terms URL is configured. Test that link and the continue action before distributing the QR.
Does Access Consent record who accepted?
No. QRLynx does not collect an identity, signature, or per-visitor acceptance and rejection record from this screen. Use a dedicated consent or verification system at the destination when your workflow needs that evidence.
What happens if a visitor does not want to continue?
The current acknowledgement screen presents one continue button. A visitor who does not agree can close or leave the page. There is no configurable decline button or fallback destination.
How long does QRLynx remember the acknowledgement?
After the visitor continues, the current QRLynx screen stores a browser cookie for that QR for 30 days. The acknowledgement is not shared with a different browser, device, or QR code.
Can I change the message without reprinting the QR?
Yes. Edit the saved dynamic QR or open Account Access Consent, update the gate, save it, and test the existing printed code. The printed QR continues to use the same managed route.
Can Access Consent protect a destination that someone opens directly?
No. The gate controls the QRLynx QR route. Someone who already knows the destination URL can follow that URL directly, so confidential or restricted content still needs its own authentication and permissions.
Does Access Consent work with every QR type?
It works with eligible standard QR types saved through the QRLynx dynamic route. It is not available for GS1 Digital Link or directly encoded static payloads such as WiFi credentials.
Does Access Consent block search engine crawlers?
The QRLynx acknowledgement page itself uses noindex and nofollow. That setting does not hide or deindex the separate destination page, which follows its own indexing controls and remains reachable through its direct URL.