iPage

Privacy Policy

iPage icon

iPage

Large Text · TTS · Accessibility

Effective date: July 30, 2026

This Privacy Policy explains how the iPage Chrome extension (the “extension”, “we”) handles information.

Summary. iPage creates a focused reading view from content the user chooses. Webpage, Gmail, PDF, and supported Google Docs content is processed in Chrome and is not sent to the developer. iPage has no developer-operated content server, iPage account, analytics, advertising, or data-selling business. Optional translation, Google read-aloud voices, and support links involve independent third-party services only when the user chooses those features.

1. Information iPage handles

1.1 Webpage content

To create a focused reading view, iPage examines the active webpage’s document structure and readable content. This can include the page URL, title, headings, paragraphs, lists, quotations, captions, image alternative text, author/date metadata, and hyperlinks. iPage also identifies common navigation, footer, comment, reaction, sharing, subscription, and accessibility-control regions so they can be excluded from Main-only view.

Extraction and reading-view rendering happen in the browser. iPage does not send webpage content, browsing history, or extracted articles to the developer.

1.2 Gmail content

When the user opens iPage in Gmail, the extension can display inbox subject rows and the body of a message the user selects. Gmail content is processed only in the browser to provide the requested simplified reading view. It is not sent to the developer, stored in a developer database, or made available for human review.

1.3 PDF and Google Docs content

For a text-based PDF, iPage downloads the PDF directly from its original address in Chrome and uses a packaged, local copy of PDF.js to extract embedded text. The PDF is not uploaded to or processed by a developer-operated server. Image-only scanned PDFs require OCR, which iPage does not currently provide.

When an open Google Doc is detected, iPage requests the document’s plain-text export from Google Docs using the user’s existing signed-in Chrome session. The request goes directly to Google and is subject to the document owner’s sharing and download settings. iPage does not receive the user’s Google password or send the document to the developer.

1.4 Saved settings and temporary cache

chrome.storage.sync stores reading preferences such as text size, line spacing, light or dark background, Main-only choice, translation target, speech rate, selected voice, and Accessibility Assist state. When Chrome Sync is enabled, Google may synchronise these preferences across the user’s signed-in Chrome browsers under Google’s terms and policies.

chrome.storage.session may temporarily cache the extracted article for the current tab so the panel can display quickly during navigation or recovery. Session storage is cleared by Chrome when the extension session ends and is not available to the developer.

1.5 Information iPage does not collect

  • No name, email address, account profile, or developer login is collected by the developer
  • No payment, financial, health, or authentication information
  • No browsing-history database or website-visit log
  • No analytics, advertising identifier, telemetry, or behavioural profile
  • No form values, passwords, Gmail content, mouse movement, or keystrokes are transmitted to or collected by the developer
  • No sale or transfer of user information for unrelated purposes

2. How information is used

Selected webpage, Gmail, PDF, and supported Google Docs content is used only to identify and display readable content, preserve safe links, count words, detect the content language, translate at the user’s request, and read the displayed text aloud at the user’s request. Preferences are used only to reproduce the user’s chosen iPage settings.

3. Translation

Translation does not start automatically. When the user selects Translate, iPage first attempts to use Chrome’s built-in Translator capability where available. Chrome may download or use language models under Chrome and Google’s terms and privacy practices.

If inline translation is unavailable, iPage can open translate.google.com as a fallback. The current webpage URL and requested target language are included in that Google Translate URL so Google can open the translated page. iPage does not send that information to the developer.

4. Read-aloud and Google voices

iPage uses Chrome’s chrome.tts API and limits its voice menu and automatic selection to Google voices exposed by the user’s Chrome installation. It matches the article’s BCP-47 language, script, and region to a compatible voice and does not intentionally substitute a voice from another language.

Some Google voices may be remote voices. When a remote voice is used, Chrome or Google may process the text needed to generate speech under their own terms and privacy practices. iPage does not receive the generated speech request, transcript, or audio on a developer server.

5. Browser permissions

5.1 Website access (<all_urls>) and active tab

iPage is designed to work on ordinary webpages and supported document URLs across the web. Website access lets the packaged content script inspect the active page’s readable document structure, show Gmail subjects and a selected message body, request an open Google Doc’s text export, retrieve a PDF from its original address, keep selected links usable, and update the iPage panel after navigation. The activeTab permission supports user-initiated interaction with the current tab. iPage does not use these permissions to build browsing history or transmit page, Gmail, or document content to the developer.

5.2 Side panel

sidePanel displays the packaged iPage interface beside the active webpage. The panel itself is extension code and does not embed a developer-operated website.

5.3 Scripting

scripting lets iPage inject only its packaged extraction scripts into a tab that was already open when the extension was installed, updated, or reloaded, or when the current script is missing. iPage does not use remote code, eval, downloaded JavaScript, or externally hosted application logic.

5.4 Storage and TTS

storage provides the local settings and temporary session cache described above. tts provides user-initiated read-aloud through voices installed or exposed by Chrome.

Chrome does not permit extensions to read protected pages such as chrome:// pages or the Chrome Web Store. iPage may also be unable to extract content hidden behind sign-in, cross-origin frames, or a manual “load more” action. Password-protected PDFs must be unlocked, scanned PDFs need OCR, local PDFs require Chrome’s “Allow access to file URLs” setting, and Google Docs must permit text export.

6. Accessibility

iPage’s interface uses semantic landmarks, labelled controls, keyboard focus, status announcements, reduced-motion support, and user-controlled text settings. Accessibility Assist adds larger controls, stronger visual contrast and focus, underlined links, and disabled animations. These features process no additional personal information.

iPage uses WCAG 2.2-informed design practices, but it does not certify or guarantee the accessibility compliance of third-party webpages. It provides an alternative reading presentation and user-controlled assistance.

7. External support links

The optional Buy Me a Coffee and PayPal buttons are ordinary links that open only when selected. Payment details and account information are handled by those independent providers under their own terms and privacy policies. iPage does not collect or process payment information.

8. Data retention and user choices

Saved preferences remain in Chrome storage until changed, cleared, or removed when iPage is uninstalled. Temporary article cache data remains only in Chrome session storage. Users can stop read aloud, restore the original language after translation, turn Main-only mode or Accessibility Assist off, clear extension data through Chrome, or uninstall iPage at any time.

9. Limited Use disclosure

The use of information received from Chrome extension permissions adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide or improve iPage’s single purpose and user-facing features. It is not sold, transferred for unrelated purposes, used for advertising, or made available for human review by the developer.

10. Security

iPage’s executable JavaScript and CSS are included in the extension package. It does not run remote application code or transmit webpage, Gmail, PDF, or Google Docs content to a developer server. Chrome, Google Translate, Google TTS voices, PayPal, and Buy Me a Coffee are independent services governed by their own security and privacy practices when used.

11. Changes to this policy

We may update this policy as iPage, Chrome, or applicable requirements change. Material changes will be shown on this page with an updated effective date.

12. Contact and support

YouTube: https://www.youtube.com/@quiki.studio
Support: Google Automator Support
Report a bug: iPage bug report form