How this website handles data.
This notice explains what the digithings.ai website stores in your browser and what happens when you use its optional chat. It does not cover a copy of the open-source software that you or another organization operate on separate infrastructure.
No ad tracking. No account required.
We do not use advertising pixels or third-party analytics on this website. You can read the site without creating an account. Like most hosted websites, our hosting provider receives ordinary request data needed to deliver and protect the site, such as your IP address, requested URL, browser information, and request time.
The site stores a small number of preferences in your browser using local storage: your colour theme and, if you choose to configure chat, your selected provider, model, and API key. Those values remain in your browser until you clear them. The provider key is sent to our Cloudflare Function only when you test it or send a chat request; the function forwards it to the provider you selected and does not persist it in an application database.
What leaves your browser.
- Messages
When you use digichat, your message and the recent conversation are sent through our Cloudflare Function to the selected model provider. The provider processes that content under its own terms and privacy policy. Do not submit confidential, personal, or regulated information that you do not want processed by that provider.
- Documentation search
Questions about digithings may also be sent to our hosted documentation search so the assistant can retrieve relevant public project documentation. Search results are then included in the request sent to the model provider.
- Provider keys
If you bring your own key, it is stored in local storage in your browser. Each chat or key-test request sends it through our Function to OpenRouter, OpenAI, Anthropic, or Google, according to your selection. We do not write the key to an application database.
- Abuse prevention
Chat requests are rate-limited by IP address in one-minute windows. The counter uses either Cloudflare KV with a two-minute expiry or a best-effort in-memory fallback. Cloudflare may separately process and retain request data according to its own policies as our hosting and security provider.
You control local data.
Theme and chat-provider settings remain until you remove them through your browser or clear the saved key in chat settings. Chat messages normally remain in the current page’s memory and disappear when that page is closed or refreshed.
When the homepage opens a conversation in the full chat page, it temporarily puts that conversation in local storage. The chat page reads and deletes it once. If the stored handoff is more than five minutes old when read, it is discarded; if the chat page never opens, it remains until you clear the site’s local data.
Ask us directly.
To ask what data we hold about you, request deletion of data we control, or raise another privacy question, email us. We may need enough information to verify and act on the request.
We will update this notice when the website’s data flows change and revise the effective date above. For the software’s security model and current limitations, read the security page.
The source for this website is public. The relevant implementation lives in frontend/digithings-web in the digithings repository.