Where does the snippet go in Framer?

In the Custom Code setting of your Framer project: paste the snippet into the field for the end of the head tag and publish the site.

Can I check my Framer site before changing anything?

Yes. Paste your published URL in the free check. It reads the live page, detects the trackers, payments and AI calls that really ship to visitors and lists the documents you need, with no signup.

Does my Framer site need a cookie banner?

It depends on what the site loads. If it uses analytics, advertising pixels or other non-essential trackers and has visitors in the EU or the UK, you need consent before those scripts run, and a banner that only shows a notice without holding the scripts back does not meet that. LexVibe's banner blocks them until the visitor accepts. If the site only uses storage that is strictly necessary, consent is not required, but your privacy policy should still say so.

What happens when I add analytics, payments or AI to my Framer site later?

The documents describe the site as it was when they were generated, so run the check again after adding an SDK. For apps linked to a LexVibe account, the check lists the processing your hosted documents do not cover yet and recommends regenerating them.

Privacy policy, terms and cookie banner for your Framer site

Framer designs and publishes the site, but the legal duties attach to whoever puts it in front of visitors. Privacy information, consent before non-essential trackers such as analytics or ad pixels and, if the site shows AI-generated content, an AI notice apply to whoever runs the site, whichever tool built it. LexVibe works out what your site needs, drafts the documents and gives you a cookie banner to drop in.

What your Framer site needs

The duties depend on what the site does, not on the tool that built it. These are the usual three:

A privacy policy as soon as the site collects personal data, even just sign-up emails. It has to say who is responsible, what is collected and why, and what rights people have. GDPR
Consent before non-essential cookies and trackers for visitors in the EU and the UK, and in several US states an opt-out that honours Global Privacy Control. ePrivacy · CCPA/CPRA
A clear notice when people interact with AI or see AI-generated content. The transparency duties of Article 50 apply from 2 August 2026. EU AI Act

Each law has its own page with its applicability threshold and a link to its official text, so you can check every claim.

Install LexVibe in Framer

In Framer, LexVibe goes in through the Custom Code setting: paste one line there and publish. If you would rather not touch the site yet, scan your published URL first.

Paste the snippet

1Open the Custom Code setting in your Framer project.
2Paste the snippet into the field for the end of the <head> tag.
3Publish the site.

The same line works on every platform:

<script src="https://golexvibe.com/v1/lexvibe-widget.js" data-lexvibe-app="YOUR_APP_ID" defer></script>

Create your app in the dashboard to get your own app id in place of YOUR_APP_ID. It is free to start.

Make the banner hold back your existing trackers

The banner can only hold back scripts it has been told about. For each analytics or advertising script already on the page, change its type to text/plain and add a data-lexvibe attribute with its category. It then runs only after the visitor accepts that category:

<script type="text/plain" data-lexvibe="analytics" src="https://example.com/analytics.js"></script>

The categories are preferences, analytics and marketing. Scripts left as they are keep running before consent. The free check lists the trackers it finds on your live site, so you know which ones to change.

What you get

Privacy policy and terms, hosted at a public URL and updated when regulations change.
A cookie banner that blocks non-essential scripts until the visitor accepts, honours Global Privacy Control and records consent.
An AI-content notice and an EU AI Act risk classification, if your site shows AI-generated content.
A cookie policy only when your site really uses non-essential trackers, so you never publish filler.

Common questions

Where does the snippet go in Framer?: In the Custom Code setting of your Framer project: paste the snippet into the field for the end of the head tag and publish the site.
Can I check my Framer site before changing anything?: Yes. Paste your published URL in the free check. It reads the live page, detects the trackers, payments and AI calls that really ship to visitors and lists the documents you need, with no signup.
Does my Framer site need a cookie banner?: It depends on what the site loads. If it uses analytics, advertising pixels or other non-essential trackers and has visitors in the EU or the UK, you need consent before those scripts run, and a banner that only shows a notice without holding the scripts back does not meet that. LexVibe's banner blocks them until the visitor accepts. If the site only uses storage that is strictly necessary, consent is not required, but your privacy policy should still say so.
What happens when I add analytics, payments or AI to my Framer site later?: The documents describe the site as it was when they were generated, so run the check again after adding an SDK. For apps linked to a LexVibe account, the check lists the processing your hosted documents do not cover yet and recommends regenerating them.

See what your Framer site is actually missing

Paste your URL. We fetch the live page, detect the trackers, payments and AI calls that really ship to visitors, and tell you which documents and consent you need. No signup.

No signup · result in seconds

More platforms and guides

This page is an engineering summary of publicly available regulatory requirements, generated from LexVibe's framework registry — not legal advice. Every framework links to its official text so you can check it yourself. For decisions about your own compliance posture, consult the primary sources and a lawyer qualified in the relevant jurisdiction.