Privacy Policy

Last updated: October 18, 2026
✉ Support: closflash@keemail.me

This policy describes the data handling implemented by this ClosFlash website. ClosFlash is operated by the owner of the domain where it is published and is not an official Ollama, Google/Firebase, or Cloudflare product.

Information processed

Guest conversations and guest URLs

While signed out, a conversation and its retained message/image previews are stored in this browser's local storage. The app treats the conversation as expired 24 hours after it was created, regardless of further activity, and removes expired entries the next time guest history is loaded or saved. Guest conversation contents are not saved to a ClosFlash server database. A URL includes a random conversation ID, but that ID is not enough to retrieve the conversation without the matching local browser record. Opening a guest URL in another browser, browser profile, or device shows a “This isn't your chat” message instead of the chat contents.

Guest history may become unavailable sooner if you clear this site's data, use private/incognito browsing, change browser profiles, or the browser evicts local storage. Guest URLs are not cross-device or public share links.

Signed-in conversations

When signed in, the app saves each conversation and its messages to Cloud Firestore under that Firebase user ID. The included Firestore security rules authorize reads and writes only when the authenticated UID matches the owner ID in the path. A conversation can be opened only by the account that owns it. Signed-in conversations do not automatically expire and are retained until deleted by someone with authorized access to the Firebase project. The current interface does not include a self-service delete-chat control.

AI processing and image uploads

Chat requests pass through a hosted Cloudflare Worker, which calls the Ollama Cloud API. The Ollama API key is configured as a Worker secret and should never be placed in browser JavaScript. Text requests use NVIDIA Nemotron 3 Ultra by default. Requests containing images are routed to Gemma 4 31B because Nemotron 3 Ultra is text-only and Gemma 4 supports image input. The selected provider/model may change if the operator changes the Worker configuration. Ollama's terms and privacy practices apply to content sent to Ollama Cloud; Cloudflare and Firebase policies apply to their respective services. This project does not promise that third-party providers retain no request data.

For time-sensitive questions (such as current events, news, latest releases, or recent developments), the backend may query public search/news endpoints, including Google News RSS and DuckDuckGo HTML search, using part of your prompt as the search query. Matching result titles, snippets, publication dates, and URLs are passed to Ollama Cloud to help generate an answer with source links. These public endpoints may receive the search query and technical request metadata. Search is best-effort and may not return results for every question; it is not a guarantee of comprehensive web coverage. Avoid submitting passwords, API keys, payment information, or other secrets in a prompt or image.

Cookies and local storage

Firebase Authentication may use browser storage or cookies to maintain your sign-in session. ClosFlash uses local storage to retain guest chat contents and their expiry information. A guest URL does not expose the chat contents in the URL itself.

Retention, deletion, and privacy requests

Guest conversations are usable for 24 hours after creation and expired items are removed from the app's local guest-history list at its next load/save. You can remove them sooner by clearing this website's local storage. Signed-in conversations have no automatic expiry. Because this version has no delete-chat button, a user needing an account conversation deleted must contact the site owner at closflash@keemail.me.

Children and policy changes

The operator sets an age policy suitable for the jurisdictions and audience served. This policy should be revised if the data flow, providers, or retention settings change. The “Last updated” date should be updated when the policy materially changes.