Cookies & browser storage
The storage used for sign-in, workspace preferences and optional tracking choices.
Last updated
What the application stores
Ads Lighthouse uses first-party cookies for sign-in, the project you select and any optional tracking choice you save, plus browser local storage for the sidebar preference. Necessary storage supports the account and interface functions you request. Regional defaults for optional analytics and marketing are explained below.
Cookies are sent with matching requests to the site. Local storage remains in your browser and can be read by the application's scripts on the same origin. Neither is required to read our public legal documents.
Storage inventory
These are the storage entries set by the application.
- ads_lighthouse_session: authenticates your session and supports security checks. First-party cookie, up to 14 days; removed when you sign out. It is HttpOnly, SameSite=Lax and Secure in production.
- ads_lighthouse_project: remembers the project you select. First-party cookie, up to 90 days from selection, renewed when a selection is saved. It is HttpOnly, SameSite=Lax and Secure in production.
- ads_lighthouse_brand: keeps the selected project's brand context consistent. First-party cookie, up to 90 days from selection, renewed when a selection is saved. It is HttpOnly, SameSite=Lax and Secure in production.
- ads_lighthouse_tracking_v1: records whether you allow analytics and marketing tags, when you chose, and the notice version. First-party cookie, up to 12 months. It is readable by the site's consent control, SameSite=Lax and Secure in production. Rejecting optional tags also saves this choice so we do not ask on every page.
- ads-lighthouse.sidebar.collapsed: remembers whether you collapse the panel sidebar. First-party local storage with no automatic expiry; it remains until you clear site data or change the preference.
Optional analytics and marketing
We use an approximate country signal from the request to apply regional defaults. Visitors identified in the European Economic Area, the United Kingdom or Switzerland see the consent banner, and optional tags stay off until they allow the relevant purpose. We use the same opt-in default when the country is unknown. For a visitor identified in a country outside those regions, we do not show the banner and the Google Tag Manager container GTM-T833N8P2 may load by default. Any saved choice, including rejection, overrides that default on later visits regardless of country. Cookie settings remains available on every page.
Google Tag Manager delivers tags; it is not itself a list of every measurement service. When the container loads, your browser requests it from Google and shares network and browser details. At this notice's update, the published container has no analytics or marketing tags, so it sets no measurement cookies through our tag configuration. Before adding any tag, we will identify its provider, purpose, data, storage duration and recipients here and configure its consent checks. The container stays off whenever you reject both optional purposes.
External services
Google sign-in and Google connection authorisation take place on Google's pages, where Google's own cookie information applies. Domain icons in the panel are requested from Google's favicon service. These requests are described in our Privacy policy.
When you open paid Checkout or manage billing, you leave Ads Lighthouse for Stripe-hosted pages. Stripe may use cookies and similar technologies on those pages for payment, security and fraud prevention under its own notices. These are not first-party Ads Lighthouse cookies.
The site's network delivery and traffic protection layer delivers and protects traffic. Security challenges, when enabled or triggered, may use additional security storage under the applicable service documentation. Such storage is distinct from the application's entries listed above.
Managing storage
You can remove cookies and local storage using your browser's site-data controls. Blocking the session cookie prevents sign-in from working. Clearing selection cookies resets your remembered project, and clearing local storage resets the sidebar preference. Signing out ends the session but does not clear every interface preference.
Use Cookie settings on any page to change or withdraw your analytics and marketing choice. We apply your new choice before the page reloads. Withdrawing consent stops the container from loading on later pages when you reject both purposes. Cookies already set by a future optional tag may need removal through your browser's site-data controls or that provider's controls; we will document the available removal method when a tag is added. Contact us if you see a storage entry you cannot identify.