1. Functional authentication cookies
These first-party cookies support features you request and protect the service. Cookie names can use the security prefixes __Secure- or __Host- on HTTPS, and session cookies may be split into numbered chunks.
- authjs.session-token
- An encrypted sign-in session cookie, normally HttpOnly and SameSite=Lax. The configured session lifetime is up to 30 days and can be renewed while you use the service. Signing out, account disable or session revocation ends access.
- authjs.csrf-token
- A browser-session security cookie used to protect authentication actions against forged requests.
- authjs.callback-url
- A browser-session cookie used to return you to the appropriate page after authentication.
- ml_impersonate
- An administrator-only, HttpOnly workspace-access cookie lasting up to two hours. It does not grant access to private chats through impersonation.
2. Local demo storage
The interactive preview can save its example library and preferences in your browser under mylibrary-demo-v1. It remains until you clear it or your browser removes site data. This is separate from an authenticated account. Demo chats and temporary file previews stay in that demo session and do not send messages to other people.
Demo browser storage is readable by scripts running on this site. Avoid entering secrets or sensitive personal information into the example workspace.
3. Your choices
You can clear or block cookies and local storage through your browser’s site-data settings. Clearing sign-in cookies signs you out; blocking required cookies can prevent authentication from working. Clearing local storage removes your saved demo changes. It does not delete a server-side account, messages, logs or uploaded files.
This version does not include optional advertising or analytics cookies, so it does not present an “accept all” tracking-cookie banner. If optional tracking is added, the operator must assess the applicable consent requirements and provide appropriate choices before it is enabled.
4. Other sites and contact
Remote icons, images and websites you open may contact third parties, which can receive request information and have their own cookie/privacy practices. MyLibrary’s operator must assess any additional proxy, hosting or monitoring tools used by the actual deployment. Details about the operator, logs, administrator access and your rights are in the Privacy notice.