What Logo Lattice stores in your browser, which cookies are set, and which third parties we rely on.
Last updated 16 May 2026
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.
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).
You can clear this data at any time through your browser's site-data settings. Clearing storage resets preferences and unsaved local work.
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.
If you are not signed in, we do not set authentication cookies. Theme and editor state use localStorage only.
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:
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.
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.
A Buy Me a Coffee widget script exists in the codebase but is currently not loaded in production layout.
Questions about this policy: support@logolattice.com. See also our terms of service.