Cookie Policy

Cookies and similar browser storage used by Burning Bridges AI.

Last updated: 2026-10-12

Publication items to complete: confirm the cookie and browser-storage inventory for the live deployment, which optional third-party integrations are enabled, whether a consent interface is required for the audiences served, and the operator’s privacy contact. Provider-specific cookie behavior is not determined by this application.

What cookies and browser storage do

Cookies and similar browser storage help the site keep sign-in and upload sessions, remember language or display preferences, apply security controls, and record visit attribution. The exact cookies set by authentication or third-party integrations may vary with deployment settings.

Cookies used by the application

The current application code sets or uses these first-party cookies:

| Cookie | Purpose | Duration in the application | | --- | --- | --- | | app_device_id | Device-related security and abuse-prevention checks. It is marked HttpOnly and SameSite=Lax, and Secure on HTTPS requests. | 1 year | | bb_visitor | Associates a temporary portrait upload with the visitor’s upload session. | 1 hour | | utm_source | Remembers a sanitized visit-source value for attribution. | 30 days | | PARAGLIDE_LOCALE | Remembers the selected language. | 400 days | | Authentication session cookies | Maintain sign-in and session state through the authentication system. | Set by the authentication configuration; no duration is stated here. |

The site also uses browser storage for preferences such as the display theme. Browser storage is not itself a cookie, but it can be managed through browser settings.

Optional third-party technologies

The application can conditionally load Google Analytics, Plausible, Google AdSense, Google One Tap, and Crisp or Tawk.to support widgets when configured by the operator. These services may use cookies or similar technologies under their own terms. The application does not define their cookie names, lifetimes, or independent data practices. The operator should confirm the live configuration and disclose the applicable provider notices before publication.

Managing cookies

You can review, delete, or block cookies through your browser settings. Blocking authentication or upload cookies may prevent sign-in, language preferences, or temporary portrait uploads from working. The current application does not provide a separate cookie-preference center.

Contact and changes

The operator’s privacy contact has not been provided. Add the contact channel and confirm whether additional consent controls are required before publication.

This policy may be updated when the service or its integrations change. The update date appears above.