Cookie Notice

Cookies are small text files stored on your device by your browser when you visit a website. They're used to remember settings, keep you signed in, understand how a site is used, and personalize content. This Notice also covers similar technologies like web beacons, pixels, local storage, and mobile device identifiers.

Strictly necessary cookies. Alvro sets exactly one, alvro_session, and only once you sign in. It is what keeps you signed in; you can't turn it off without breaking sign-in, and signing out clears it.

Functional storage. Alvro keeps a few things in your browser's local storage rather than in a cookie: your light or dark theme, whether you were last browsing as a guest or a host, and — if you host — the draft of a car listing you haven't published yet, so closing the tab doesn't lose your work. None of it leaves your device, and none of it is used to identify you.

No advertising or analytics cookies. Alvro runs no ad pixels and no tag manager, and nothing here builds a profile of you or follows you to other sites — so there is no advertising or measurement cookie to consent to or to switch off. The one thing that does measure anything is the performance monitoring described under Third parties below: it samples about one page view in ten, and it uses no cookie at all. If any of that changes, this Notice changes with it and you will be asked first.

Running Alvro means your browser sometimes loads things from other companies' servers. Here is every one of them, what it is for, and whether it sets a cookie. Two do:

• Map tiles — sets cookies. The maps on car and search pages are drawn from CARTO (a, b, c and d.basemaps.cartocdn.com), using OpenStreetMap data. Loading a page with a map contacts those servers and they may set their own cookies.
• Photography — sets cookies. Marketing and placeholder photography is served from images.pexels.com. Its CDN sets two cookies (__cf_bm and _cfuvid) to tell automated traffic from human traffic. They are set by that CDN, not by Alvro, and Alvro cannot read them.
• Profile pictures. Placeholder avatars in the inbox and booking screens come from i.pravatar.cc.
• Payments. Card details are collected by Stripe at checkout and never reach Alvro's servers.
• Error and performance monitoring. Alvro sends crash reports to Sentry so they can be fixed — and, separately, a sample of roughly one page view in ten, to measure how long pages take to load. That sample is not limited to pages that went wrong, so some record of ordinary browsing does leave your browser. What it contains is the page's path — for example /cars/1042 — and timing. Anything after the ? or # in the address is stripped before the report is sent, and Alvro does not attach your name, email or account id to it. Reports are routed through alvro.com so ad blockers can't silently drop them; they still end up with Sentry.
• Address and vehicle lookups. Typing an address queries OpenStreetMap's Nominatim service; adding a car looks its VIN up against the US government's NHTSA database.

Whichever of these a page loads, it is contacted because the page needs it — a map, a photo, a payment form. None of them is analytics or advertising, and none is loaded to build a profile of you. Some receive your IP address, as any server you load a file from must.

Because Alvro sets no advertising or analytics cookies, there is no category switch to offer you — there is nothing in that category to turn off. What you can do:

• Sign out, which clears the session cookie that keeps you signed in.
• Configure your browser to block or delete cookies. Blocking strictly necessary cookies will prevent sign-in from working.

If Alvro ever introduces analytics or advertising cookies, a preference control will ship with them and this Notice will say so.

We may update this Cookie Notice as we add new features, change partners, or in response to legal requirements. Material changes will be announced through the app or this page.

Questions about cookies? Email privacy@alvro.com.