Your website
privacy workspace.

Your privacy work.
One console.

Banner, cookies, visitor choices and privacy requests for every site on your plan, all in one place. The overview shows what changed and what needs you.

Screens from the Velo console, shown with an example site and illustrative data.

How it works,
screen by screen.

From the first install to the last privacy request, here is what you do in Velo and where you do it.

01 · Set up

Live in four steps

Add your website, install Velo with one snippet or through Google Tag Manager, check the connection and run your first scan. Your progress is saved, so you can stop and pick up where you left off.

• A default banner shows the moment Velo is installed
• The connection check confirms Velo is reporting from your site
• Consent Mode v2 signals passed to supported Google tags
• Google may model gaps in eligible accounts; Velo sends the signals

02 · Banner

Design the banner your visitors see

Pick a theme or set your own colours, write the copy in the languages you need and choose what visitors can switch on. The preview shows the banner the way a visitor sees it.

• Ready made themes or your own colours
• Copy, languages, preferences and the privacy button in one editor
• Preview on desktop and mobile, in each language
• Free keeps Velo branding; Pro adds custom branding and logo controls

03 · Scanner

Know every cookie on your site

The scanner visits your site as a real visitor would, before and after accepting cookies, and lists every cookie and script it finds. Unknown cookies can come with a suggested category, and nothing changes until you accept it.

• Cookies, scripts and localStorage keys, with the pages they were found on
• Suggested categories for unknown cookies, applied only when you accept
• Findings that flag what needs your attention
• On Pro, a monthly automatic rescan keeps the list current

04 · Regions

The right defaults in every region

Velo reads each visitor’s country and applies the matching consent defaults. Where the law requires opt in, it stays locked on. Where you have a choice, you make it.

• Opt in across the EEA, the UK and Switzerland, and in Brazil, Peru, Colombia and Argentina
• Opt out in the US, with Global Privacy Control signals honoured automatically
• An optional “Do not sell or share my personal information” label for California
• Country overrides wherever the law leaves the choice to you

05 · Analytics

See how visitors answer

Follow how many visitors accept, reject or customise their choice, how that moves over time and where they are. Every figure is compared with the previous period.

• Accept, reject, customised and GPC refusal rates
• Choices over time and by country
• A consent breakdown by category
• Export the numbers as CSV

06 · Records

Proof of every choice

Every decision is logged with a receipt ID, the time, the region, the categories allowed and the banner version the visitor saw. Look up a single receipt when someone asks.

• Search any decision by its receipt ID
• Choice, region, categories and GPC status on every record
• Export records as CSV

07 · Requests

Answer privacy requests on time

Access, deletion and consent withdrawal requests sit in one queue, each with a reply by date 30 days after it arrived. Velo warns you a week before a request is due and flags anything overdue.

• Open, due soon, overdue and closed views
• Filter by request type and site
• Track each request from open to resolved

Start with a scan.

See what your homepage already loads before you install anything. This is the kind of result the free scanner hands back.

Worth a closer look

A consent layer is there. Now verify it holds

A consent platform loads alongside 3 tracking tags from the Tag Manager container. The question no static scan can answer: do those tags wait for the visitor’s choice?

studio.example

Checks passed

2/4

Static checks on the first response

Tracking tags

3

In the page and Tag Manager

Consent platform

Detected

Present in the load

Cookies on first response

1

Any kind, set by the server

What we checked

Homepage HTML and public Tag Manager container

Tracking technology

3 tracking tags found inside Google Tag Manager. In the EEA and the UK these need consent.

Check in a browser

Consent platform

Found in the Tag Manager container. A banner alone is not enough. It has to hold tags back until the visitor chooses.

Pass

Google Consent Mode v2

Google tags are present. Whether the Consent Mode default fires before them is what a real browser check settles.

Check in a browser

Cookies before consent

No tracking cookies were set by the server on the first response.

Pass

Tags we found

GTM-XXXXXXX

G

Google Tag Manager

In the page HTML

Tag management

Google Analytics 4

Inside Tag Manager

Analytics

G

Google Ads

Inside Tag Manager

Advertising

Meta Pixel

Inside Tag Manager

Advertising

Sample result with illustrative data. The scanner reads your homepage HTML and public Tag Manager container without running JavaScript.

Works with
your platform.

Velo works on any site where you can add one line to the page head or one tag in Google Tag Manager. Pick your platform to see how Velo fits it and how to install it.

Switching from another consent platform? Compare Velo with Cookiebot, CookieYes, OneTrust or Usercentrics.

From the journal.