Privacy
notice.

This notice explains how Velo and AmplioData OÜ handle personal data on this website, in the Velo console and inside the Velo product when it runs on a customer site. It is written in plain language and is not a substitute for the full terms.

1. Who we are

Velo is a consent management product built and operated by AmplioData OÜ, a company registered in Estonia under Business Register code 17190588, with its registered office at Sepapaja tn 6, 15551 Tallinn, Estonia, and VAT number EE102836994. We work from Barcelona, Spain. When this notice says "we", it means AmplioData OÜ. Our full identification is set out in the legal notice. You can reach us about anything on this page at support@veloconsent.com.

2. Two different roles

It matters which side of Velo you are on.

When you browse this website or use the Velo console

AmplioData OÜ is the controller of the data described in sections 3, 4 and 5, and this notice covers it.

When Velo runs on a customer's website

The website owner is the controller. Velo acts as a processor on their behalf, handling consent records under their instructions. Those visitors should read the privacy notice of the site they are visiting. Our obligations in that role are set out on the GDPR and data processing page.

3. What we collect on this website

• Your consent choice. When you answer the cookie banner, we keep your choice, a coarse region read at the edge and a timestamp, so we can honour what you asked for and show later what you chose. Your browser keeps the choice in a cookie for up to a year and in browser storage until you clear it.
• Delivering and protecting the site. Cloudflare, which hosts this site, handles your IP address and browser details to deliver pages and to block abuse.
• Visits from our ads. When you arrive through one of our ads, our server counts the visit without cookies. It records the page, the campaign tags in the link, your country, your type of device, whether the visitor is a known crawler, which kind of ad click ID the link carried (never the ID itself) and a rough referrer. It stores no IP address, no browser details and no identifier, and it reads nothing from your device and stores nothing on it.
• Analytics, depending on your choice. Google Analytics 4 and PostHog show us how the site is used. See section 4.
• Advertising, depending on your choice. Google Ads tells us which campaigns bring visitors and sign ups, and lets us show our ads again to people who visited. See section 4.
• Things you send us. If you email us, or use the contact form, which opens your own email app, we receive what you choose to share, such as your name, work email and message. If you run a free scan, we fetch the site you name to show you the result.

We host the fonts, images and scripts this site uses ourselves. Google Analytics and PostHog reach this site through our own domain, and our server passes their data on only as section 4 describes.

4. Analytics and advertising on this website

These tools only use your data for the categories allowed in the banner. In the EU, the EEA, the UK, Switzerland, Brazil, Peru, Colombia and Argentina, nothing is allowed until you choose. Elsewhere analytics and advertising are on by default: you can switch them off at any time from the cookie button, and a Global Privacy Control signal from your browser turns advertising off. The banner tells Google's tags the result through Google Consent Mode v2.

• Google Analytics 4 (analytics). Measures visits, pages, scans and sign ups, through our own address (veloconsent.com/m) before it reaches Google. If you allow analytics, it sets cookies, our server sets a first party ID that Google Analytics uses to recognise you on your next visit, and our server passes your IP address to Google so it can work out your approximate location. If you do not, Google still receives cookieless pings that tell it your choice and let it estimate totals. They set no cookie, use no lasting ID, and our server forwards them without your IP address.
• Google Ads (advertising). Google Analytics shares conversions, such as sign ups and scans, and lists of past visitors with our Google Ads account. We use them to measure our campaigns and to show our ads again to people who visited. Google Signals is on, so for visitors signed in to a Google account with ad personalisation turned on, Google can link visits across devices in its reports. All of this only uses your data if you allow advertising.
• Enhanced conversions (advertising). When you give us your email in a form and have allowed advertising data, our server turns it into a SHA-256 hash before anything reaches Google, and Google uses the hash to match the conversion to an ad. Without that consent our server removes the email and it is never sent.
• PostHog (analytics). PostHog, hosted in the EU in Frankfurt, shows us how people use the site: pages viewed, clicks, and session recordings in which everything you type into a form is masked. It starts only when analytics is allowed, keeps its ID in a cookie and in browser storage, and uses the velo_subject ID from your consent record so that one visitor counts once. PostHog is set to discard your IP address.

The cookie notice lists every cookie and storage item, with its lifespan.

5. When you use the Velo console

• Your account. Your email address, your password, which we store only in hashed form, or your Google sign in, the websites you add, your settings and your team. If you sign in with Google, Google shares your name and email address with us.
• Payments. Stripe handles subscriptions and card payments. We never see or store your full card number; we keep your plan, your invoices and the Stripe reference. If you allowed analytics, checkout also carries the Google Analytics IDs of your visit so a purchase can be matched to the campaign that brought you. If you did not, the purchase reaches Google Analytics under a one time ID that cannot be linked to you.
• Emails. Account emails, such as verification, password reset, invitations and billing notices, are sent through Scaleway Transactional Email in Paris.
• Product analytics, depending on your choice. When analytics is allowed, the console uses PostHog, without cookies or browser storage, to see which features are used and where people get stuck. These events are linked to your user ID, your account and your email address, and sessions are recorded with form inputs masked. Without analytics consent PostHog does not load in the console. Separately, whatever your choice, our server records a few account milestones in PostHog under your user ID and your account: when your banner first goes live, when a scan confirms it works, when you first open a report, and purchases and plan changes. Your choice under Cookie preferences in the account menu also covers Google Analytics in the console.
• Where it is stored. Account data and consent records are stored in a PostgreSQL database run by Scaleway in Paris, which the console reaches through Cloudflare.

If you install Velo Consent from the Shopify App Store

• What Shopify shares with us. When you install the app, Shopify gives us your store's name, its myshopify.com address, its contact email and its main domain. We use them to create your store's Velo account and site. The app asks Shopify for no access to your products, orders or customers, and we receive no data about your customers.
• Your visitors' choices. The banner also passes each visitor's choice to Shopify, so that Shopify, your sales channels and other apps follow it. Shopify handles that part under its own privacy policy.
• Uninstalling and erasure. If you uninstall the app, we keep your settings so that a reinstall picks up where you left off. About 48 hours later Shopify asks us to erase your store's data, and we then delete your store's site, banner and region settings and scan reports. The consent records your visitors created are kept until their retention period ends, as described in section 11, because they are your evidence of the consent each visitor gave or withdrew. They are pseudonymised and identify no Shopify customer.
• Payments. Paid plans for Shopify stores are billed by Shopify, not by Stripe.

6. What Velo records inside the product

When Velo runs on a customer site, it records a pseudonymised consent log: the choice made, a coarse region detected from the request country at the edge, and a timestamp. Region detection performs no third party geolocation lookup. Velo does not build profiles, does not track visitors across sites, and never sells or shares this data.

7. The Velo Privacy Inspector Chrome extension

The Velo Privacy Inspector is a free Chrome extension that checks whether the Google tags on a web page respect Google Consent Mode and send enhanced conversions. It works entirely inside your browser.

• What it reads. When you press Scan, it reloads the page you are on and, for about 10 seconds, reads the requests that page sends to Google's tag services and the consent commands on the page. For the form test, it watches for the first Google Ads conversion request after you submit a form, for up to 5 minutes, and notes only whether contact details were present in it, never their value or hash.
• What it keeps. Results stay in your browser's session storage and are deleted when you close the tab or Chrome. Download report saves a file to your own computer.
• What it sends. Nothing. The extension has no server, no analytics and no account, and sends nothing about you or the pages you scan to us or anyone else. Setup guide links open pages on this website with campaign tags naming the extension, but nothing about the site you scanned. Your visit to those pages is covered by sections 3 and 4.
• Site access. Chrome asks you to allow access to a site and to Google's tag hosts the first time you scan it. You can remove that access at any time in Chrome's extension settings.

Because the extension collects no personal data, there is nothing for us to hold, share or delete. What the scanned site itself sends to Google is covered by that site's own privacy notice.

8. Why we are allowed to use it

• Running and securing this website and the console, and counting visits from our ads without cookies: our legitimate interest in operating, measuring and protecting them (Article 6(1)(f) GDPR).
• Analytics and advertising on this website and in the console: your consent (Article 6(1)(a) GDPR and the ePrivacy rules on cookies), which you can withdraw at any time.
• Account milestones in the console (sent by our server to PostHog): our legitimate interest in knowing whether customers get Velo working and which plans they choose (Article 6(1)(f) GDPR). They carry no browsing data, only the milestone, and your user ID and account.
• Your account, payments and account emails: performing our contract with you (Article 6(1)(b)), and our legal duty to keep invoices (Article 6(1)(c)).
• Answering your message or enquiry: our legitimate interest in replying, or taking steps to enter a contract at your request (Article 6(1)(b)).
• Providing Velo to a customer: performing our contract with that customer.

9. Who receives it

We do not sell your data.

10. Transfers outside the EU

Cloudflare, Google and Stripe may process data in the United States. Those transfers rely on the EU–US Data Privacy Framework, under which these providers are certified, and on the European Commission's standard contractual clauses. Our PostHog project is hosted in the EU, and Scaleway keeps our data in France.

11. How long we keep it

• Your consent choice: in your browser, a cookie for up to a year and browser storage until you clear it.
• Google Analytics: event data for 14 months.
• PostHog: session recordings for 30 days. Other events for as long as we need them to understand how the site and the product are used, and we delete them when you ask.
• Visits from our ads: three months.
• Your account: while it is open, then only what the law requires us to keep, such as invoices, which Estonian accounting law requires us to keep for seven years.
• Messages and enquiries: up to 24 months after our last exchange, unless we need them longer for a legal or accounting reason.
• Consent records inside a customer's site: the retention window that customer sets.
• Consent records after a Shopify store is erased: at least three years from when each was recorded, or the longer window the store had set, after which they are deleted. Records of a visitor withdrawing consent are not deleted: proof that consent was withdrawn matters more than the original choice, so we keep it with no end date.

Cookie lifespans are listed in the cookie notice. We do not keep personal data longer than we need it.

12. Your rights

You can ask us to give you a copy of your data, correct it, delete it, restrict or object to its use, or move it elsewhere. Where we rely on your consent, you can withdraw it at any time, which does not affect what we did before you withdrew. To exercise any of these, email support@veloconsent.com. You can also complain to a supervisory authority: in Spain the Agencia Española de Protección de Datos (AEPD, aepd.es), in Estonia the Andmekaitse Inspektsioon, in the UK the Information Commissioner's Office, or the authority where you live.

To change or withdraw your consent on this website, open the cookie button in the bottom corner of any page. In the console, use Cookie preferences in the account menu.

13. Changes to this notice

If we change how we handle data, we will update this page and move the date at the top. Material changes will be made clear.

Questions about your data?

Email support@veloconsent.com or read the GDPR and data processing page.