This article is about the Proxi admin app at app.proxi.co.
If you've put a Proxi map, directory, or calendar on your own website, you may wonder what it does to your visitors' browsers and whether your cookie banner needs to know about it. Short version: very little, and probably not.
What a Proxi Embed Sets on Your Site
Maps and directories: nothing on your site. The embed runs in its own frame from our domain. Inside that frame, the only identifier is an anonymous viewer ID so likes and votes work; it isn't tied to a name and it isn't shared with anyone.
Calendars: the embed remembers events a visitor has saved, in their own browser, so they're still there next time. That's a convenience for the visitor, not tracking.
No advertising, no visitor identification, no session recording. Those tools never run inside Proxi embeds or on the pages your visitors use.
Analytics
We count views and clicks so your dashboard can show you how your map is doing. Those counts carry no names or email addresses. For visitors in the UK, the European Economic Area, and Switzerland, analytics sets no cookies and sends no identifiers at all.
Your Banner Is Still Yours
Cookie notices and consent on your website are your responsibility, the same as for any widget you add. In practice, a Proxi embed is "functional" rather than "advertising," so most banners can leave it uncategorized or list it as necessary. If your consent tool blocks unknown frames until a visitor agrees, add our domain to its allowed list so the map shows right away: app.proxi.co.
Visitors Who Send a Privacy Signal
Some browsers send a "don't track me" setting called Global Privacy Control. Proxi honors it. It doesn't change what your embed does, because the embed wasn't tracking them in the first place.
Good to Know
The full list of what our own website sets is in our Privacy Policy, with a link to the cookie list. That's about proxi.co, not your embed.
Custom domains work the same way: a map on maps.yourtown.org sets the same things as one on ours.
If a visitor says the embed "won't load" and mentions cookies or a sandbox, that's a website-builder setting, not consent — see Which Embed Code Should I Use? for the fix.