Email address, a Google or GitHub account identifier supplied through sign-in, session data, session expiry, and account creation time. The current sign-in session expires after 30 days or when you log out.
DATA PRIVACY
Clear about what GeoVouch processes.
Last updated September 11, 2026 · Applies to the hosted GeoVouch service at geoguru.xyz.
What we process
Website URLs, prompts, chosen models and settings, analysis task status, generated answers, extracted entities, cited URLs, search-derived evidence, reports, and timestamps.
Credit purchases are taken on Stripe's own hosted checkout. Card numbers never reach GeoVouch. We store the Stripe session, payment, and event identifiers, the pack purchased, the amount and currency, and the time — enough to prove a payment happened and to credit the right account.
A random visitor identifier and a small fixed set of workflow events, such as analysis creation, model selection, sign-in completion, run completion, and results viewing. These events do not include submitted prompts, target URLs, model answers, emails, OAuth identifiers, IP addresses, or browser user-agent strings.
If you use the Quick Feedback form: the category, your message, the page you were on, and an email address — taken from your account when you are signed in, or whatever you type when you are not. We reply by email and keep the thread there.
Records of failures — the error message, where in the service it happened, and the account involved if there was one — kept so a fault can be found and fixed after it happens. An error message can contain a fragment of whatever was being processed. GeoVouch does not intentionally ask for passwords, payment cards, or sensitive personal data.
The shared prompt corpus
Prompt Result Analysis contributes to a corpus that every user's analysis draws on. When you run a prompt analysis, we store the prompt text, the models and search mode used, the ranking of products named in the answers, and the URLs those answers cited. Those records carry no account or visitor identifier, and they do not include the model answer text.
This is what makes cross-prompt comparison and near-duplicate prompt suggestions possible: they are evidence about how models answer a question, not a record of who asked it. Two consequences worth stating plainly. Other users can see a prompt you ran, though not that you ran it — so treat a prompt as public, and do not put confidential or personal information in one. And because the corpus is not linked to you, deleting your own analysis task does not remove its contribution; re-running a task replaces its own contribution rather than adding a second.
Why we use it
- Provide Google or GitHub sign-in, save analysis tasks, and show their current results and history.
- Run the requested website, search, citation, and prompt-result analyses.
- Take payment for Credits and keep an accurate balance and ledger.
- Measure aggregate workflow completion and identify reliability or usability problems without recording the content of submitted analyses in product-usage events.
- Keep the service secure, prevent abuse, debug reliability issues, and meet legal obligations where applicable.
GeoVouch does not sell analysis inputs or account data, and does not use customer inputs to train its own model. Third-party providers process data under their own terms and privacy notices.
Where data is stored and processed
Hosted storage. Supabase is the primary application-data store, running managed PostgreSQL in AWS us-east-2. The application connects as a restricted database role whose access is constrained by row-level security, so a request can only reach the records belonging to its own session.
Model processing. OpenRouter is the sole LLM access provider. For a requested model analysis, the relevant prompt and necessary analysis context are sent through OpenRouter to obtain a response. Model providers reachable through OpenRouter may process requests according to their own policies.
Search processing. Serper is used to retrieve Google search results for External GEO and Share of Voice. The search terms sent are generated from your analysis target; results are cached for a limited period to avoid repeat queries.
Payment processing. Stripe processes card payments on its own hosted checkout page and sends GeoVouch a webhook confirming the result.
Sign-in processing. Google and GitHub sign-in are brokered by Supabase Authentication. GeoVouch receives the account information required to establish and maintain your session; provider credentials are not stored by GeoVouch.
Hosting. The application itself runs on Vercel.
Retention and deletion
Signed-out visitors. Records created without an account are tied to a guest session that expires 7 days after its last use. Once it expires, those records are no longer reachable by anyone using the service and are removed by a periodic purge.
Accounts and analyses. Account records, analysis tasks, and their results are kept while the account exists, so that your history stays available to you. Email support@geoguru.xyz to request deletion and we will remove them.
Purchases. Purchase records and the Credit ledger are retained as financial records, independent of an account deletion request, for as long as required for accounting and tax purposes.
Error records. Kept for a short diagnostic window and then deleted.
Shared corpus. Corpus records carry no identifier linking them to you, and are retained as long-running evidence about model behaviour. See the section above before submitting a prompt.
Choices, security, and changes
You can use GeoVouch without an account until a Credit-bearing action requires one. To request access, correction, export, or deletion of your data, email support@geoguru.xyz.
Session cookies are HttpOnly and SameSite=Lax, and are marked Secure in production. Connections to the database verify TLS against Supabase's root certificate. No security control eliminates all risk, so please do not place secrets or sensitive personal information in an analysis prompt or target URL.
We will update this page before any material change in processing, storage, subprocessors, or retention. The revised date at the top identifies the current version.