Privacy

GovBot Soils privacy

GovBot Soils sends bounded location and soil-query requests to USDA NRCS to prepare source-cited soil-survey briefs. You do not need to provide personal information to use it.

What is sent to USDA NRCS

Coordinates, bounded areas, map-unit keys, and fixed interpretation requests are sent to USDA NRCS Soil Data Access (SDA), a fixed public agency endpoint. USDA NRCS handles those requests under its own practices.

No account or key

There is no sign-in, no user account, and no source API key. You do not need to provide your name, email, or other personal information to use GovBot Soils.

Request caching

Agency source responses, and the query keys that contain the public research inputs for each lookup (the coordinates, area or search parameters used), are held in bounded process memory. A source response is eligible for reuse for 10 minutes after retrieval. This limit governs reuse, not deletion: an expired entry may remain in memory until a later lookup of the same key, replacement or capacity eviction, or process exit. There is no application database.

Operational logging

The runtime does not intentionally persist conversation text or query bodies. The service runs on Google Cloud, and Google Cloud keeps operational HTTP request logs. These logs can include IP address, request path, timestamp, status, latency, and user agent. They are retained for 30 days under the configured retention setting.

Support email

If you email hello@govbot.ai, your message is retained until manually deleted. There is no fixed deletion schedule.

OpenAI and ChatGPT

If you use GovBot Soils through ChatGPT, OpenAI handles your conversations under its own, separate privacy practices. GovBot Soils does not control them.

What not to send

Do not send home addresses or confidential or sensitive personal information. Coordinates or areas are enough for soil-survey requests.

Contact

Questions about privacy: Ideation Lab, Corp. — hello@govbot.ai