About this block

Cookie Consent Bar renders as a card band with two sentences of exact scope: "We set a cart cookie and a session cookie, nothing else. No ad pixels, no cross site anything." Accept and Decline share equal visual weight as paired outline buttons. The closing line, "Declining changes nothing about how the site works, which is the point," is the entire argument for parity.

No data array needed. Equal button weight is the design decision: making Decline obviously available removes the suspicion that consent UI is designed to extract a yes, which is the suspicion that makes users distrust the store.

When to use

Reach for this block as a bottom bar on first visit across all pages, below the store footer. Wire Accept and Decline to real consent state; the copy promise ("nothing else") must match the actual cookies set.

A natural flow around it on an Ecommerce Pro page:

Before

• Store footer

After

• Trust section
• Contact section

What you can display

One strong use is the two cookie, zero tracking store. Other consent configurations:

• Analytics enabled. One additional sentence naming the provider and the aggregate only scope.
• Preferences cookie. The locale and currency remembering, named, no behavioral profiling.
• Returning visitor. Remind only, the full disclosure linked, not repeated in the band.

Tip: naming what you do not track ("no cross site anything") persuades more effectively than listing what you do, because the absence is what buyers fear most.