SEO Portfolio Local privacy notice
Last updated: 30 September 2026
This notice covers the Google Search Console connection used by the private SEO Portfolio dashboard and self-hosted OpenSEO installation operated by Kiril Papaz. Privacy contact: papaz_no1@yahoo.com.
Information accessed
When you connect Google, the application receives authorization tokens and reads the Search Console properties your account can access, including property identifiers and permissions. For properties you select, it can read search-performance metrics and breakdowns, including queries, pages, dates, countries, devices, clicks, impressions, click-through rates, and average positions. OpenSEO can read available URL-inspection results and basic Google identity details, such as account identifier, name, and email, to identify the connected account.
The current Search Console connection requests read-only access. This notice does not authorize future access to Gmail, Drive, or other Google services. Any additional Google integration requires its own disclosure and permission request.
Purpose
Google data is used to connect your authorized website properties, display search performance, investigate indexing, and produce reports or analyses you request within the workspace. The app does not sell Google data or use it for advertising. Google data is not used to train general-purpose AI models.
Storage and protection
The dashboards run on Cloudflare. Cloudflare provides application hosting, databases, storage, and access protection. Google authorization credentials stored by both dashboards are encrypted. Connections to Google and the public dashboards use HTTPS. Authorized workspace users and the operator can access project data according to the application's access controls.
The portfolio dashboard retains collected performance snapshots. OpenSEO stores account connections, project settings, and reports or analysis results that you save. Stored history is not automatically removed when a connection is disconnected. There is currently no fixed automatic deletion period for saved project history.
Service providers and sharing
Google processes authorization and Search Console API requests. Cloudflare processes application traffic and stores deployment data on the operator's behalf. Infrastructure providers may process operational or security logs, such as request metadata.
OpenSEO installation telemetry is currently enabled. It sends a pseudonymous installation identifier, software and deployment information, feature counts, setup status, and whether a Search Console connection exists to the OpenSEO developer through PostHog. The installation-heartbeat implementation does not include Search Console queries, page URLs, performance rows, account emails, or authorization tokens in its payload. The operator can disable this telemetry.
If you explicitly use an AI assistant or connected client to analyze Google data, the requested data may be sent to that client or the selected AI service to provide the requested analysis. Its separate privacy terms apply. Only use those features with providers and data-handling settings you approve. The app does not sell or transfer Google data to advertising platforms or data brokers. Other transfers are limited to providing requested features, security, or legal obligations.
Disconnecting, revocation, and deletion
You can revoke the app's Google authorization in your Google Account connections settings. This stops future authorized requests once the revocation takes effect; it does not erase previously saved history.
In OpenSEO, disconnecting an individual project removes its property mapping but leaves the Google account authorization available for other projects. Removing the connected Google account removes its stored authorization and related project connections. In the portfolio dashboard, disconnecting clears its saved refresh credential while retaining saved history.
To request deletion of saved Google-derived history or other stored project data, contact papaz_no1@yahoo.com and identify the account or project concerned. The operator will verify the request and arrange deletion. Backup or infrastructure-log copies may remain until the provider's retention period ends. No immediate deletion or fixed completion deadline is promised by this notice.
Google API data-use commitments
The application's handling and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is used only for the disclosed, user-facing features and permitted purposes described above.
Changes and contact
Material changes to Google-data use will be disclosed before the new use begins, and additional consent will be requested where needed. Contact papaz_no1@yahoo.com about privacy or deletion.