Contact Lunalisa

Contact Lunalisa

Use the verified support mailbox for prototype, privacy, or legal questions.

To contact Lunalisa, email support@lunalisa.pro. This is the public channel for questions about the browser-local storyboard prototype, accessibility problems, factual corrections, privacy, legal notices, and early product feedback.

The site does not use a contact form, live chat, support account, ticketing portal, or automated intake service. Clicking the email link opens the mail application configured on your device. Your email is handled by the systems used to send and receive that message, not by a form embedded on this website.

How to make a support message useful

Begin with a short subject that identifies the area: prototype issue, accessibility, editorial correction, privacy, or legal question. Describe what you expected, what happened, the page address, and the browser or device involved. If an interaction failed, list the steps that reproduced it. This information helps separate a content problem from a layout, browser, or validation problem.

For editorial corrections, include the exact sentence, the official source that supports the change, and the date you checked it. Third-party product availability, pricing, credits, and policies can change quickly, so a dated first-party source is more useful than an undated screenshot or a copied search snippet.

Example message for a prototype issue

A useful report might say: “On the storyboard planner page in the current version of Edge on Windows, I entered a campaign idea longer than eight characters, selected Proof, and submitted the form. The placeholder disappeared, but scene three was not visible at 200% zoom. I expected all five scene cards to remain readable without horizontal scrolling.”

That report contains the page, environment, action, result, and expected behavior. It does not include the sender's confidential campaign brief. A screenshot can help if it excludes private tabs, account information, personal messages, and unreleased client material.

What not to send

Do not email passwords, API keys, payment card information, government identifiers, health information, confidential client briefs, unreleased financial results, private media, or files you are not authorized to share. Lunalisa does not need those materials to review the current local prototype.

Do not send emergency requests through this address. No continuous monitoring, guaranteed response time, service-level agreement, or urgent-response capability is promised. If a message concerns immediate danger or an emergency, contact the appropriate local service instead.

Product feedback

The most useful feedback describes a real decision. Explain what kind of campaign you were planning, where the five-scene structure helped, where it became unclear, and what you did next. Avoid including sensitive campaign content. A generalized description such as “a fifteen-second product launch for a small ecommerce team” is normally enough.

Feedback does not create a customer relationship, product commitment, roadmap promise, or obligation to implement a suggestion. If a future research or early-access program requires additional information, its scope and handling should be stated separately before collection.

When reporting a confusing result, name the scene and the decision you could not complete. For example, explain that the Proof scene did not distinguish an approved demonstration from an unsupported claim, or that the Action scene did not leave enough room for a destination. This produces more actionable feedback than a general request for “better output.”

If you are suggesting a feature, describe the repeated obstacle rather than only the interface control you imagine. The project can then evaluate whether the need belongs in the focused planning workflow, requires a separate product capability, or should remain in the team's existing production system.

Privacy and legal questions

Questions about the website's current data behavior may use the same support address. The public prototype has no login, uploads, payments, remote analytics, or persistent project storage. A campaign brief entered into the planner remains in the active browser page and is not placed in an event payload.

Legal correspondence should clearly identify its purpose and the person or organization sending it. The configured operator is domain, at 30 N Gould St Ste R, Sheridan, WY 82801, USA. Publishing that contact information does not authorize unsolicited marketing, scraping, or unrelated bulk messages.

Third-party guide corrections

Lunalisa publishes independent guides that may mention Higgsfield. Lunalisa is not affiliated with, endorsed by, or sponsored by Higgsfield. If an official feature, free-access rule, billing practice, or plan detail has changed, send the current first-party page and the date observed. The editorial team should verify the claim before revising the guide.

Contact FAQ

What is the official support email?

The verified public mailbox is support@lunalisa.pro.

Can I upload a campaign file for review?

No upload service is available. Do not email confidential or rights-restricted campaign materials.

Does the website provide live chat?

No. The current contact channel is email only, and no response time is guaranteed.

Can I report an accessibility issue?

Yes. Include the page, browser, assistive technology if relevant, steps, actual result, and expected result without sending sensitive information.

Verified public contact

Email support@lunalisa.pro. Operator: domain, 30 N Gould St Ste R, Sheridan, WY 82801, USA.

Next action

Evaluate the workflow before adding a backend

Complete the local prototype and record what would make this useful enough to revisit or pay for.

Validation

Request early access by email

Email support@lunalisa.pro

No website form, analytics provider, cookie, or browser storage is enabled.