Why most Remix consent banners do not work
Loaders run on every navigation, including the first server render. Analytics called from a loader or from root.tsx's default export reports the visit before any client-side consent state has been read from storage. A banner that renders after that has recorded a decision, not enforced one — and the enforcement is the part the ePrivacy Directive and the GDPR are actually about.
- ✓Poliogo's banner intercepts the tracking scripts rather than sitting beside them, so a tag that has not been consented to never executes.
- ✓Strictly necessary cookies — session, security, cart — are never held, so nothing about your product breaks while a visitor is deciding.
- ✓Every choice is written to a consent record with a timestamp and what was on screen at the time, which is the evidence a regulator asks for.
Installing it in Remix
Remix registers its routes in code rather than by filename, so no tool can add a page to it by writing a file and being confident it serves. Poliogo says so plainly and hands over the exact steps instead of opening a pull request that guesses at your router.
- ✓Rather than write a file that your routes() config might ignore, Poliogo gives you the module to add and the one line that mounts the banner in app/root.tsx.
- ✓React Router v7 projects are the same shape and the same steps — the framework was renamed, the routing question was not.
- ✓Everything downstream is unchanged: the scan, the drift pull requests against document content, and the hosted Trust Center all work exactly as they do on an automatic install.
remix.config.js identifies the project as Remix, and the scan reads your manifests and source the same way it does everywhere else — in memory, keeping only the service list.
Every service found, in plain English, with the evidence for each. Correct anything that is wrong before a word is generated.
The page (app/routes/privacy.tsx), the route line for your router, and the banner tag in app/root.tsx. Poliogo writes all three out for you — it will not guess at a router it cannot read.
Document updates still arrive as pull requests, because the documents are files. Only the initial wiring was yours.
What you get on a Remix project
The banner is one part of it. The scan underneath is what keeps the rest true.
It finds the trackers itself
AutomaticOne scan of your Remix project spots Google Analytics 4, Sentry, PostHog, Meta Pixel and around fifty more — and sorts each into strictly necessary, analytics or advertising without being told.
It holds them until people agree
Most banners record a choice and let the scripts run regardless. This one gates execution, which is the behaviour the ePrivacy Directive describes and the one an auditor can actually observe.
Policy pages, not just a banner
Privacy, cookie and terms pages written into your project — app/routes/privacy.tsx and its siblings — so they are yours, indexable, and styled by your own layout.
Geo-aware without a country list
European visitors get a consent gate, Californians an opt-out with Global Privacy Control honoured, Israeli visitors their own regime. GDPR is on every plan; CCPA and Israeli law from Starter.
It notices when you add something
DriftThe next scan of the repository is diffed against the snapshot your documents were generated from, so a new tag becomes an update you approve rather than a quiet inaccuracy.
Consent Mode v2 and TCF 2.3
Google Consent Mode v2 signals go out on every plan, so your ad reporting keeps modelling conversions for visitors who decline. IAB TCF 2.3, which many EU ad networks require, is included from Pro Builder.
Questions people ask
Will the banner slow down my Remix site?
No. The banner is a small async script that loads in the background and paints in one frame — it is not a framework, a UI library or a tag manager. Your Core Web Vitals do not move, which matters because for most sites the consent banner is the only third-party script on a page that has any reason to be there.
Does it actually block Google Analytics 4 before someone agrees?
Yes, and that is the difference worth paying attention to. Loaders run on every navigation, including the first server render. Analytics called from a loader or from root.tsx's default export reports the visit before any client-side consent state has been read from storage. Poliogo holds the non-essential scripts back until a visitor chooses, rather than asking politely while they run anyway — which is the part regulators look at.
Where does the privacy policy page end up in a Remix project?
At app/routes/privacy.tsx, which serves /privacy. It is a normal file in your project — your layout wraps it, your styles apply to it, and you can edit it afterwards like anything else in the repository.
Do I need to know which cookies my site sets?
No — that is the scan's job. It finds the tracking your project actually uses (Google Analytics 4, Sentry, PostHog and around fifty more), sorts each one into strictly necessary, analytics or advertising, and writes the cookie table for you. You confirm the list rather than compiling it.
Is this free?
The Free plan covers one project with a privacy policy, a cookie policy, the banner and unlimited manual re-scans — no credit card, and not a trial. Paid plans add Terms of Service, automatic background monitoring, more projects and the MCP server for Cursor and Claude Code.
What happens when I add a new tracker later?
The next scan of the repository sees it, updates the cookie classification and the policy text, and shows you exactly what changed in plain English before anything is published. On Free you run that scan whenever you like; paid plans watch for it in the background.
Put a working consent banner on your Remix site
Connect the project and see what the scan finds in under 60 seconds. Free plan, no credit card, and nothing is written or published until you approve it. Poliogo is a compliance management technology platform, not a law firm, and this page is not legal advice.
Start free — no credit cardPoliogo is an automated code analysis and document display tool, not a law firm. Poliogo does not provide legal advice, representation, or guarantees of statutory compliance, ADA/WCAG certification, or legal immunity. Visual banners and generated documents are advisory tools and do not substitute for professional legal review.