Transparency
Transparency
How Libre is built to minimize retained data — and how we will report legal requests when there is something worth publishing.
Last updated · June 11, 2026
Why transparency looks different here
Most transparency reports are long tables of data handovers because the underlying product stored user data in the first place. LibreSearch is architected the other way: if we do not log searches or maintain accounts, there is often nothing responsive to a subpoena beyond “we do not have that record.”
That is a design choice, not a loophole. This page focuses on what we retain, what we would do if served legal process, and how you can verify the implementation.
What we retain (and what we do not)
LibreSearch
- Search queries: not stored as a user-attributed history.
- Accounts: none required; no profile database.
- Settings: client-side in your browser unless a feature explicitly says otherwise.
libreapps.xyz
- Contact form submissions: kept only as long as needed to respond.
- Standard server/hosting logs: may exist for security; not used for advertising profiles.
See Privacy policy for website specifics.
Legal and government requests
If we receive valid legal process, we will:
- Review it with counsel when appropriate.
- Produce only data we actually hold.
- Push back on overbroad requests where the law allows.
- Update this page when a disclosure affects users in a material way, when we are legally permitted to do so.
Published statistics
We will publish summary counts here after we have completed at least one reporting period — not before. Until then, the table below stays empty on purpose.
| Period | Requests received | Data disclosed |
|---|---|---|
| No reporting period completed yet. First entry will appear after we have real numbers to share. | ||
Verify in code
Policies are only as good as the code behind them. LibreSearch is AGPL-3.0. Clone the repo, read the request path, and file an issue if something does not match this page.