Logopack · Legal

Cookies & Browser Storage

Last updated November 5, 2026 · Version 2026-11-05.3

The browser storage used by Logopack and one choice for its disclosed optional analytics.

What these choices cover

Browser storage includes cookies, local storage and session storage. Our Cookie settings provide one choice for Logopack’s optional first-party analytics, Google visit and purchase reports, and DataFast public-page analytics. 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.

Analytics and its shared choice record

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 the shared analytics choice, its version and decision and expiry times. The choice is valid for 180 days. After expiry, these optional browser analytics require a fresh opt-in. The current version covers the disclosed optional browser uses together; older choices do not automatically expand their scope. 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 under the shared choice

Google Analytics is off until the shared analytics choice permits it. Any legacy provider-specific storage does not independently grant permission. The shared choice 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 shared 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.

An internal browser-purchase consent record 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 and purchase reporting, and DataFast public-page analytics together. There are no separate provider checkboxes. Essential only and Reject optional analytics withdraw all these optional uses. Close without changing does not grant a new permission. Refusing analytics does not affect account access, previews, exports or payments.

An older choice does not automatically enable the expanded analytics scope; the updated banner asks for a fresh decision. You can reach Cookie settings through Legal & Privacy at any time, including when no banner is shown. Global Privacy Control overrides an earlier analytics permission. Withdrawal stops future collection by these browser integrations; information already sent or in transit cannot be recalled by the control. This browser choice does not switch off the separate Stripe import into DataFast.

Sign-in, application and draft storage

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.

The updated standard generator keeps only non-file preferences, scoped ownership metadata and short-lived return-flow markers in session storage. Logo and icon originals are held in page memory and are not written to session storage, local storage or IndexedDB by this flow. Reloading or leaving the page for sign-in or checkout may require selecting the originals again; these file-handling changes do not remove paid account access. Earlier versions may have written original files to browser storage, including IndexedDB. Old browser records are not automatically imported or erased by this change. Browser session-restoration behaviour can also affect how long non-file session records remain.

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.

DataFast browser analytics and Stripe revenue import

DataFast public-page tracking is included in the optional browser analytics choice. It stays off until you accept the current choice. Earlier choices do not automatically enable an expanded scope.

With browser consent, DataFast receives public-page addresses and limited campaign labels, referrer origin, pseudonymous visitor and session cookie identifiers, and basic browser and device information. DataFast also receives technical network information such as your IP address. Our browser tracker excludes account pages, payment events, advertising click identifiers, sensitive URL parameters, fragments, names, email addresses and logo content. With your permission, DataFast also measures completed registration, accepted logo uploads, successful export generation, checkout starts, demo-logo use and homepage demo-pack download starts. These goals send only fixed action names and page labels with pseudonymous browser identifiers, not names, emails, account IDs, filenames or logo content. A checkout start is not a purchase, and a download start does not confirm that a file was saved.

Stripe is already connected to DataFast. That separate connection imports revenue records for the selected LogoPack products. Rejecting analytics, withdrawing browser consent, Global Privacy Control or clearing browser cookies does not switch off that Stripe import. The browser exclusions above do not apply to the Stripe feed or any customer information it contains. With your permission, we pass existing DataFast visitor and session identifiers to Stripe when creating a new checkout. DataFast uses them to link confirmed LogoPack payments to visits and marketing channels. Changing browser choices stops new identifier sharing, but does not remove identifiers already attached to an existing checkout. Payments from an existing checkout may still be linked after that change.

The browser choice is recorded in logokit_cookie_consent for up to 180 days; a detected Global Privacy Control signal overrides it. DataFast visitor cookies may last up to one year and its session cookie about 30 minutes, but our browser collection requires unexpired consent. Withdrawal stops new events from our browser tracker, clears its accessible cookies and reloads the page to stop its listeners. These controls do not recall information already sent or confirm deletion of records held by DataFast. Linked analytics records are not anonymous. Use Legal & Privacy or contact support to make a privacy or data-rights request.

Optional Reylin public-page analytics

Reylin (reylin.app) is included in this choice to measure visits to approved public pages. It receives fixed page labels and a pseudonymous browser session identifier, plus technical network information such as your IP address. This pilot does not send query strings, referrer details, account pages, names, emails, logos or payment events. Earlier choices do not enable Reylin; please make a fresh choice. Withdrawal stops new events and clears its accessible session identifier, but cannot recall events already sent.