This Lunalisa cookies notice describes the current website's use of cookies and similar browser storage. It is effective 2026-08-27. The current release does not use cookies, local storage, session storage, analytics identifiers, advertising pixels, authentication tokens, or persistent project storage.
What a cookie is
A cookie is a small value a website can ask a browser to store and return with later requests. Cookies are commonly used for sign-in sessions, preferences, shopping carts, security, measurement, and advertising. Similar technologies can include local storage, session storage, device identifiers, tracking pixels, and scripts that send behavioral events to a remote service.
Explaining these categories does not mean Lunalisa currently uses them. The public site has no account, payment, personalization, remote analytics, advertising, or saved-project feature that requires such storage.
Current browser-local behavior
The storyboard planner uses ordinary page state while the current tab is open. When a visitor enters a campaign idea and submits the form, local script reveals deterministic scene text. That result is not written to a cookie, local storage, or session storage. Refreshing or closing the page removes it.
The event interface uses fixed workflow and page identifiers for local interaction semantics. It does not include the visitor's brief, email address, or generated text in an event payload, and no remote analytics provider is currently connected.
Example: completing and leaving the planner
A visitor enters “Show how a portable lamp changes a small desk after sunset,” selects Clarity, and displays the five-scene result. The page can show a hook, context, proof, payoff, and action while that tab remains active. No cookie remembers the idea, no account associates it with the visitor, and no saved-project list is created.
If the visitor closes the tab and returns later, the form begins empty. To retain an approved plan, the visitor must copy suitable non-sensitive notes into a tool they control. That external tool may have its own storage and cookie behavior.
Categories not currently used
Authentication cookies: none are needed because there is no login or account session. Preference cookies: none are used to remember theme, language, or form choices. Analytics cookies: none are used to measure visitors or campaign behavior. Advertising cookies: none are used for targeting, attribution, or retargeting. Payment cookies: none are set by Lunalisa because checkout and subscriptions are not enabled.
The absence of these technologies is a statement about the current production site, not a permanent promise that the product can never change. Any future feature that needs browser storage or a third-party script must be reviewed before release.
Hosting and network requests
Delivering a website requires ordinary network requests for HTML, styles, scripts, fonts, and images. Hosting infrastructure can process technical request data necessary to serve and secure those files. That server-side processing is not the same as placing a browser cookie, although a hosting configuration could introduce its own behavior if changed.
The planned deployment platform is Vercel. Before production deployment, the implemented headers, logs, edge features, and platform settings should be checked against this notice. No optional analytics or marketing product should be enabled by default.
External links
Some guides link to official third-party pages. When a visitor follows one of those links, the destination may set cookies or use storage under its own policies. Lunalisa does not control a third party's technology and does not claim that the destination is cookie-free. Review the external site's consent controls and notices directly.
When this notice must change
This notice requires review before enabling accounts, saved projects, personalization, forms, live chat, embedded video, payment, analytics, experimentation, advertising, fraud tooling, or any provider script that reads or writes browser information. The review should identify the purpose, provider, duration, legal basis where applicable, consent behavior, and a practical way to withdraw or change a preference.
A feature should not be described as “necessary” merely because it is convenient to measure. Data collection must match a defined product or security need and remain proportionate to that purpose.
Your browser controls
Browsers normally allow people to inspect, block, or delete stored site data. Because Lunalisa currently writes no cookies or persistent browser storage, using those controls should not affect a saved Lunalisa project—there is no saved project. Browser settings can still affect unrelated sites, email links, or external destinations.
Cookie FAQ
Does Lunalisa use analytics cookies?
No. Remote analytics and analytics cookies are not enabled in the current release.
Will the site remember my storyboard?
No. The prototype keeps the visible result only in the active page and does not save it to persistent browser storage.
Does clicking an external source change this notice?
The destination has its own cookie practices. This notice covers Lunalisa, not a third-party website reached through a link.
What happens if Lunalisa adds accounts or analytics?
The implementation and public notices must be updated before launch, including any required consent and preference controls.
Questions
Questions about this notice may be sent to support@lunalisa.pro. Do not include confidential campaign information or other unnecessary personal data.