FairqueryBlogToolsAboutSecurityllms.txt

Fairquery Privacy Notice

Last updated and effective: October 17, 2026

This notice explains what information Fairquery collects, how we use and share it, and your choices. It covers the blog at https://fairquery.github.io, Fairquery's tools, APIs, software and digital products, and messages you send us (together, the "services"). Platforms such as Apify, RapidAPI, Gumroad and GitHub have their own privacy policies.

Who we are. Fairquery is a brand name. The services are provided by the individual who operates the Fairquery brand as a sole proprietor based in Florida, USA, and any successor described in our Terms of Service (https://fairquery.github.io/terms/). "Fairquery", "we", "us" and "our" mean that operator. Contact: fairquery@proton.me.

1. The short version

Our Security page (https://fairquery.github.io/security/) describes in detail how each tool handles data. It describes current design and practice, not a guarantee.

2. What we collect, by product

The blog. The blog is a static site on GitHub Pages. It sets no cookies, runs no analytics, and loads no third-party scripts, fonts or embeds. GitHub logs visitors' IP addresses for security purposes under the GitHub Privacy Statement. We do not have access to those logs.

Free MCP tools and the VS Code extension. These run on your own machine. Fairquery code stores nothing from them and sends nothing to Fairquery. Some send queries directly from your machine to public services (for example, package names to OSV.dev). Your MCP client, editor or operating system may keep its own logs. Code hosts such as GitHub and npm see downloads; we see only aggregate statistics, such as download counts.

Apify Actors and paid MCP tools. Actors run in your own Apify account with your own Apify token. Your inputs and results are stored in your account's run storages under your Apify plan's retention. Fairquery's code is designed not to send them to Fairquery. Apify's Standard Actor Contract (or other end-user terms shown on the Actor's listing) applies, and under it Fairquery acts as a processor for you. Apify may give us limited information, such as aggregate usage and revenue statistics, runs you choose to share with us for debugging, and issues or reviews you post about our Actors.

RapidAPI APIs. Your requests pass through RapidAPI to a Fairquery-operated Apify Standby service. It processes each request in memory, returns the result in the response, and is designed not to write inputs or results to storage. We do keep:

RapidAPI and Apify also keep their own platform logs, which we don't control.

Gumroad purchases. Gumroad processes purchases as the seller of record and holds your payment details. Gumroad shares purchase information with us, such as your email address, the product, price, date and country, and other details you give at checkout. We do not receive your full payment card number.

Emails and support. If you email fairquery@proton.me, we receive your address, your message and any attachments. If you contact us through GitHub (issues or private vulnerability reports) or Apify, we see what you post and your public profile there.

Data about other people. Some tools process data about people: names you screen for sanctions, text you redact, email addresses you validate, or contact details returned by the website contact enricher, which may include named business email addresses and phone numbers published on public websites. You decide why and how this data is processed, and we process it only on your behalf to provide the service (see section 9 of the Terms). The tools are designed to process it per request or run, not to compile or keep a database of it.

3. How we use information

We use the information we hold to provide, secure and troubleshoot the services; enforce quotas, rate limits and our Terms and prevent abuse; deliver purchases and answer support and security reports; keep business, tax and accounting records; and comply with law and protect our rights and others'. We may use aggregate information, such as request counts, to improve the services.

4. How information is shared

5. No sale, no ad sharing, no AI training

We don't sell personal information, inputs or results. We don't share them for cross-context behavioral advertising or with third parties for their own direct marketing. We don't use your inputs or results to train AI models.

6. Cookies, analytics and Do Not Track

The blog sets no cookies and uses no analytics, advertising or tracking technology. We don't allow third parties to collect information about your activity over time and across websites through the blog, apart from the standard request data our host GitHub logs. Because the blog doesn't track visitors, it doesn't respond differently to Do Not Track signals: there is no tracking to turn off. Platform websites use their own cookies and handle these signals under their own policies.

7. How long we keep information

We keep information as long as we reasonably need it for the purposes in section 3, including legal, tax and record-keeping needs, and then delete it when practical. For example, support emails and purchase records may be kept for several years. Quota counters and request logs are kept as long as needed to run the service, under the retention settings of the platforms we use. Data in your Apify account follows your plan's retention, and you can delete it sooner. Copies may remain for a time in backups.

8. Security

We use reasonable measures to protect the information we hold, such as keeping data to a minimum, using platform access controls and keeping credentials out of code. No system is perfectly secure, and we can't guarantee that information will never be lost, accessed or disclosed without permission.

9. Your choices and requests

10. Children

The services are for business and professional use by people 18 or older and are not directed to children. We do not knowingly collect personal information from children under 13. If you believe a child has sent us personal information, email us and we will delete it.

11. International users

Fairquery is operated from the United States. Information is processed in the United States and in other countries where our platforms and their providers operate, whose data-protection laws may differ from those where you live.

12. Changes to this notice

We may update this notice. We will post the updated version on this page with a new date. For material changes, we will also make reasonable efforts to flag the change, for example on the blog. Where the law requires your consent to a change, we will ask for it.

13. Contact

Privacy questions and requests: fairquery@proton.me. Security issues: see https://fairquery.github.io/security/. Terms of use: https://fairquery.github.io/terms/.