Cookies & Browser Storage

Browser storage includes cookies, local storage and session storage. Our Cookie settings separately control Logopack’s optional first-party analytics and our Google Analytics integration. They are not a promise to control every technology used by Base44, Google sign-in or Stripe on their own services or within their infrastructure.

Refusing optional analytics leaves account access, export and payment features available. Storage needed for a feature you request is handled separately. Clearing essential sign-in or draft storage can sign you out or remove unsaved work.

An offer identifier and signed assignment (logopack_offer_visitor_v1 and logopack_offer_token_v1) keep the pricing and export options shown to you consistent. These values do not contain your email or logo files. The server links an assignment to your account when you sign in and compares registration and paid purchase totals for each offer. Clearing browser storage can remove a guest assignment; an account keeps its assigned offer. These keys are handled separately from optional page analytics and remain until cleared or replaced.

The local-storage key logokit_cookie_consent records your first-party analytics choice, its version and decision and expiry times. The choice is valid for 180 days. After expiry, first-party analytics require a fresh opt-in. You can change or withdraw your choice through Cookie settings at any time.

Only after its opt-in, our first-party analytics records page views and sessions, using page paths without query strings or fragments and the origin of the referring site. Signed-in session events may include your account identifier. We use this information to understand how Logopack is used.

• Local storage: logokit_visitor_id identifies a returning browser; logokit_has_visited records whether it has visited before.
• Session storage: logokit_session_id identifies a browser session; logokit_session_tracked and logokit_user_session_tracked prevent duplicate session events.
• These optional keys are removed when our app processes rejection, withdrawal or consent expiry. Session-storage keys otherwise last for the browser session; local-storage keys can persist until cleared. Removing these keys does not automatically erase events already saved on the server.
• A detected Global Privacy Control signal disables this optional analytics. Do Not Track defaults it to off, although you may explicitly opt in where the interface permits.

Google Analytics is off until a separate explicit choice permits it. The Google choice uses logopack_google_analytics_consent_v1 in local storage and expires after 180 days. Our Google analytics cookies use the logopack prefix, the logopack.app domain and the root path, and last up to 180 days. Only these owned cookies are removed on withdrawal; essential sign-in/draft storage and the first-party consent record are preserved. Cookie expiry may move with activity, but the separate consent still expires 180 days after your choice. Browser restrictions may shorten cookie storage. This is a browser-storage lifetime, not a promise to delete Google’s server records after 180 days.

The separate browser-purchase choice uses logopack_google_browser_purchase_choice_v1 for at most 180 days. Optional session-storage keys logopack_google_browser_purchase_pending_v1 and logopack_google_browser_purchase_seen_v1 bind a fresh consented checkout and prevent repeat reports. Pending records expire within 30 minutes; expiry prevents use, while physical removal occurs when the app next processes the record or the browser session ends. The pending record holds the original pseudonymous Google client/session identifiers, an account-scoped local reference and a random nonce. The server stores a hash binding with the existing signed financial events under financial-record retention, without those raw analytics identifiers.

Accept analytics in the banner permits the disclosed Logopack analytics, Google visit analytics and Google purchase reporting. In Preferences, the three optional choices can be saved independently. Essential only and Reject optional analytics withdraw all three. Close without changing does not grant a new permission. Refusing any option does not affect account access, previews, exports or payments.

A previous first-party choice never enables Google Analytics. You can reach Cookie settings through Legal & Privacy at any time, including when no banner is shown. Global Privacy Control overrides an earlier Google permission. Withdrawal stops future collection by our integration; information already sent or in transit cannot be recalled by the control.

Base44 application code uses local-storage keys including base44_app_id, base44_access_token, base44_from_url, base44_functions_version and base44_app_base_url for application configuration, sign-in and return navigation. The base44_clear_access_token flag can trigger removal of sign-in values, including a legacy token key. These values may remain until overwritten or cleared by the application or browser.

Session-storage keys logokit_wizard_scope_v1 and logokit_wizard_scoped_v1: keep export settings, original SVG file bytes and return-flow flags separate for the current guest session or signed-in account. logokit_wizard_accounts_v1 indexes recent account scopes; logokit_wizard_return_v1 keeps an exact, short-lived observed sign-in return safe across reloads. logokit_wizard_handoff_v1 holds a short-lived, single-use continuation when you explicitly take a guest draft through sign-in; logokit_wizard_reservation_v1: reserves room for that transfer, and logokit_wizard_conflict_v1: retains an account-bound choice when both drafts exist. Earlier unscoped keys logokit_wizard_state, logokit_resume and logokit_save_after_resume, and drafts from other account sessions, may be preserved separately without being opened automatically. These records remain until the application or browser clears them or the browser session ends, subject to the browser’s session-restoration behaviour.

Providers can use additional storage under their own notices. This list identifies app-managed keys rather than claiming to be an exhaustive inventory of all provider infrastructure. See our Privacy Policy for the providers, contact details and information about requesting deletion of retained server records.