Privacy Policy

Last updated: June 27, 2026

1. Optional browser analytics: removed

• This site loads no optional browser analytics. There is no Google Tag Manager, no Google Analytics, and no Cloudflare Web Analytics beacon.
• No project-inserted optional analytics or tracking scripts run on these pages.

2. Hosting and infrastructure

• The site and API are served through Cloudflare's hosting, CDN, and security infrastructure.
• As part of delivering and protecting any web service, that infrastructure may process necessary request, network, security, and diagnostic data (for example connection metadata and request routing/abuse-protection signals). This is standard operational processing by the hosting provider, not optional analytics inserted by this project.
• We do not claim that "no logs" or "no infrastructure processing" exist. Such operational processing is governed by the hosting provider's own terms and policies.

3. Browser storage used by site features

Some interface features store small values in your browser's localStorage on your own device. This is local to your browser, not a server-side account database, and is not transmitted to us as an analytics signal:

• Favorites — entities you mark are kept locally (ai-nexus-favorites).
• UI state — expand/collapse state of page sections (section-*).
• Technical cache / fallback — a data-source partition list (_vfs_partitions) and a degraded-entity marker (degraded_entities) used to load and recover catalog data efficiently.

You can clear this at any time from your browser's site-data controls. It lives only on your device.

4. API and MCP requests

• When you call the public API or MCP server, the request parameters you send (such as your query and filters) are processed to produce a response. We do not claim that request content is never processed.
• The API and MCP server require no account and no API key, so requests are not tied to a stored user identity by this project.
• We do not state a fixed retention period for request data here. Operational handling of requests at the infrastructure level is governed by the hosting provider's policies.

5. Optional aggregate telemetry (code contract)

• The codebase contains optional, route-local aggregate telemetry. It is disabled unless explicitly enabled by deployment configuration.
• Where it is enabled, its schema is constrained to aggregate signals only. The schema prohibits recording request bodies, prompts, raw queries, cookies, IP addresses, geolocation, user-agent strings, and raw referrers.
• This section describes the code contract only. It does not assert whether this telemetry is enabled or disabled in any particular production deployment.

6. How we use information

• We do not run optional browser analytics and do not maintain user accounts, so there is no profile of you to sell, share, or transfer.
• Request handling exists to answer API/MCP requests and to keep the Service available and protected from abuse.

7. Open Source

Free2AITools is open source. You can audit our data handling by reviewing the source code.

8. Changes

We may update this policy. Changes will be posted on this page with an updated date.

9. Contact

Privacy questions: GitHub Issues