Skip to main content
AsreSEO
[LEGAL_COMPLIANCE // PRIVACY_DIRECTIVE]

Privacy Policy & User Data Protection

Last updated: October 8, 2026 • Effective immediately across all platforms, client portals & edge proxies

This Privacy Policy explains how AsreSEO, our agency platforms, and the GCP Personal OAuth Proxy & SEO Command Center ("Application", "we", "us", or "our") access, process, store, and protect your information when you interact with our website, request marketing consultations, or connect your Google Cloud Platform account to our edge SEO management systems.

[SECTION_01]

1. Platform Architecture & Identity

AsreSEO is an enterprise digital marketing, generative search optimization (GEO), and technical web architecture agency. Alongside our core consulting and search engineering services, we operate the GCP Personal OAuth Proxy & SEO Command Center (mcp.asreseo.com), a high-performance, edge-native SEO analytics dashboard and authenticated proxy built on Cloudflare Workers.

The Application acts as an edge proxy between your authorized client devices and third-party APIs (Google Cloud Platform, Google Search Console, Google Analytics 4, Bing Webmaster Tools). It is engineered to preserve tenant data sovereignty, zero-trust security, and zero external telemetry leakage.

[SECTION_02]

2. General Information Collected via Forms & Inquiries

When you use our contact terminal, book a strategic consultation, or initiate agency correspondence, we receive information such as your name, corporate email address, international phone number, website URL, and project specifications. Contractual correspondence may also include company registration details and billing addresses.

If delivering a contracted service requires administrative access to tools such as Google Search Console or your CMS, that access is used solely within the explicit scope of that engagement and revoked upon contract completion. Server log metadata (IP addresses, browser signatures, visited endpoints) is recorded strictly in aggregate for DDoS protection and edge performance routing.

[SECTION_03]

3. Google API Data Accessed & Scopes Requested

When you connect your Google Account via OAuth 2.0 to the Command Center or our automated reporting pipelines, the Application requests only the specific scopes necessary to deliver core SEO analytics and remediation actions:

Google Search Console API (webmasters.readonly)

Accesses search analytics performance data (clicks, impressions, average CTR, keyword positions), verified sitemaps, and URL inspection indexation telemetry to display SEO performance and detect keyword cannibalization clusters.

Google Analytics 4 Data API (analytics.readonly)

Accesses aggregated visitor metrics (sessions, engaged sessions, active users, conversion events) to correlate organic search rankings with real-world website conversions.

Google Drive API (drive.file)

Restricted exclusively to creating, managing, and organizing A4 executive PDF reports and audit spreadsheets within an application-managed "Client Vault" folder. The Application cannot view, modify, or access any other files in your Google Drive.

Google Docs & Sheets APIs (documents, spreadsheets)

Used only when you explicitly trigger an export action to create structured remediation briefs, keyword opportunity spreadsheets, and client pitch proposals.

Google Tasks & Calendar APIs (tasks, calendar.events)

Enables dispatch of actionable SEO remediation tasks (e.g. 404 error fixes, striking distance optimizations) and scheduling periodic quarterly SEO reviews on your calendar upon your explicit command.

Gmail API (gmail.send)

Used exclusively to transmit user-configured scheduled weekly executive summaries and critical anomaly alerts (e.g. sudden ranking or indexing drops) directly to recipients specified by you. The Application never reads, scans, searches, or modifies your inbox or existing emails.

[SECTION_04 // MANDATORY_COMPLIANCE]

4. Google API Services User Data Policy (Limited Use Compliance)

GCP Personal OAuth Proxy & SEO Command Center's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In strict adherence to Google's Limited Use requirements:

  • User-Facing Features Only: We only use access to user data to provide or improve user-facing features that are prominent in the requesting application's user interface.
  • No Third-Party Transfers: We do not transfer user data to third parties, unless necessary to provide or improve features, comply with applicable law, or as part of a merger/acquisition.
  • Zero Advertising Use: We do not use or transfer user data for serving advertisements, including retargeting, personalized, or interest-based advertising.
  • No Human Reading: We do not allow humans to read user data unless we have obtained your affirmative agreement, it is necessary for security purposes, or to comply with applicable law.
[SECTION_05]

5. Data Storage, Isolation & Retention

All OAuth credentials, refresh tokens, and session metadata are stored strictly in isolated, encrypted Cloudflare Workers Key-Value (KV) storage namespaces belonging to your deployed instance.

  • Encryption at Rest & in Transit: All communications between the Application, Google APIs, and your browser are strictly encrypted using TLS 1.3.
  • Ephemeral In-Memory Processing: Raw query results (Search Console analytics, PageSpeed diagnostics) are processed ephemerally in Worker memory and are not stored permanently on disk.
  • Token Lifetime: OAuth access tokens are refreshed automatically and kept only in your private KV store.
[SECTION_06]

6. Processors, Automation Clusters & Open-Source Nodes

To deliver our services we utilize trusted edge infrastructure providers (Cloudflare, Google Cloud Platform, GitHub). Processors only access data to the extent strictly necessary and operate under bound data protection agreements.

Furthermore, automated data pipelines, continuous SEO health monitors, and webhook integrations execute on our dedicated workflow automation engine hosted at n8n.asreseo.com. Automated ingestion, model routing, and image payload handling utilize our open-source custom n8n node developments authored by Ali Bakhtiari: n8n-nodes-avvalai and n8n-nodes-imagerouter. Workflows operating on our self-hosted n8n cluster process data in isolated sandboxes with strict zero-trust access controls.

Our open-source edge tools such as emdash-seo (WebABC SEO Suite) execute strictly in-process within local Cloudflare Worker boundaries without external telemetry data egress.

[SECTION_07]

7. Artificial Intelligence & Machine Learning Transparency

When optional Gemini AI technical audits or executive summary generations are requested via the Command Center or our consulting pipelines, data is processed ephemerally using zero-data-retention enterprise API endpoints.

CONFIRMATION: Your Google user data and private business telemetry are NEVER used to train, retrain, improve, or fine-tune generalized machine learning models, foundation models, or third-party AI systems.
[SECTION_08]

8. User Rights, Revocation of Access & Data Deletion

You retain full control over your credentials, personal information, and stored SEO telemetry at all times:

  • Revoke Access via Google: You can immediately revoke the Application's access to your Google Account at any time by visiting Google Third-Party Account Permissions.
  • Purge Local Storage & KV Tokens: You can clear all cached credentials and stored telemetry directly from the Application's Settings panel or by purging the Cloudflare KV namespace.
  • Data Subject Rights (GDPR / CCPA): You have the right to request a complete copy of any data we hold about you, correct inaccurate records, or demand permanent erasure by emailing us.
[SECTION_09]

9. Cookies Policy

This website uses minimal essential cookies to preserve user preferences and ensure security against automated CSRF attacks. We do not use intrusive third-party cross-site advertising cookies. You can disable cookies at any time in your browser settings.

[SECTION_10 // CONTACT_INQUIRIES]

10. Contact & Privacy Officer

For any legal, privacy, or Google API compliance inquiries, please contact our data controller directly:

Organization: AsreSEO & GCP Personal OAuth Proxy

Principal Engineer & Maintainer: Ali Bakhtiari

Primary Email: info@asreseo.com

Developer Email: ali.bakhtiarii@gmail.com

WhatsApp & Support: +1 (346) 327-2878