Privacy-first architecture
You don't need cookies to personalize.
Cookie-based tools were built for logged-in ecommerce. Physical retail has walk-in traffic, anonymous visitors, and a one-person legal team. Here's the comparison.
Busyfolder vs. cookie-based tools
Cookie-Based (Dynamic Yield, Nosto) | Busyfolder | |
|---|---|---|
| How it works | Drop a cookie → track behavior → build profile | ZIP code → public signals → return banner |
| Data collected | Browser fingerprint, device ID, session history, clickstream | 5-digit ZIP only (24-hour TTL) |
| Consent required | Yes — GDPR/CCPA consent banner | No — zero PII by architecture |
| Legal review time | Weeks to months | 15 minutes (DPA template included) |
| Works for anonymous visitors | No (needs cookie/session) | Yes (works on first visit) |
| Works for walk-in Wi-Fi | No | Yes (IP → ZIP) |
| Integration time | 6 months (platform migration) | 2 weeks (one POST endpoint) |
| Pricing | $50K–$200K+/year | $999/month (5–10 stores) |
| Cookie-safety | Dependent on browser policies | Immune — no cookies used |
What Busyfolder reads instead of tracking you
All signals are public, aggregated, zero-PII. No profile is built. No visitor is identified.
WeatherNOAA
Rain → waterproof jackets; UV > 8 → SPF 50
Local eventsTicketmaster, Eventbrite
SXSW → festival essentials; game day → team gear
DemographicsCensus, SafeGraph
Affluent ZIP → premium collection; near campus → student budget
Points of interestSafeGraph
Near gym → post-workout; near hotel → travel sizes
Holidays & trendsGoogle Trends
Local holiday → seasonal; trending → now popular
The architecture
Visitor arrives → Your server gets ZIP (IP geolocation)
POST /v1/select { zip, banners[] } → Busyfolder reads public signals
Returns best banner_id in <60ms
ZIP discarded after 24 hours. No profile built.
See it work with your own ZIP codes
Free sandbox. No card. No PII. No expiry.