Screpy Browser Extension Privacy Policy

This Privacy Policy explains how Airscarp LLC ("Airscarp LLC," "Screpy," "we," "our," or "us") handles information in connection with the Screpy browser extension. This policy is written for users, reviewers, and platform operators (including Chrome Web Store reviewers). It applies to the Screpy browser extension only, unless another product explicitly states that this policy applies.

Screpy is an SEO-focused browser extension. Its core features include:

Some features run when you open the extension popup. Some visual features run on matching pages so the extension can apply local visual modifications.

• on-page SEO analysis for the currently active tab;
• optional visual link-highlighting on regular websites;
• optional visual enhancements on Google Search result pages; and
• backlink lookup for the current domain via a separate Airscarp-operated BacklinkScan service.

Below is the exact data inventory for the current codebase (reviewed June 27, 2026).

When you open popup analysis, Screpy reads:

Purpose:

Storage and transfer:

Important note:

• active tab URL; and
• full HTML of the active page (document.documentElement.outerHTML).
• run local SEO analyzers (meta, headings, links, technical signals, etc.) in extension context.
• processed in memory for analysis;
• not sent as full page HTML to Screpy servers;
• not written to extension local storage by current code.
• page HTML may contain personal or sensitive information that already exists on that page; Screpy accesses it locally to provide requested analysis output.

For visual features, Screpy may read page context such as:

Purpose:

Storage and transfer:

• current URL and hostname;
• link attributes (href, rel, target) needed for classification/highlighting;
• Google Search result link/domain elements needed for SERP highlighting and result numbering.
• classify links and apply visual styling based on user settings;
• mark matching Google results and add plain-text ranking labels.
• Screpy may inject local CSS/style markers into matching pages so enabled highlight features can render visually;
• handled locally in page context;
• not used for ads, profiling, or analytics by current code.

Screpy stores feature settings in browser.storage.local, including:

Purpose:

Storage and transfer:

• on-page link highlight settings (key: onpage.highlight.link-settings);
• SERP highlight domain-color entries (key: serp.highlight.domains).
• persist your selected highlight rules/colors between sessions.
• stored locally in browser extension storage on your device;
• not synced to Screpy-operated cloud services by current code.

When technical checks are run, Screpy may request:

Screpy may process:

Purpose:

Storage and transfer:

• the analyzed page URL;
• robots.txt;
• sitemap candidates and declared sitemaps;
• selected links for status probing.
• HTTP status codes and status text;
• response headers;
• response timing and byte-size signals;
• robots directives and sitemap validation metadata;
• link probe results.
• render technical SEO analysis (HTTP/robots/sitemap/link-health).
• results are used in extension UI;
• destination servers receive normal request metadata (for example IP address and headers) under their own policies.

If you open the Backlinks section, Screpy sends the current site's domain to:

Purpose:

Storage and transfer:

• https://app.backlinkscan.com/api/backlink-checker?domain=<domain>
• retrieve backlink-related data for the current domain.
• response data may include backlink-related SEO fields such as referring domains, referring URLs, anchor text, summary metrics, and country aggregates;
• request is made to BacklinkScan, a separate Airscarp-operated service used for backlink data;
• response data may be cached in memory during the current extension session for UI performance;
• Screpy does not send full page HTML in this request.

If you contact us directly (for example by email), we receive the information you include, such as:

Purpose:

• email address;
• name or signature details;
• support/privacy request content.
• provide support, respond to requests, and maintain operational/legal records.

Screpy accesses data only when feature execution requires it.

• Popup analysis: when you open or refresh the popup on a page.
• On-page highlighting: on regular http/https pages where the content script runs; rendering depends on your saved settings.
• SERP highlighting/positioning: on matching Google Search result pages.
• Technical checks: when analysis modules request HTTP/robots/sitemap/link probe data.
• Backlinks: when you open Backlinks pages in the popup.

Screpy currently requests:

Used to read the currently active tab context when you invoke popup analysis.

Used to execute extension code in the active tab for analysis context extraction and page-level feature behavior.

Used to read/write your local extension settings.

Current host permissions are limited to:

These are used to:

Screpy does not request host access for file://, chrome://, or other non-web schemes in current config.

• http://*/*
• https://*/*
• run supported page-level features on regular web pages;
• run Google Search page enhancements;
• perform technical SEO requests required by analysis modules.

Screpy uses data only to provide extension functionality and related operations, such as:

Based on current code, Screpy does not use analyzed page content for advertising or behavioral profiling.

• SEO analysis of the currently selected page;
• visual highlighting and SERP enhancements configured by the user;
• technical diagnostics (HTTP, robots, sitemap, link status);
• backlinks lookup for the current domain;
• local setting persistence;
• support and compliance handling when users contact us.

Screpy is designed to use extension-accessed data only for user-facing extension functionality and related operational purposes described in this policy. In line with the Chrome Web Store User Data Policy, including Limited Use expectations, Screpy does not sell extension-accessed data, does not use it for advertising or behavioral profiling, and does not transfer it to third parties except as needed to provide requested extension features, comply with law, protect security, or respond to user-initiated support/privacy requests.

Screpy also does not allow humans to read active-page HTML or other extension-accessed page content unless the user explicitly sends that information to us for support, the access is necessary for security or legal reasons, or the data has first been aggregated or de-identified so it no longer identifies a user or page.

Screpy may send limited data off device in the following cases:

As with any network request, destination services may process technical metadata (for example IP address, headers, and connection logs) under their own privacy terms.

• requests to analyzed sites and link targets for technical checks;
• requests to BacklinkScan, a separate Airscarp-operated service, for backlinks lookup (domain-level input);
• direct support communications initiated by the user.

Current related-service API usage in code:

BacklinkScan is operated by Airscarp as a separate service used to provide backlink data for the extension. Other destination sites contacted for technical checks or link probes are outside Screpy's control and may process request metadata under their own policies.

Screpy does not currently embed analytics/ad SDKs in the extension codebase reviewed on June 27, 2026.

• BacklinkScan API endpoint: https://app.backlinkscan.com/api/backlink-checker

Based on current codebase behavior, Screpy does not currently implement:

This section describes current behavior only. If features change, this policy will be updated.

• user account registration/login in the extension;
• payment or billing collection inside the extension;
• cookies set by Screpy for extension analytics/tracking purposes;
• browser history collection or full browsing activity logs maintained by Screpy;
• cloud storage of full analyzed page HTML by Screpy;
• telemetry/analytics SDK collection by Screpy from extension usage;
• ad network tracking integrations in extension runtime;
• sale of personal data.

Current persistent extension-local keys:

Other analyzer computations are primarily in-memory for runtime display and are not persisted as full-page HTML archives by current code.

• onpage.highlight.link-settings: link highlight type enable/color preferences.
• serp.highlight.domains: saved domain-color rules for SERP highlighting.

Retention model for current code:

• active-page HTML is processed during runtime and not stored remotely by Screpy;
• local settings remain until you modify them, clear extension data, or uninstall;
• support messages may be retained as reasonably necessary for support, legal compliance, and dispute resolution;
• data received by third-party destinations follows those destinations' retention rules.

We apply reasonable measures to limit processing to stated feature scope. Current implementation characteristics include:

No storage or transmission method is fully secure. Users should avoid running analysis on pages where local processing itself is not desired.

• extension-local settings storage via browser extension APIs;
• network requests controlled by browser security model and destination servers;
• no Screpy-operated cloud database for full analyzed page HTML in current code.

You can control Screpy by:

For privacy requests, contact hello@screpy.com.

• choosing when to open/refresh popup analysis;
• enabling/disabling/modifying highlight settings;
• adding/removing SERP highlight domain rules;
• choosing whether to use Backlinks pages;
• clearing extension local data in browser settings;
• uninstalling the extension at any time.

Screpy, analyzed websites, and third-party services may operate in different countries. Data involved in extension operations may therefore be processed in jurisdictions with different data-protection laws.

Screpy is not directed to children. We do not knowingly design this extension for child-directed data collection or advertising profiling.

If you believe a child provided personal data directly to us, contact hello@screpy.com.

We may update this policy to reflect product, legal, security, or operational changes. Updated versions will revise the "Last Updated" date.

Airscarp LLC Email: hello@screpy.com