01 Scope and Product Purpose
RainLabs SEO Inspector is a browser extension for user-initiated, on-page SEO audits. It reads information from the webpage in your active tab only when you ask it to analyze that page. It uses that information to calculate an SEO score, identify issues, display recommendations, and, for available Pro features, create reports, save Audit History, and compare audits.
This notice supplements the general RainLabs Privacy Policy. It does not replace that policy for the RainLabs website, accounts, support, or other RainLabs products.
02 Webpage Data Accessed
For a requested audit, SEO Inspector may read:
- The current page URL, hostname, title, and document-level settings.
- Metadata such as descriptions, robots directives, canonical URLs, language, viewport, and character set.
- Heading text and hierarchy.
- Link destinations, link text, relationship and target attributes, and aggregate link counts.
- Image URLs, alternative-text attributes, dimensions, loading attributes, and aggregate image counts.
- Open Graph, social-card, technical, favicon, alternate-link, and manifest metadata.
- Structured data, including JSON-LD content and detected schema types.
- Visible body text for aggregate word and text-length counts.
Raw visible body text is used to calculate aggregate content counts and is not normally returned as full body text in the audit data. Chrome also prevents extensions from inspecting certain protected or browser-internal pages.
03 Local Audit Processing
The SEO analysis runs locally in the extension. The inspected webpage is not uploaded to RainLabs, Supabase, or Paddle to calculate the audit. A normal audit is not added to Audit History unless you explicitly choose Save audit.
Account, entitlement, and checkout functions do communicate with external services as described below. If you voluntarily send an exported report or page information to RainLabs for support, RainLabs will receive the information you choose to send.
04 Downloaded Reports
Markdown and JSON reports are generated locally after you request an export. The Markdown report may include the page URL and title, score, audit findings, current values, recommendations, canonical URL, H1 headings, image and link counts, and detected structured-data types.
The JSON report contains more of the extracted page and audit data. It may include metadata, headings, image URLs and attributes, link destinations and text, social and technical metadata, and raw JSON-LD entries. Each raw JSON-LD entry is capped at 50,000 characters in the current implementation. Because page owners can place identifying or sensitive information in these fields, review a report before sharing it.
Exported files remain wherever your browser or operating system saves them until you move or delete them. RainLabs does not upload or cloud-sync exported reports through the current extension.
05 Local Audit History
Pro Audit History stores only audits that you explicitly save. Saved snapshots may include the page URL, hostname, title, save time, SEO score and result counts, canonical URL, H1 headings, word count, image and link counts, detected structured-data types, and audit findings and category results.
History is stored in chrome.storage.local in the current browser profile. Records use account-specific local storage keys so one signed-in RainLabs account does not load another account's saved History. The current extension stores a maximum of 30 snapshots for an account and does not upload or cloud-sync them.
Deleting saved History
Open Audit History in the extension. Use Delete on a saved audit and confirm to remove that snapshot. To remove every saved snapshot for the current account, use Clear history and confirm. Clearing History cannot be undone. These controls remove the relevant local History data; they do not delete your RainLabs account or server-side subscription records.
06 Accounts and Authentication
An account is optional for the core audit and is required for account-based Pro features. RainLabs uses Supabase for authentication. When you sign in through the extension, your email address is submitted to Supabase Auth to identify your account. Your password is submitted to Supabase Auth for authentication and is not stored in Audit History or exported audit reports by SEO Inspector.
After successful authentication, Supabase provides session information, including access and refresh tokens. The extension persists that session in its extension-local browser storage so you can remain signed in and refresh authentication. RainLabs and Supabase may also handle your account identifier, email address, authentication events, and related security and account records. The RainLabs website maintains its own authenticated website session.
07 Entitlement and Checkout Requests
To determine whether Pro features are available, the extension sends an authenticated entitlement request to RainLabs. This request includes the Supabase access token needed to identify the signed-in account. It does not include the inspected webpage or audit results.
When an eligible signed-in user starts an upgrade, the extension sends RainLabs an authenticated checkout-preparation request with the selected monthly or annual billing interval. RainLabs uses the authenticated account, product and subscription records, and trusted Paddle catalog information to prepare the product-specific checkout. The extension does not send inspected webpage data in that request.
08 Extension, Website, and Paddle Boundaries
- Chrome extension: performs audits, report generation, and Audit History storage locally.
- RainLabs services: provide account authentication integration, entitlement checks, secure checkout preparation, and subscription-status handling.
- RainLabs website: hosts the secure checkout transition on rainlabsapp.com and provides account and subscription views.
- Paddle: displays and processes payment checkout, billing details, payment information, taxes, and transaction records under Paddle's own practices.
Card information is entered into Paddle's checkout and is not collected directly by the extension. RainLabs receives the transaction and subscription information needed to maintain product access. Review the Paddle Privacy Policy for Paddle's processing practices.
09 Retention and Deletion
- Unsaved audits are not added to Audit History.
- Saved History remains in local extension storage until removed with the verified History controls or otherwise cleared from that browser profile.
- Downloaded reports remain on your device until you delete them.
- The authentication session remains in extension-local storage while it is persisted and valid; signing out ends the extension session through Supabase Auth.
We do not currently specify a fixed SEO Inspector-specific retention period for Supabase account records, entitlement and subscription records, checkout records, or operational and security logs. These records may be retained as needed to provide and secure RainLabs services, meet service-provider requirements, comply with legal obligations, and maintain legitimate business records. This notice does not promise immediate deletion of backend records or an automated account-deletion workflow. Contact RainLabs to request review of available privacy choices.
10 Analytics and Advertising
No analytics or advertising SDK is included in the current extension. SEO Inspector does not use inspected webpage data for personalized advertising, sell that data to data brokers, or use it to determine creditworthiness or for lending purposes.
11 Chrome Web Store Limited Use
RainLabs SEO Inspector's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Consistent with the current implementation, webpage data is accessed only for the extension's disclosed, user-facing SEO audit purpose and related report, History, and comparison features. Normal audit operation does not transfer inspected webpage data to RainLabs, Supabase, Paddle, advertising services, or data brokers. Account and subscription data is used only for authentication, entitlement, checkout, billing, security, support, and related product operations described in this notice.
RainLabs does not normally receive inspected webpage data and does not permit human access to it unless you explicitly provide that data for support, access is necessary for security or legal compliance, or the data has been aggregated and anonymized for permitted internal operations.
See the official Chrome Web Store Limited Use policy.
12 Contact and Changes
For SEO Inspector privacy or support questions, or to request review of account-related privacy choices, email hello@rainlabsapp.com. RainLabs may need to verify your identity before acting on a request, and available rights and exceptions depend on applicable law.
RainLabs may update this notice when SEO Inspector's features, data practices, service providers, or legal requirements change. The latest revision date appears at the top of this page.