> For the complete documentation index, see [llms.txt](https://visi-digital-internasional.gitbook.io/geo-prospector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visi-digital-internasional.gitbook.io/geo-prospector/release-notes/6.7.25.1.md).

# Version 6.7.25.1

Released **24 July 2026**.

Geo Prospector Established Edition 6.7.25.1 improves geographic targeting, plan capacity, category relevance, zero-result handling, progress accuracy, and secure runtime packaging.

## Structured location targeting

* Country → Province/State → City targeting is available through the expanded location hierarchy.
* Country-level and province-level searches continue through structured geographic query plans.
* The selected target category remains canonical while geographic coverage expands.

## Plan limits

| Plan       | Maximum data per search |
| ---------- | ----------------------: |
| Free       |                      50 |
| Starter    |                     500 |
| Business   |                   1,000 |
| Enterprise |                   5,000 |

## Category and empty-result handling

* Controlled related-category matching improves useful Google Maps coverage.
* Unrelated categories remain excluded.
* Candidate exhaustion is handled as a valid completed state instead of a fatal exit-code error.
* Empty valid searches display a clear no-result message.

## Progress and credits

* Progress reflects valid saved rows.
* Zero valid rows no longer appear as a completed target result.
* Credit usage is based on valid rows loaded into the application.
* Empty valid searches consume zero lead credits.

## Secure runtime

This release includes:

* Established public verification key
* Signed security-anchor manifest and signature
* Device-bound activation
* Clock rollback protection
* Bundled Node.js runtime
* Bundled Playwright Chromium
* Protected Python Email Finder backend

The private signing seed remains outside the project and is not included in the installer.

## Installer verification

| Property                     | Value                                                              |
| ---------------------------- | ------------------------------------------------------------------ |
| Installer                    | `GeoProspectorSetup.exe`                                           |
| Size                         | `273765875 bytes` (261.08 MiB)                                     |
| Installer SHA-256            | `49ACD03FDAEC621B9CFD5A45FB9CF51F90BC55197DE8381C37A072192BDE519F` |
| `geo_prospector.exe` SHA-256 | `A56DA0086E84B6FB4D58D40C07CA1E5A9F47C73113330AA77B36C68F116122EE` |
| `data/app.so` SHA-256        | `5291341EB9DC45BA5414C82FC18766F5AA70E5CE8BDC0C66065C74E445856480` |

* [Download the installer](https://github.com/visi-digital-internasional/geo-prospector-update/releases/download/v6.7.25.1/GeoProspectorSetup.exe)
* [View the GitHub release](https://github.com/visi-digital-internasional/geo-prospector-update/releases/tag/v6.7.25.1)
* [Read the update guide](/geo-prospector/updates-and-security/updating.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://visi-digital-internasional.gitbook.io/geo-prospector/release-notes/6.7.25.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.