Privacy Policy

The short version

FireFetch is a desktop application. Your Firestore data is read from and written to Google's servers directly by the application running on your computer. It does not pass through us, because we are not in the path.

We operate one server-side service: licensing. It exists to know which plan you are on and how many writes you have used. It is designed so that it cannot learn which Google Cloud projects you work on.

What never reaches us

• The contents of your Firestore documents
• Your queries, scripts or their results
• Your Google account credentials or service-account keys
• The names or IDs of your Google Cloud projects and databases
• Your Firebase Authentication users

Credentials are stored locally, encrypted with a key held in your operating system's credential store — Keychain on macOS, Credential Manager on Windows, Secret Service on Linux.

What the licensing service stores

To operate a paid product, we hold:

• Your account — the email address you signed up with, and a hash of your password
• Your plan — tier, billing period dates, and status
• Usage counts — how many writes have been recorded against each database you have marked premium, and against your free allowance

How databases are identified

This is the part worth understanding, because it is the part most services get wrong.

When FireFetch needs to report usage for a database, it does not send us the project ID or database name. It computes a keyed hash of them —HMAC-SHA256, using a secret salt belonging to your account — and sends that opaque value instead.

The consequence is structural rather than a promise: the licensing service holds identifiers it cannot reverse, and which differ between accounts even for the same project. It cannot enumerate your projects, correlate two customers working on the same project, or tell anyone what you are building.

Reads are not tracked

FireFetch does not meter reads, so it does not report them. Browsing and querying generate no usage records of any kind.

Payments

Payments are handled by a third-party payment processor. We do not receive or store your card details. The processor's own privacy policy governs what it collects.

The MCP server

FireFetch's Model Context Protocol server runs locally and listens on loopback only. It is not exposed to your network or to us.

If you connect an AI assistant to it, data that assistant reads is sent to whoever operates that assistant, under their privacy policy — not ours. That is a decision you make per database, and the read-only default is there to make it a deliberate one.

Analytics and tracking

This website uses no advertising trackers and sets no advertising cookies. The application does not report your activity to us.

Your rights

You can ask us what we hold about your account, correct it, export it, or delete it. Deleting your account removes your account record and usage counters. Email[email protected].

Changes

If this policy changes in a way that affects what we collect, we will say so rather than quietly updating the date at the top.

Contact

Questions about privacy: [email protected].