> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/global-sections/footer-group/age-verification.md).

# Age verification

Add an age gate in front of your storefront: a full-screen check with Accept and Decline buttons, your own imagery and wording, set up in the footer group.

If you sell alcohol, tobacco, vapes, or anything else with an age restriction, the **Age verification** section puts a full-screen check in front of the store. The visitor confirms their age before they can browse, and the answer is remembered in a cookie so they are not asked again on every page.

The gate is built from the same blocks as the rest of the theme, so it can carry your photography, your tone of voice, and your legal wording rather than a generic browser prompt.

***

### How to find it

{% stepper %}
{% step %}

#### Open the footer group

In the Theme Editor, scroll to the **Footer** group in the section list.
{% endstep %}

{% step %}

#### Add the section

Click **Add section** and choose **Age verification**. It is not in the theme by default — you add it once, and it then applies to the whole store.
{% endstep %}

{% step %}

#### Write the content

The section comes with a heading, a text block, and the verification buttons. Replace the placeholder wording with your own, then **Save**.
{% endstep %}
{% endstepper %}

***

### How it works

The gate opens as soon as the page loads, over a dimmed overlay, and the page behind it cannot be scrolled. It is deliberately hard to dismiss:

* there is no close button in the corner;
* the `Esc` key does nothing;
* clicking the overlay does not close it.

The only way in is the **accept** button. The **decline** button is a link — point it anywhere you like, usually a search engine or an informational page.

{% hint style="warning" %}
**The accept button has to have a label.** If **Accept button label** is left empty, no button is rendered — and since nothing else closes the gate, visitors are locked out of the store completely.
{% endhint %}

***

### How often it appears

**Frequency** decides how long the visitor's answer is remembered:

| Frequency         | The gate reappears         |
| ----------------- | -------------------------- |
| **No limit**      | On every page load         |
| **Once**          | Never again on that device |
| **Every 6 hours** | After 6 hours              |
| **Every day**     | After 24 hours             |
| **Every 3 days**  | After 72 hours             |
| **Every week**    | After 7 days               |

{% hint style="danger" %}
**The default is No limit.** Left as it is, the gate asks the same visitor on every single page they open. Set **Frequency** to **Once** — or to one of the interval options if your rules require re-checking — before you publish.
{% endhint %}

The answer is stored per browser, so a customer who switches devices or clears cookies is asked again.

***

### Blocks

| Block                    | What it adds                                                                                                        |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| **Verification buttons** | The accept and decline buttons. Set **Accept button label**, **Decline button label**, and **Decline button link**. |
| **Heading**              | The main line — "Are you 21 or older?"                                                                              |
| **Subheading**           | A short line above the heading, for the store name or a category.                                                   |
| **Text**                 | Rich text for the legal wording or a link to your terms.                                                            |
| **Image**                | A standalone image inside the panel.                                                                                |
| **Context image**        | An image with its own width and ratio.                                                                              |
| **Line**                 | A divider between blocks.                                                                                           |
| **Empty space**          | Extra spacing between blocks.                                                                                       |
| **Custom Liquid**        | Your own Liquid, HTML, or an app snippet.                                                                           |

The section starts with a heading, a text block, and the verification buttons. The default labels are **I am over 21** and **I am under 21** — change them to the age that applies in the markets you sell to.

{% hint style="info" %}
A decline button with no link set is rendered greyed out and does nothing. Either give it a destination or remove the label so the gate shows a single button.
{% endhint %}

***

### Design

**Image** and **Mobile image** let the gate carry a photograph. The mobile image replaces the desktop one on small screens, so a wide lifestyle shot can become a portrait crop on a phone.

**Center text** aligns the content in the middle of the panel.

**Fill content** controls the panel itself. With it on, the content sits on the section's background colour; turn it off and the panel becomes transparent, so the content floats directly on the overlay.

**Overlay color**, **Overlay gradient**, and **Overlay opacity** style the dimmed layer behind the gate. The opacity starts at 70%, which keeps the storefront recognisable without competing with the question.

**Color scheme** switches the panel between the default and inverted palettes, or a custom combination of background colour, gradient, and text colour.

***

### Good to know

**The gate does not open on its own inside the theme editor.** To preview it, select the Age verification section in the section list — it appears while the section is selected and closes when you select something else. Any answer you give in the editor is not remembered, so it keeps appearing for you while you work on it.

**It applies to the whole store.** Unlike [Popup](https://staylime.com/docs/avante-themes/global-sections/footer-group/popup.md), the Age verification section has no home-page-only option and no delay or scroll trigger. It is all pages, immediately, by design.

**An age gate is not a substitute for legal advice.** The theme gives you the mechanism; which ages, which wording, and which markets require it are decisions for you and your legal adviser.

***

### Customization ideas

**Match the gate to the brand.** A full-bleed product photo with the panel transparent — **Fill content** off — reads as part of the store rather than a browser alert.

**Send decliners somewhere useful.** Point the decline link at a page explaining your policy instead of a search engine, so the visitor understands why they were turned away.

**Add the legal line as a Text block.** Keep the heading to the question itself and move the regulatory wording underneath, where it does not compete with the buttons.

***

### Related

* [Popup](https://staylime.com/docs/avante-themes/global-sections/footer-group/popup.md)
* [Flyout](https://staylime.com/docs/avante-themes/global-sections/footer-group/flyout.md)
* [Footer](https://staylime.com/docs/avante-themes/global-sections/footer-group/footer.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/global-sections/footer-group/age-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
