DOCULOCATE

Privacy details

Last updated October 3, 2026.

This marketing site

The interactive demo uses fictional files and prepared results. It does not upload documents, run live searches, contact AI providers, or store your files. This site contains no analytics or advertising scripts. While a page is open and visible, it sends a short request to the application’s health endpoint about once a minute so the application is ready when you click through. The request carries no document or search data, but the application host can see it, including your IP address and standard request details. Hosting services may process standard request information such as IP addresses and access logs.

The active document on the application server

The application processes one active document at a time for each visitor. Original file bytes, extracted text, viewer data, and the search index are held in server memory, not stored on disk or in a database. Each visitor’s document is kept separate: signed-in people have their own, and a visitor who has not signed in gets a private one tied to their browser (see “Cookies”). Replacing the document, using Reset, an idle server dropping it to make room for others, or a restart clears it from that store. This is not a promise about infrastructure logs, backups, browser history, or provider retention.

Recent-file history in your browser

The app uses browser local storage to keep up to five recent upload entries. For files up to 3 MiB, it attempts to save the file contents so selecting a history entry can upload and restore the file. Larger files can appear in history without cached contents and need uploading again. Browser storage limits can reduce the history retained.

DocuLocate always opens at the empty upload screen: it does not reload your last document by itself. Pick a recent file from History to bring it back. Browser history survives a page reload and a server restart. Reset removes the server’s active document but does not erase this browser history. Clear history removes the saved history entries and their cached contents; it does not remove the active document from the server. To clear both, use Reset and Clear history. Your original files on disk are unchanged.

Search, answers and optional AI

Search, reranking and the built-in answers run on the application server, using semantic and keyword retrieval and simple rules. They are not sent to any outside service and use no AI. The built-in answer is a sentence or value taken word for word from your document, and when it is not confident the Answer label is shown struck through instead.

Only if you choose to use an AI provider, and add your own API key, does the application send your query and candidate passages to that provider for result reranking and possible answer generation. If you also press Ask, it sends your question and the document’s full text to that provider so it can write an answer, up to a size limit you can set in Settings. Provider retention and training policies apply. No blanket promise is made that providers do not retain data or use it for training.

Signing in is optional

You can upload and search without an account. An account is needed only to use your own AI provider, and to get an account page. You can sign in with Google or with an email address and password. With Google, the application receives your name, email address and profile picture from Google. With email and password, it stores your email address and a salted hash of your password (never the password), and there is no email verification or password reset. Account details live in the application’s database.

Your AI provider keys are stored encrypted. They are used only for your own searches, are never shown again (only their last four characters are), and can be removed at any time from Settings or your Account page. The Account page also lets you delete your account, which removes your saved keys, settings and any document held on the server. The person operating the application can see account email addresses, how each person signed in, when they last signed in, and the last four characters of saved keys, but not the keys themselves.

Cookies

The application sets only first-party cookies that it needs to work. If you have not signed in, a random identifier cookie (dl_anon, up to 30 days) keeps your document separate from other visitors’ documents. If you sign in, a session cookie (dl_session, up to seven days) keeps you signed in until you log out. This marketing site sets no cookies and uses no analytics or advertising scripts. To limit abuse, the application also uses IP addresses in memory for rate limiting.

Access to the instance

On the hosted application, each visitor’s document is private to that browser or account. If you run DocuLocate yourself in local mode, there are no accounts and a single shared active document, so anyone with access to that instance may be able to search, retrieve, replace, or remove it; deployment access controls matter, especially for sensitive files.

Your choices

You can explore this marketing demo without uploading anything. Before uploading to an application instance, understand its network access, whether sign-in is required, and whether an AI provider is in use. Review browser history on shared computers, and use the separate Reset and Clear history controls when you want to remove both server and browser copies.