Cookie Policy

Last updated: June 19, 2026

Short Version

Zam! does not use advertising cookies, retargeting pixels, session replay, Google Analytics, Mixpanel, or data-brokerage tracking on the marketing site.

Cloudflare may provide aggregate website delivery, security, performance, and web-analytics telemetry as part of hosting. Zam! does not use that telemetry to sell ads, build behavioral profiles, or read budget data.

The marketing site sets one required first-party site-data marker so browser controls can show zambudget.com in cookie and site-data lists, including private or incognito sessions when site data is allowed.

The app uses necessary browser storage for preferences, sign-in/session behavior, local budgets, encrypted Cloud Sync helpers, and temporary demo behavior. That storage is for product function, not advertising.

This policy covers normal cookies and similar browser storage technologies that store or access information on your device, including localStorage, sessionStorage, and IndexedDB.

What Zam! Uses

Required site-data cookie

Hosts: zambudget.com and app.zambudget.com. Cookie: zam_site_data_notice=required. Purpose: keeps a required first-party site-data marker visible in browser cookie controls for the current Zam host. Type: first-party functional/site-data cookie, host-only to the current Zam host. Optional analytics or advertising cookies: not used.

LocalStorage

Used for app preferences, theme/accent settings, browser-only budget data, temporary demo state, non-sensitive UI settings, and local gift-card merchant metadata cache status.

IndexedDB

May be used for local trusted-browser capability storage, such as a non-extractable WebCrypto key that lets the same browser keep syncing after refresh without storing the raw recovery key in localStorage.

Session storage and memory

May be used for short-lived UI state, temporary authentication flow state, and in-memory encryption keys. Session-only data may disappear when the tab or browser is closed.

Provider session cookies

Supabase, Stripe, Cloudflare, Proton, Google, or similar infrastructure providers may use necessary security/session cookies or anti-abuse checks when you sign in, open checkout, receive email, or access protected infrastructure.

Cloudflare Web Analytics / Insights

Cloudflare may serve a lightweight beacon or process request metadata for aggregate traffic, performance, reliability, and abuse-prevention measurements. This is infrastructure telemetry, not advertising or budget-content analytics.

What Zam! Does Not Use

  • No advertising cookies
  • No cross-site retargeting pixels
  • No Google Analytics, Mixpanel, or similar behavioral analytics scripts
  • No session replay or heatmap scripts
  • No sale of budget data or behavioral profiles

Clearing Browser Storage

You can clear Zam! browser storage from your browser's site-data controls. Clearing storage can remove local preferences, browser-only budgets, demo state, local gift-card metadata caches, trusted-browser keys, and other local-only data.

You can block or clear cookies and site data through Browser settings > Site settings > Cookies and site data for zambudget.com or app.zambudget.com, or use Zam!'s local erase/reset controls such as Erase Local Budget Data or Erase Local Data. Blocking app required site data may prevent Zam! from saving or loading budgets, keeping sign-in state, or preserving trusted Cloud Sync unlock state.

If you use Cloud Sync, keep your recovery key saved before clearing browser data. Zam! cannot decrypt or recover synced budget contents without that key.

Questions

For privacy or cookie-policy questions, contact the legal mailbox.

Contact: legal@zambudget.com
Mail-only office address:
6635 S. Dayton St. Ste 310 #524
Greenwood Village, CO 80111-6156