Two entries. No trackers.

LANDING's own code sets no cookies. Its Certified Lander page uses these two local storage entries. Third-party code and wallet providers may use their own storage.

Your Lander wallet

Stored under landing:lander-wallet once the registry confirms or restores your Certified Lander card. It holds your public Solana wallet address, so the next time you open the Lander page it can look up and show the same card.

A swap being checked

Stored under landing:pending-signature after you swap through Jupiter on the Lander page, while the registry checks that the swap was finalized on Solana. It holds the transaction signature. It is deleted as soon as the registry confirms or rejects the swap. If the check runs out of time, it stays so the page can try again on your next visit.

Both values are public on-chain identifiers and may constitute personal data when linked to an identifiable person. The site sends them to the project registry to look up or confirm your card. Scripts running on this origin, including third-party code loaded by the page, may access its local storage.

That is the complete list

• No cookies of any kind
• No analytics or advertising trackers
• No session identifiers or logins, because there are no accounts
• No third-party tag managers

The Jupiter swap window and your wallet app are run by their providers and may keep their own data under their own policies.

Clearing site data for landingcoin.fun in your browser removes both entries. Nothing is lost: the Lander page simply will not remember your card, and you can restore it any time with your wallet address.

Blocking local storage does not break browsing. It may prevent Certified Lander verification, restoration or remembering your card; allow storage for this site to use those features.