Back to explore

Privacy policy

What Logo Lattice stores in your browser, which cookies are set, and which third parties we rely on.

Last updated 16 May 2026

Overview

Logo Lattice (logolattice.com) is operated by Luke Orriss. This policy describes the data we collect, how it is stored, and the third-party services involved when you use the editor, marketing pages, or Studio (accounts and premium features).

The free editor works without an account. Optional Studio sign-in, cloud projects, and payments add server-side processing described below.

First-party browser storage (localStorage)

Logo Lattice stores the following keys in your browser's localStorage on our origin. None of this is transmitted automatically except where noted (for example, cloud sync when you are signed in with Studio).

  • theme - your light, dark, or system colour preference (via next-themes).
  • logo-lattice:app-settings:v1 - editor defaults and UI preferences, including whether usage analytics is enabled.
  • grid-logo-builder:v1 - your in-progress logo document and sidebar collapsed state. Used as a local backup when you are not on a synced cloud project.
  • iso-logos:editor-floating-panels:v1 - positions of draggable panels (toolbar, function bar, style orb).

You can clear this data at any time through your browser's site-data settings. Clearing storage resets preferences and unsaved local work.

First-party cookies

When you sign in to Studio, our authentication library (Better Auth) sets HTTP-only session cookies on logolattice.com so the server can recognise your session. We do not use these cookies for advertising.

  • better-auth.session_token - session identifier; required to stay signed in. HttpOnly and scoped to our site.
  • Additional Better Auth cookies may be set during sign-in flows (for example CSRF or OAuth state). Names follow the better-auth.* prefix unless configured otherwise.

If you are not signed in, we do not set authentication cookies. Theme and editor state use localStorage only.

Usage analytics (PostHog)

When Usage analytics is enabled in Settings → Privacy (on by default for new visitors), we load PostHog to understand how the product is used. You can turn this off at any time; we call opt_out_capturing when disabled.

PostHog may store identifiers in localStorage and/or cookies on our domain, for example:

  • Anonymous or pseudonymous distinct IDs and session replay metadata (person profiles are identified_only - we do not attach your logo artwork).
  • Events we send: page views ($pageview with URL), export_svg_clicked, export_png_clicked, export_logolattice_clicked, import_logolattice_clicked (with shape count only, not geometry).

Data is sent to the PostHog host configured in our deployment (see PostHog's privacy policy). No canvas pixels or SVG paths are uploaded as part of analytics.

Third-party services

These providers process data when you use related features. They may set their own cookies or storage on their domains during redirects or embedded flows.

  • Better Auth - email/password and session management on our servers; issues first-party session cookies as above.
  • Google - optional “Continue with Google” sign-in. You are redirected to Google; Google’s cookies and privacy policy apply on accounts.google.com.
  • Dodo Payments - Studio checkout, customer portal, and webhooks. Checkout and billing portal open on Dodo Payments’ domain; their cookies and terms apply there. We receive subscription status via webhooks and store premium entitlement on your user record.
  • PostgreSQL (hosted database) - account details, hashed credentials, sessions, and cloud project snapshots for Studio users.

A Buy Me a Coffee widget script exists in the codebase but is currently not loaded in production layout.

Server-side data we store

  • Account: name, email, email verification status, profile image URL (if provided), premium flag, timestamps.
  • Projects (Studio): project title and editor snapshot JSON synced from the client when you save.
  • Payment metadata: handled by Dodo Payments; we update premium access from verified webhooks and checkout success flows.

Your choices

  • Toggle Usage analytics in the in-app Settings panel under Privacy.
  • Clear site data in your browser to remove localStorage and cookies for logolattice.com.
  • Sign out of Studio to invalidate your session cookie.
  • Contact us to request access, correction, or deletion of account data where applicable law requires it.

Contact

Questions about this policy: support@logolattice.com. See also our terms of service.