Data Protocol

SEOGOD ingests technical search data through Google OAuth only after a user authorizes access. We request read-only access to Google Search Console and Google Analytics 4 so the platform can show search visibility, traffic context, ranking opportunities, proof reports, and prioritized SEO fixes for the websites connected by that user.

• Search Console: search queries, pages, impressions, clicks, average position, and click-through metrics.
• Analytics: traffic, engagement, channel, page, and conversion context available through the selected GA4 property.
• Website ingestion: we crawl public HTML to audit title tags, headers, internal links, structured data, and semantic structure.

Data is processed to generate SEO audits, content recommendations, patch suggestions, visibility reports, and owner-ready summaries. Some website and performance context may be sent to trusted AI infrastructure providers to generate these recommendations. Google user data is not sold, used for advertising, or used to train SEOGOD-owned AI models.

SEOGOD's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google data only to provide and improve user-facing SEOGOD features requested by the user, such as Search Console insights, Analytics summaries, SEO prioritization, reports, and proof-backed recommendations.

We do not transfer Google user data to third parties except as necessary to provide or improve those user-facing features, comply with applicable law, protect against security abuse, or as part of a merger, acquisition, or sale of assets with continued privacy protections.

OAuth tokens and sensitive credentials are encrypted at rest and are only used by server-side SEOGOD systems. We keep reporting and audit records only for as long as needed to operate the account, provide historical proof, resolve support requests, and meet legal or security obligations. OAuth tokens are deleted when a user disconnects Google access or closes the related account.

• Tokens: deleted on disconnect or account closure.
• Audit records: retained for historical mapping and proof until account termination unless a longer legal or security need applies.
• Patches: stored until manual deletion or account closure.

Users retain control over connected data sources. You may revoke Google access at any time through SEOGOD, through your Google Account security settings, or by removing SEOGOD's access in Google Account permissions. Requests for data export, deletion, account termination, or Google OAuth disconnection can be sent to the support address below.

SEOGOD uses infrastructure and processing providers to operate the platform, including Supabase for database and authentication, Vercel for hosting, Resend for transactional email, Razorpay for payments, Google APIs for authorized search and analytics data, and AI infrastructure providers for SEO recommendations. These providers process data only as needed to run SEOGOD features, secure the service, or satisfy legal obligations.

SEOGOD uses essential cookies and session storage to keep users signed in, protect OAuth state, remember portal preferences, and secure the dashboard. We do not use advertising pixels inside the SEOGOD dashboard.

We may update this policy as SEOGOD changes. Material updates will be reflected on this page and, when appropriate, communicated through the account email or dashboard. If our Google data use changes in a meaningful way, users will be asked to review the updated policy before that new use begins.