Cookies, sessions, and local signal storage.

How VibeForge uses cookies and storage

VibeForge uses a small amount of browser storage to keep the app fast, remember basic access state, measure product usage, and support checkout. The cookie banner is informational and non-blocking so the prompt builder remains usable.

VibeForge storage we set

• vibeforge_email in localStorage: remembers the email you entered for signup, copy unlock, or Pro status checks so you do not need to retype it every visit.
• vibeforge_email_session cookie: a 90-day HttpOnly, SameSite=Lax email session cookie used by server routes to check Pro entitlement and saved profile access.
• vibeforge_saved in localStorage: stores free saved Vibe Profiles and browser-only prompt builder saves on your device.
• vibeforge_attribution in localStorage and a first-party cookie: stores UTM campaign fields for up to 30 days so signup and checkout events can be attributed to ad campaigns.
• vibeforge_cookie_consent in localStorage: remembers that you dismissed the cookie banner.

Analytics cookies and identifiers

• VibeForge loads the NanoCorp/PostHog analytics script to capture page views, SPA route changes, clicks, JavaScript errors, and Core Web Vitals.
• PostHog analytics may use cookies or localStorage identifiers to understand anonymous sessions and product usage over time.
• We use analytics to improve the Vibe Board, measure campaign performance, diagnose bugs, and avoid shipping slow or confusing pages.

Authentication and Pro access

• The signed vibeforge_email_session cookie lets server routes verify the email associated with a Pro entitlement without exposing the raw session logic to client scripts.
• Pro saved profiles are stored server-side with your email lead record. Free prompt saves stay in your browser unless you choose to upgrade or save through a Pro feature.
• Clearing cookies or localStorage may sign you out of email-based access, remove local prompt saves, and require you to enter your email again.

Stripe checkout

• VibeForge sends Pro buyers to a NanoCorp-hosted Stripe checkout page. Stripe may set checkout, fraud-prevention, and payment-security cookies on the checkout domain.
• VibeForge receives payment status events needed to activate Pro, but Stripe handles card numbers and sensitive payment credentials.
• Do not enter Stripe test-card numbers on live checkout links; test cards work only on dedicated test checkout links shared for testing.

Your controls

• You can clear VibeForge localStorage and cookies from your browser settings to remove local identifiers, saved prompts, attribution values, and banner acknowledgement.
• You can block or limit third-party cookies in your browser. Some analytics, attribution, checkout, or session behavior may become less accurate.
• For privacy or deletion requests related to stored email, Pro entitlement, or saved profile data, contact vibeforge@nanocorp.app.