Cookies & Browser Storage

Browser storage includes cookies, local storage and session storage. Our Cookie settings control Logopack’s own optional first-party analytics. They are not a promise to control every technology used by Base44, Google 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.

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

Only after opt-in, our 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.

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_state, logokit_resume and logokit_save_after_resume preserve export settings, source SVG text and return-flow flags across a redirect. They remain until the application 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.