Planet reader privacy

Information the reader handles

When you select Start, the reader accesses the chosen signed-in desktop Planet book. It collects the supported Veteran and Plus records, source fields, notes and comments, CRM history, original form content and original images.

These records can contain names, phone numbers, email addresses, dates of birth or ages, physical addresses, relationships, occupation, assignment information, identifiers and security-related source fields. Forms, notes and images may also contain personal communications, health information, financial information or other sensitive personal information. The reader preserves source content; it does not claim to remove sensitive fields.

The reader also handles source URLs, the selected book connection, read identifiers, timestamps, progress, errors and integrity checks needed to complete and recover the read. A book's native Me mapping helps bind the read to that book; it does not independently verify the identity of the Planet account holder.

You sign into Planet directly. The reader does not ask for your Planet login password or verification codes and does not copy or export session cookies. It uses the browser's existing signed-in session for requested page and original-file reads. Source records may independently contain security-related information.

The reader does not monitor unrelated browsing or record general mouse movements or keystrokes. Its production package has no advertising or analytics integration.

Local capture, transfer and Save

Reader 1.6.18 encrypts retained local captures, original files and capture recovery metadata. Your GMT sign-in authorizes a limited unlock session through GMT's server. Unlocking requires an internet connection. Capture keys are kept in the extension's memory while unlocked and are not saved as unwrapped keys in local browser storage. GMT manages the account keys on its server.

Earlier developer captures can remain in their previous storage until you explicitly confirm which GMT account should own them and migrate them into encrypted storage. Migration verifies the encrypted copy before removing its previous local entries. This is not a claim of forensic erasure of browser or device remnants. Historical developer pairing settings are separate from this capture migration and are not used by the production reader.

When a read started from GMT completes and passes its checks, the records and original bytes automatically become available to the signed-in GMT Scrape page in browser memory. This happens before backend Save. You can also explicitly receive an earlier completed capture.

Selecting Save leads in GMT uploads the capture and originals to GMT's authenticated application server and connected Supabase database and storage services. Original-file uploads can go directly from the browser to that backend. The reader requests source pages and originals from Planet and its image-hosting services.

The reader does not place calls or update Planet business records. Checking setup does not start a scrape.

Purpose and Limited Use

GMT limits its collection, use and transfer of reader data in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.

GMT uses captured data only to provide or improve the disclosed reader purpose and the user-requested capture workflow, including necessary maintenance, security and reliability. GMT does not sell captured data, supply it to data brokers or advertising platforms, use it for personalized advertising, or use it to determine creditworthiness or for lending.

Transfers to service providers must be necessary for that purpose and described in this notice. Other transfers are limited to legal obligations, protection against fraud or abuse, or a merger, acquisition or asset sale after the user's explicit prior consent.

GMT personnel may read specific user data only with explicit consent for that data, when necessary for security, or when required by law. Aggregated, anonymized information may be used for internal operations under the policy's conditions. Asking for support does not authorize opening a complete lead book.

Retention and deletion requests

Local captures can remain after another read. This release has no automatic age-based expiry for reader captures or saved capture data. A failed or stopped attempt remains incomplete; an earlier completed capture can remain available separately.

Removing the extension can remove its local storage. It does not erase exports already downloaded or data saved in GMT. Archiving or deleting earlier records from active work does not permanently erase their originals or history. Saving a newer capture does not erase the earlier source evidence.

You can request access to or deletion of reader captures and saved capture data at neumanic2@gmail.com. Requests are handled manually. GMT will verify your authority over the relevant account and data, review the request, and explain what was removed and what remains retained.

The app currently has no complete account-erasure button. GMT will not describe archiving as permanent deletion or claim to remove downloaded copies outside its control.

Support and privacy contact

Contact Nicolas Neumann at neumanic2@gmail.com. Do not attach passwords, verification codes, security keywords, original lead images or complete lead exports to an initial email. See reader support for setup and troubleshooting.