Check recent Common Crawl visibility from the page you are viewing.Learn how it works
855.629.6584
MAXPlaces Marketing
Get My AI Visibility Report

CC Index Check

Privacy policy

This policy explains when the Chrome extension reads the active page URL, what is removed, how standard connection metadata such as the IP address is handled, where lookup data goes, how local results are retained, and how to delete them.

Effective August 4, 2026Last updated August 4, 2026

1. Scope and affirmative consent

This policy applies to CC Index Check, a Chrome extension published by MAXPlaces Marketing, LLC. The extension is designed to check a public page and host for reported Common Crawl evidence and related Common Crawl WebGraph rank positions.

On first use, the popup displays a data-use disclosure. Until you click Check this page, the extension does not call Chrome’s tab API, read the active tab URL, or contact a lookup provider. Your choice must be saved successfully in Chrome local extension storage before the first lookup begins.

The saved consent record contains only the current disclosure version, represented as{ accepted: true, version: 2 }. It contains no acceptance timestamp, account, user identifier, or device identifier. After acceptance, opening the popup performs the requested check automatically. A future release that materially changes providers or data use will advance the disclosure version and ask again.

2. Data the extension handles

Active page URL

After consent, the extension reads the URL of the active tab in the current Chrome window. It does not request or read your complete browser history. Under Chrome Web Store terminology, an active page URL is web browsing activity even when it is handled only to provide the feature you requested.

Before any lookup or cache write, the extension removes:

  • embedded usernames and passwords;
  • the entire query string, including all query parameters; and
  • the URL fragment following #.

The sanitized URL retains the protocol, normalized hostname, and path because those fields identify the page to check. Paths can sometimes contain account names, order numbers, or other information chosen by a website. Use the extension only on a public page whose path you are comfortable sending to the providers listed below.

Connection metadata and IP address

Internet requests expose ordinary connection metadata, including the client IP address, to each recipient. Chrome Web Store terminology includes IP-address handling in the Location data category. Section 5 explains how MAXPlaces uses an IP-derived SHA-256 quota key for abuse prevention and how infrastructure providers may handle ordinary request logs.

Data the extension does not read

The extension does not read page text, HTML, images, form fields, passwords, cookies, authentication tokens, downloads, personal communications, or the content of any other tab. Browser-internal pages, local files, internal-network hosts, URLs whose hostname is a literal IP address, URLs using a non-default port, and other unsupported URLs are rejected.

Public result data

Lookup responses can include a Common Crawl collection identifier and crawl dates; captured URL, timestamp, HTTP status, MIME type, and length; HC Rank and PageRank positions; provider availability; and cache age. These are public or derived web-archive signals associated with the sanitized URL or hostname.

3. How data is used and sent

The sanitized active URL is used only to provide, maintain, secure, or troubleshoot the Common Crawl and WebGraph check shown in the popup. The data flow is limited to the following recipients.

Primary lookup: MAXPlaces

The extension sends the sanitized protocol, host, and path in a JSON POST body to the MAXPlaces quick-check API at aio.maxplaces.com. The endpoint applies the same sanitization again. Its immediate extension response is marked not to be stored by shared HTTP caches. MAXPlaces can reuse recent domain-level public crawl evidence to provide the result; the page path is not used as the server report cache key.

Direct fallback providers

If the MAXPlaces quick-check endpoint itself is unavailable, the extension can make the requests necessary to complete the same user-facing feature directly:

  • Common Crawl: the sanitized exact URL, including protocol, hostname, and path, can be placed in a query to index.commoncrawl.org. A separate hostname lookup can be used to find host evidence.
  • Metehan WebGraph: the normalized hostname or domain is sent towebgraph.metehan.ai to request HC Rank and PageRank data. The page path is not sent to Metehan.

A valid MAXPlaces response that reports a provider result as unknown is displayed as unknown and does not trigger direct fallback requests. The Full MAXPlaces check link opens aio.maxplaces.com only when you click it and passes the normalized hostname, not the page path.

Common Crawl and Metehan operate independent services. Their handling of direct request metadata is governed by their own policies and infrastructure settings.

4. Chrome local storage and retention

The extension uses chrome.storage.local for the consent-version record described above and a bounded result cache. It does not use Chrome Sync, so this information is not intentionally synchronized to your other signed-in Chrome devices by the extension.

  • The cache contains at most 50 sanitized page URLs and their lookup reports.
  • A conclusive result can be reused without another live lookup for up to 24 hours.
  • An inconclusive, unavailable, or stale result can be reused for up to 5 minutes.
  • The most recent entries are retained when the 50-entry limit is enforced.

When the extension next accesses its cache, it prunes expired records before using or writing entries. Expired data is not eligible for normal cache replay. Because this cleanup occurs on later extension use, an expired record can remain physically present in local storage until the next cache access, eviction by newer entries, clearing of extension data, or uninstall. A still-current earlier success can be displayed as Last confirmed when a user-requested recheck encounters a temporary provider failure.

5. Network infrastructure, IP addresses, and logs

Like other internet requests, calls to MAXPlaces, Common Crawl, and Metehan necessarily expose standard request metadata to the recipient and its infrastructure. Depending on the service, that metadata can include an IP address, user-agent/browser information, request time, requested endpoint, response status, and the Chrome extension origin.

The MAXPlaces API is hosted and protected using Cloudflare infrastructure. MAXPlaces processes the client IP to enforce an abuse-prevention quota. The application quota record uses an IP-derived SHA-256 key rather than a raw IP and expires on an approximately 10-minute rate-limit window. Cloudflare and endpoint operators may process or retain raw IP addresses and ordinary HTTP or security logs under their own operational, legal, and security retention settings.

MAXPlaces application error logging for this endpoint is designed to record a random request ID and a bounded error type rather than the submitted URL. Domain-level public reports may be cached briefly for performance. The extension does not send an account ID or create a user profile at the MAXPlaces endpoint.

6. No extension analytics, ads, sale, or profiling

The CC Index Check extension contains no analytics or advertising code. MAXPlaces does not use or transfer active-page browsing activity from the extension to:

  • serve personalized, retargeted, interest-based, or behavioral advertising;
  • sell data or provide it to data brokers or information resellers;
  • create cross-service browsing profiles or conduct unrelated market research;
  • determine creditworthiness or make lending decisions; or
  • support a purpose unrelated to the extension’s disclosed current-page check.

People at MAXPlaces do not routinely review active-page URL data. Limited access to infrastructure records may occur when necessary to investigate security or abuse, comply with law, or address a specific support request for which you voluntarily provide the relevant information.

The MAXPlaces website, including this public policy page, is separate from the extension and may use the website analytics and cookie practices described in the generalMAXPlaces Privacy Policy and Cookie Policy.

7. Security practices

  • All provider and MAXPlaces requests use HTTPS.
  • Fetch requests omit cookies and other credentials.
  • Only fixed, declared API hosts can be contacted by extension code.
  • Remote responses are treated as data, constrained in size and time, and are not executed as code.
  • Provider text is rendered as text rather than injected as executable HTML.
  • Incognito operation is disabled.

Local records are stored within the Chrome profile using Chrome’s extension storage controls. The extension does not add its own encryption layer to that local cache, so access to the operating-system or Chrome profile can also expose extension data. No transmission or storage method can guarantee absolute security.

8. Your choices, deletion, and support

If you do not accept the first-use disclosure, do not click Check this page; the extension will not read the active URL or contact lookup providers. The current release does not include a separate revoke button after acceptance.

You can remove the local consent record and cached reports by clearing data specifically for the extension through Chrome controls or by uninstalling CC Index Check. Disabling and re-enabling an extension may not clear local records. After extension data is cleared, the disclosure appears again before another lookup.

Clearing local data cannot recall a request already delivered to a lookup provider or erase ordinary infrastructure logs controlled by another operator. To ask about information controlled by MAXPlaces, email [email protected]. Because the quick-check service does not create an account or persistent user identifier, MAXPlaces may not be able to associate an infrastructure record with a particular person without additional details.

The extension never sends a support request automatically. Information you choose to include in an email to support can be read by the people responding to that request. See thesupport page for safe troubleshooting guidance.

9. Children and changes to this policy

CC Index Check is a professional web-research utility and is not directed to children under 16. MAXPlaces does not knowingly use the extension to collect information from children.

We may update this policy to reflect extension, provider, security, or legal changes. The date above will be updated. If a future extension release materially changes its URL handling, recipient providers, or purposes, it will advance the in-product disclosure version and require affirmative acceptance before the active URL is read under the new practice.

10. Chrome Web Store Limited Use and contact

CC Index Check’s use and transfer of information received from Google Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Data received through Chrome permissions is used only to provide or improve the extension’s disclosed single purpose, or for directly related security, legal, and user-requested support needs. It is not used or transferred for advertising, unrelated profiling, sale, or creditworthiness.

Contact

MAXPlaces Marketing, LLC
399 Conklin Street, Suite 305
Farmingdale, NY 11735
Privacy: [email protected]
Extension support: [email protected]
Phone: 855.629.6584