Privacy Policy

Crawlvero is an independently operated project, not a claimed registered company. The owner plans to operate from Egypt as an individual. Confirmed public legal identity and applicable contact details remain to be completed before this draft becomes effective. Use the Contact page for the configured support and privacy channel; do not send credentials or identity documents unless a specific, necessary verification method has been agreed.

GA4, Bing Webmaster and Yandex Metrica have completed an owner-account connection and import check. This is not public Google verification or a guarantee that every customer account is eligible. Each provider requires separate consent and selection of an existing resource for the authorized site. These connections do not install tracking tags or create provider resources.

GA4 requests analytics.readonly, lists accessible properties and imports daily Organic Search sessions, users, page views and engaged sessions, with report dates and provider quality metadata. Bing requests webmaster.read and imports search clicks and impressions across Bing verticals, not a domain authority score. Yandex requests metrika:read and imports daily organic visits, users and page views using lastTrafficSource attribution, preserving sampling information.

Provider credentials are encrypted server-side and are not returned to agents. Saved reports are scoped to the site's workspace. Authorized agents can read reports only through supported tools and permissions; tool availability differs between clients. Daily users are not additive across dates, an empty organic report does not mean no total traffic, and an import date range is not a retention period. The 90-day GSC retention target does not automatically apply to these additional providers.

The service may process account and workspace details, user preferences, URLs and page content requested for audits, crawl and performance observations, findings, reports, job telemetry, security logs, usage measurements, and integration metadata.

Data is used to authenticate users, isolate workspaces, run requested audits, generate evidence and reports, enforce quotas, prevent abuse, diagnose failures, measure service cost, and synchronize an authorized billing or integration state.

Optional Google sign-in requests openid, email and profile to identify the account and support sign-in or explicit account linking. This can include your Google account identifier, email and verification status, name and profile image. Crawlvero does not receive your Google password. Signing in does not connect Search Console or grant access to Analytics, Gmail or Drive.

Google sign-in tokens are used to verify the sign-in response and are not retained in the linked account record. The account identity and Crawlvero session are separate records. The optional Search Console connection, unlike identity-only sign-in, stores an encrypted refresh token for authorized later synchronization.

The separate Search Console connection requests read-only access (webmasters.readonly). After your consent, it reads the list of accessible Search Console properties and their permission levels to match a property to the selected site. The current adapter selects the matching resource; check the displayed property before requesting synchronization.

An authorized background synchronization reads search-performance records for a bounded date range: dates, queries, page URLs, countries, devices, clicks, impressions, click-through rate and average position. Stored records support the site's Search Console reports. Connecting alone does not launch an audit or a synchronization. This access does not change your site, Search Console settings or ownership, and does not submit URLs for indexing.

A refresh token is encrypted on the server so an authorized later synchronization can obtain short-lived access without another sign-in. Tokens are not returned to dashboards, agents or normal application logs. Public Google verification is still pending; additional provider data flows are described separately in this draft.

Site reports and integration records belong to the selected workspace and are available according to server-enforced membership and permissions. They are not visible to every Crawlvero user. An authorized AI client can receive only the data supported by its tools and granted scopes, when requested; connecting an AI client is a separate permission from connecting Google.

Using an external chat or agent can send the returned report data to that provider, which processes it under its own policies and your settings. The current remote report exposes Search Console connection status, not a complete Search Console reporting integration. Crawlvero does not send integration credentials to these clients. Do not connect an agent unless you intend it to receive the supported workspace data.

The proposed operating policy limits Google data to providing and improving the user-facing functions for which access was granted. It excludes sale of Google data, advertising targeting, unrelated cross-customer profiling and training general-purpose AI models. Any permitted transfer must comply with the Google API Services User Data Policy, including its Limited Use requirements. These commitments require operator approval before this draft becomes effective; this text does not certify Google approval.

The current deployment runs application processes on the operator's computer, reached through Cloudflare Tunnel over HTTPS. The active application database is local PostgreSQL on the operator's computer. A historical database copy remains on Neon. Encrypted recovery archives are configured for synchronization through the operator's Google Drive; the recovery key is kept separately. Resend handles configured service email and support receipt. Google handles identity and separately authorized Search Console requests. Paddle is currently used in Sandbox; real-money billing is not enabled.

These providers process data required for their respective functions. Requested audits also contact the target websites. Confirm the applicable processing locations, international-transfer basis, contractual roles and final provider inventory before adopting this policy; do not assume all processing remains in Egypt or on one computer.

Connecting a customer's Search Console or future analytics provider is for that customer's site and workspace. It does not enroll the customer's data in Crawlvero's own visitor tracking. Our own site measurement and private product-usage reporting are a separate workstream, not a completed analytics deployment. Any new collection needs a defined purpose, minimal fields, retention and applicable notice or consent before activation.

Necessary session and preference storage supports sign-in, locale and appearance. This draft does not authorize advertising trackers or a marketing mailing list. Customer queries, complete URLs, findings, chat text and integration credentials are not intended as payloads for our external visitor analytics.

The Search Console disconnect removes that site's stored connection and encrypted refresh token once no synchronization is running or waiting for a retry. It does not automatically erase previously imported metrics, completed reports or backups, and it does not revoke the Google-side grant. You can separately remove Crawlvero's access in your Google Account. Because sign-in and Search Console use the same Google Cloud project, Google-side revocation may also affect linked Google sign-in; keep an alternative sign-in method available.

The separate Delete imported GSC data action requires site-management permission and confirmation of the selected site. It removes that site's imported GSC metric rows and stored connection credential from the active database. The action is unavailable while a synchronization is running or waiting for a retry. It does not delete your account, other sites, technical audits, job and run history, or existing backups, and does not remove data held by Google or revoke Google's grant.

Deleting GSC data is not account-wide erasure. A successful deletion stores a minimal receipt in the active database: the affected site/workspace, time, counts and requesting account where available, without Google queries or credentials. For access, correction or broader deletion, use the Contact page and identify the relevant account and site without sending passwords or tokens. A verified request-handling process and any legally required exceptions still need approval before this policy becomes effective.

The date range selected for an import or report is not a retention period. The selected target for imported GSC metric history is 90 UTC calendar dates. Age-based maintenance is implemented but currently disabled, so there is no automatic age-based expiry in operation. Disconnecting alone leaves stored metrics. Activation and the effective retention policy still require approval.

Encrypted backups are local. A 30-day target has been selected separately; the manual operator tool requires a reviewed list and explicit confirmation before deleting expired copies. It preserves at least two verified copies and copies held for recovery. No scheduled backup expiry is enabled. Holds, failed integrity checks, downtime and pending approval can delay deletion; this draft does not promise an exact maximum age or immediate deletion of every copy.

Deleting data from the active database does not alter existing backups. The recovery tool refuses a backup containing GSC data unless the operator explicitly chooses to discard all GSC metrics and connection credentials from the restored copy; old GSC imports are not replayed. This does not erase the source archive or provide general account-wide deletion during recovery. Request handling and recovery from a copy outside the operator's computer remain release requirements.

Crawlvero uses workspace authorization, encrypted provider refresh tokens, protected sessions, SSRF controls and bounded background jobs. Authorized operators may need limited access for a specific support or security purpose; access to Google data must comply with the applicable provider policy. These controls are not a guarantee of uninterrupted availability or an independent security certification.

The service is intended for business and professional use, not for children. Material changes to the effective policy will be communicated through an appropriate product or contact channel once those channels are operational.