Privacy Policy

Last updated: June 2026

This policy explains what the Search Console Peek Chrome extension ("the extension", "we", "us") collects, why, and how it is handled. It is operated by Algoramming. Questions: support@algoramming.com.

What the extension accesses

Your Google Search Console data — clicks, impressions, CTR, position, top queries and pages for properties you own. This is requested with a read-only scope (webmasters.readonly), fetched directly from Google and shown to you in the extension. We do not store your Search Console performance data on our servers.
Your basic Google profile — your name, email address, profile picture, and Google account identifier (email, profile scopes).
The active tab's domain — read only when you open the extension, and only to auto-select a matching property. It is not stored or transmitted.

What we store, and why

So we understand who uses the extension and how, we store the following in our database (hosted on Supabase):

Your name, email, profile picture, and Google account identifier.
Usage metadata: number of visits, first-seen and last-seen timestamps.
The names/URLs of the Search Console properties you view in the extension.

We collect this only after you acknowledge the in-extension notice. We use it solely to operate, understand, and improve the extension. We do not sell it, and we do not use it for advertising.

How your data is shared

Google — for authentication and to provide your Search Console data, under Google's Privacy Policy.
Supabase — our database provider, which stores the information listed above on our behalf.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Data retention & your choices

We keep your record until you ask us to delete it.
You can request access to or deletion of your data at any time by emailing support@algoramming.com.
You can revoke the extension's access entirely at your Google Account permissions.

Security

Data is transmitted over HTTPS and stored with access restricted to the extension's backend functions. Your Search Console access token is never sent to our servers.

Changes

We may update this policy; material changes will be reflected by the date above.