LexVibe

Privacy policy, terms and cookie banner for your Base44 app

Base44 builds the app, but publishing it makes you answerable for what it does with visitors' data. Privacy information, consent before non-essential trackers and, if the app shows AI-generated content, an AI notice apply to whoever runs the app, whichever tool wrote the code. LexVibe works out what your app needs, drafts the documents and gives you a cookie banner to drop in.

What your Base44 app needs

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

  • A privacy policy as soon as the app 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 Base44

In Base44, LexVibe works through a single prompt: paste it in the chat and the assistant scans the project and asks for the three facts it cannot infer, then sends you to the free check to finish the setup and adds the snippet. You can also paste the snippet yourself in the app settings.

Paste one prompt in Base44

  1. 1Paste this line in the Base44 chat.
  2. 2The assistant fetches LexVibe's instructions, scans your project for what the code shows and asks only for what it cannot know: the owner, a contact email and your target markets.
  3. 3It sends you to the free check, which pre-fills what it detected and finishes the setup in three steps. Your app id comes from your own dashboard.
  4. 4Back in the chat, the assistant adds the one-line snippet with that id. Publish, then check the live site.
Read https://golexvibe.com/prompt and follow it to make this app legally compliant (privacy policy, terms, cookie banner, EU AI Act).

Or paste the snippet yourself

  1. 1Open your app settings in Base44.
  2. 2Look for «Custom code» or «<head> scripts» and paste the snippet.
  3. 3Save and publish.

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 app 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 a Base44 app?
Open your app settings in Base44 and look for Custom code or head scripts, paste the snippet, then save and publish. Those are the same three steps the LexVibe dashboard shows for Base44.
Can the assistant in Base44 do this for me?
Partly. Paste the one-line prompt and the assistant fetches LexVibe's instructions, discovers what it can from the code and asks only for the owner, a contact email and your target markets. It then sends you to the free check to finish the setup, and once you have your app id from the dashboard it adds the snippet to the project.
Does my Base44 app need a cookie banner?
It depends on what the app 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 app 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 Base44 app later?
The documents describe the app 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 Base44 app 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.