1. Data-minimization principle

GVGEO is built so that a feature sends only the information reasonably needed to perform that feature. External providers are not all contacted on every request. The exact provider can depend on which integrations are configured by the service operator and which feature you choose to run.

This page describes product data flows, not the independent retention or model-training policies of external providers. Those policies are governed by each provider’s own terms and privacy documentation.

2. Website audits

InputPublic URL, public HTML/resources, robots.txt, sitemap and audit options.

DestinationGVGEO server-side audit engines and the public website you asked us to fetch.

Stored resultAudit status, findings, scores, evidence, timestamps and project/report history where applicable.

Audits are designed for publicly accessible resources. GVGEO’s URL-safety controls reject private/local network destinations and do not intentionally bypass authentication walls.

3. Live AI Visibility

InputQuestion text, brand/domain, optional competitor context, language/country and run identifiers needed for the selected provider.

Possible providersConfigured retrieval services such as Bright Data or Cloro, which may interact with supported AI/search platforms.

Stored resultProvider status, answer text or structured result where available, brand/competitor mentions, citations, timestamps and usage records.

A provider error is stored as an error/unavailable state rather than being silently converted into “brand not mentioned.”

4. AI question generation and Content AI

InputProject/domain context, instructions, selected public-page content and the material needed to create questions or a draft.

Possible providersConfigured model services can include Google/Gemini for question generation and OpenAI or Anthropic for Content AI workflows.

Stored resultGenerated question sets, content drafts, usage records and workflow status when the feature saves them to your account.

Do not place passwords, private customer records or unrelated confidential information into prompts or public-page content submitted for optimization.

5. WordPress connector

Sent from WordPressPairing data such as site URL, project ID/connector version, authentication token on later requests and deployment status/results.

Sent to WordPressOnly the reviewed deployment job: supported technical file payloads, approved content draft, target URL and job metadata required to execute or roll back.

Not requiredYour WordPress administrator password. Supported raw AI-crawler request logs remain local to the connector and are not uploaded.

Connector tokens authenticate the paired site and should be treated as secrets. Disconnecting a project revokes the GVGEO connection for that site.

6. Payments through PayPal

Shared for checkout/reconciliationPlan, billing cycle, amount, currency, local order reference and provider subscription/payment references.

Processed by PayPalPayment credentials and PayPal account/payment-method information.

Stored by GVGEOOrder/subscription status, provider references, payment/refund events and timestamps needed for entitlement, reconciliation and support.

GVGEO does not store your full card number or PayPal password.

7. Email delivery and optional OAuth login

Verification, password-reset and account messages may be sent through a configured email provider such as Brevo or SMTP, which requires the destination email and message content. If you choose Google or GitHub OAuth, the selected provider handles the login authorization and returns the identity information required to link or sign in to your GVGEO account.

8. Your controls

You choose when to run paid AI checks, request AI-assisted content, connect WordPress and approve deployment jobs. You can disconnect WordPress and cancel future automatic renewal from supported account controls. For deletion or privacy requests that do not yet have a self-service control, use the contact page.

Third-Party Services & Data Processing