Cookies and browser storage

When you sign in, the API sets a 30-day logomann_session cookie. It is HttpOnly, uses SameSite=Lax, and is marked Secure over HTTPS. Browser JavaScript cannot read this authentication cookie. Logging out expires it.

Session storage keeps an unfinished project brief in the current tab. It is not an authentication credential and normally disappears when that tab session ends. A successful project submission clears it.

Local storage keeps navigation return paths and a generation request key so an interrupted request can be retried safely. The generation key can include the project ID and remains while the outcome is uncertain; it is cleared after confirmation or a known terminal failure. Return paths are cleared when used or replaced.

When browser storage is available, choosing “Create account” while a public project brief is unfinished saves a temporary copy of the brief, industry and reference URLs in local storage so an email-verification link opened in another tab in the same browser can restore it. The copy can be restored for one hour, is removed when restored or when the project is submitted, and an expired copy is ignored and cleared the next time project creation opens. It does not authenticate you or transfer to another device.

You can clear Logomann cookies and site data in your browser settings. Clearing the session cookie signs you out. Clearing browser storage can remove an unfinished brief, a pending generation retry key, or a return path.