Saved places and local reviews
The key asheville-saved stores your saved place IDs in local storage until you clear them. Review entries under asheville-review- plus a listing ID are also saved on your device; this local feature does not by itself publish a review to the server. Anyone using the same browser profile may be able to see these saved items.
Sign-in and unfinished forms
Clerk uses cookies or related browser storage to keep sign-in and account flows working. Temporary business-claim and new-listing fields are stored in session storage to preserve your progress through account verification. Session storage normally ends when its tab or browser session closes; completed onboarding also clears its saved draft. Blocking this storage can interrupt sign-in or form recovery.
Site and game statistics
The script /avl-stats.js reports page views and arcade play time to our own server. It sets no cookies and uses no browser storage.
Listing interaction counts
The session-storage key avl-visit contains a generated session identifier used to avoid repeatedly counting the same listing interaction. The application sends the listing ID, interaction type, and this identifier to its analytics endpoint. This feature measures directory interactions; it is not a third-party advertising pixel.
External resources
Map tiles from OpenStreetMap, Google Fonts, externally hosted images, and loaded social embeds make requests to their providers. Those providers may use their own storage and receive your network information. Their behavior is governed by their own policies and your browser settings. We do not treat browsing this page as consent to new advertising cookies.
Control your storage
Use your browser’s site-data settings to inspect or delete Asheville.gg cookies, local storage, and session storage, or block third-party cookies. Clearing site data removes saved places and local reviews and may sign you out. Private browsing limits persistence but does not hide your IP address from the services you contact. Questions can be sent to jeff@jeffhampton.us.