Privacy Policy — Page Performance

1. What Page Performance does

Page Performance is a Chrome extension that allows users to analyse the performance of the web page currently open in Chrome, or the corresponding website, using data from Google Analytics 4 and Google Search Console.

The extension operates primarily within the user's browser and communicates directly with Google APIs to provide its reporting functionality.

2. Google account authorization

Google account authorization starts only after the user explicitly clicks the Connect Google account button.

Page Performance requests only the following Google OAuth scopes:

• read-only access to Google Analytics;
• read-only access to Google Search Console.

Page Performance does not request permission to modify Google Analytics or Search Console data. It does not request access to Gmail, Google Drive or Google Contacts, and it does not request a Google profile scope.

3. Google user data accessed

When authorized by the user, Page Performance may access the following Google user data.

Google Analytics

• Analytics accounts and properties accessible to the user;
• property and web data-stream metadata used to identify the appropriate property for the website being analysed;
• available key events;
• Analytics reporting metrics and dimensions required to generate Page Performance reports, including sessions, active users, conversions, acquisition data, engagement data, page views, events and ecommerce metrics where available.

Google Search Console

• Search Console properties accessible to the user;
• search-performance data for the selected page or website, including queries, pages, countries, clicks, impressions, click-through rate and average position.

Page Performance accesses this information only when required to provide the user-facing reporting, property-matching and configuration functionality of the extension.

4. Browser information accessed

Page Performance reads the URL and hostname of the active Chrome tab.

This information is used to identify which website and page the user wants to analyse, match the appropriate Google Analytics and Search Console properties, and construct the requested reports.

Page Performance does not collect a background history of websites visited by the user. Tab and URL changes are observed by the reporting interface while the Page Performance side panel is open.

5. How information is used

Information accessed by Page Performance is used only to:

• authenticate the user's Google account;
• identify Google Analytics and Search Console properties available to the user;
• match those properties to the website being analysed;
• retrieve analytics and organic-search performance requested by the user;
• generate reports, comparisons and insights inside the extension;
• remember the user's per-website configuration;
• provide user-initiated features such as saved-page comparison, copying summaries and CSV exports;
• maintain short-lived caches to reduce unnecessary Google API requests.

Google user data is not used for advertising, profiling, creditworthiness, lending, data brokerage or any purpose unrelated to the user-facing features of Page Performance.

Google user data is not used to train artificial intelligence or machine-learning models.

6. Local storage

Page Performance stores application data within Chrome extension storage.

This may include:

• OAuth access-token and expiry information;
• selected Google Analytics and Search Console properties;
• user preferences such as the selected conversion event and channel grouping;
• cached property metadata;
• cached report data;
• temporary saved-page comparison information.

Report data is treated as stale after approximately ten minutes and property-discovery metadata is treated as stale after approximately twenty-four hours. Expired cache information may remain in local extension storage until it is replaced, cleared or the user signs out.

Page Performance does not operate a remote database or developer-operated server for storing Google Analytics or Search Console report data.

7. Data sharing and disclosure

Page Performance does not sell, rent or disclose Google user data to advertisers, data brokers or information resellers. Google user data is not transferred to third parties for advertising or marketing purposes.

Information is transmitted to Google only as necessary to authenticate the user and request data from the Google APIs selected by the user.

User-initiated exports are generated locally in the browser. The Copy summary feature writes the generated summary to the clipboard only after the user explicitly requests it.

Data may be disclosed only where required by applicable law or where necessary to protect the security and integrity of the service.

8. Google API and Chrome Web Store user data policies

Page Performance's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Page Performance's handling of user data also follows the Chrome Web Store Limited Use policy. User data is handled only to provide or improve the extension's single-purpose, user-facing functionality and only in ways disclosed in this Privacy Policy.

Google user data is not transferred or used for advertising, data brokerage, creditworthiness, lending or unrelated purposes.

Human access to Google user data is not permitted except where the user explicitly requests and consents to access for support, where necessary for security purposes, or where required by law.

9. Security

Page Performance communicates with Google APIs using HTTPS.

OAuth credentials and application information are stored within the user's Chrome profile using Chrome extension storage. Access tokens are time limited.

When the user signs out, Page Performance requests revocation of the active Google OAuth token and removes locally stored authentication information, site configuration, source metadata and report caches.

No system can guarantee absolute security, but reasonable technical measures are used to reduce unauthorized access to user information.

10. Data retention and deletion

Users control their connection to Google from within Page Performance.

Signing out:

• requests revocation of the active Google OAuth token where possible;
• removes locally stored authentication information;
• removes per-site configuration;
• removes cached source metadata;
• removes cached report data.

Users may also remove extension-local information by uninstalling Page Performance from Chrome. Google Account permissions can additionally be revoked through the user's Google Account security settings.

11. Children's privacy

Page Performance is intended for professional website analytics and is not directed at children. The extension does not knowingly collect personal information from children.

12. Changes to this Privacy Policy

This Privacy Policy may be updated when Page Performance's functionality or data practices change. The date at the top of this page indicates the latest revision.

Material changes affecting how Google user data is accessed or used will be disclosed as required before the new practices take effect.

13. Contact

Questions about Page Performance or this Privacy Policy can be submitted through the Page Performance support page.

14. Google services

Google Analytics, Google Search Console and Google OAuth services are provided by Google and are subject to Google's own terms and privacy policies.

Page Performance is an independent product and is not affiliated with or endorsed by Google.