Privacy Policy.
What AgAgentHub collects, how we use it, and what our read-only Google Search Console integration does.
Effective October 22, 2026
About AgAgentHub
AgAgentHub is an independent website that describes publicly documented agricultural AI projects and use cases. Most pages can be read without an account. The editorial review and administrative tools are restricted to the site owner. Public use-case submissions are currently paused.
Information we handle
- Website requests: Our hosting and infrastructure providers may process the IP address, browser and device information, requested URLs, request time, and technical logs needed to serve and protect the site.
- Private owner access: Supabase provides authentication for the private editorial and CEO workspaces. This may involve the authorized account email, sign-in records, authentication tokens, and browser storage needed to maintain a session.
- Project documentation: The site stores information from public repositories, project pages, and other sources used in its editorial workflow. We do not ask visitors to provide farm records or field-level operational information.
- Existing submissions: Submissions made while earlier contribution features were available may remain in the private editorial database. New public submissions are currently disabled.
Google Search Console access
AgAgentHub's owner may authorize a private, scheduled indexing monitor using Google OAuth. The integration requests only the https://www.googleapis.com/auth/webmasters.readonly permission, which allows read-only access to Search Console information for properties the authorizing account can access.
The monitor checks publicly published AgAgentHub article URLs with Google's URL Inspection API. It can receive and store an article URL, Google's indexing verdict, coverage and fetch status, indexing restrictions, last crawl time, an inspection link, and the time of the check. These observations help the owner identify pages that are not indexed or have a reported issue.
OAuth client credentials and the owner's refresh token are intended to be stored as private server-side settings in Netlify; they are not part of public website pages. The monitor exchanges the refresh token for short-lived access tokens as needed. It does not ask ordinary visitors to sign in with Google, access visitors' Google accounts, submit URLs for indexing, or change Search Console settings.
Limited use: We use Google Search Console information only to monitor and troubleshoot indexing for AgAgentHub. We do not sell Google user data, use it for targeted advertising, or use it to train AI models. We do not give external AI providers access to Google OAuth credentials or the indexing results through this monitor.
Service providers and notifications
We rely on service providers to operate AgAgentHub. These currently include Netlify for hosting and server-side functions, Supabase for application data and private authentication, and Google for Search Console data when the owner connects it. Our automated editorial workflow also uses AI services for publicly sourced project analysis and drafting; the Search Console monitor does not send Google data to those services.
When indexing monitoring is enabled, the system may send an alert to the owner's designated Discord channel containing the published article URL and Google's reported indexing problem or delayed status. These alerts are not intended to contain the Google account email, OAuth tokens, private credentials, or visitors' personal information. Data shared with service providers is subject to those providers' own privacy practices.
Cookies and browser storage
Restricted owner pages may use browser storage for Supabase authentication. Infrastructure providers may use cookies or comparable technical mechanisms needed for delivering and securing the service. The current website does not depend on visitors signing into a Google account.
Retention and security
We retain public editorial records and private operational or indexing records while they are useful for running, auditing, or securing the project. No fixed automatic deletion period is currently configured for Search Console indexing observations. Hosting and authentication logs may have different retention periods determined by their providers and settings.
We limit access to private database records and OAuth credentials and use encrypted connections to service providers. No online system can be guaranteed completely secure. If a Google OAuth grant is revoked, the indexing monitor can no longer use that grant to obtain new access tokens.
Your choices and questions
Google account holders can review or revoke third-party access through Google Account connections. Revoking the grant stops future authorized Search Console checks until the owner reconnects it; previously recorded indexing observations are not automatically erased.
For questions about the private Google integration, use the support contact shown on AgAgentHub Search Monitor's Google OAuth consent screen. AgAgentHub does not currently offer a general public contact form. Please do not post passwords, OAuth tokens, or other sensitive account information in public channels.
If you have a concern about an article's sources or accuracy, consult our review process. Depending on your location, you may have additional rights concerning your personal information.
Changes to this policy
We may update this page as AgAgentHub's features, providers, or data practices change. The effective date above will change when a material update is published.