1. Scope and contact
This policy describes how the See website on mobile Chrome extension handles information when you preview websites, compare devices and capture or edit screenshots. It applies to the extension, not to the product website or other websites you visit.
The developer of See website on mobile is responsible for the extension’s data practices. For privacy questions or requests, contact adrei7650@gmail.com.
The extension works without an account or payment. Its preview and screenshot processing takes place on your device.
2. Data processed by the extension
The extension processes the following information locally in Chrome to provide the features you activate:
- Page addresses and content
- The address, document content and layout of pages you open in the simulator, plus temporary tab and navigation state, are used to display and maintain device previews. The extension does not read Chrome’s browsing-history database.
- Interaction events
- Pointer, scroll, click and permitted keyboard or input events are processed for touch simulation and optional synchronization between device previews. Sensitive inputs, such as recognized password and payment fields, are excluded from input synchronization. These events are not sent to an analytics service.
- Screenshots and annotations
- Images, annotations and editor drafts are processed and temporarily stored on your device. Capture metadata can include the source site’s hostname, device model, image dimensions, tab reference and capture time. Exporting or copying an image is initiated by you.
- Settings and device choices
- Preferences, favorites, custom devices, recent device choices and saved comparison sets are stored in Chrome’s local extension storage. The extension does not use Chrome’s storage sync service.
The extension does not upload the pages you preview, their addresses, your screenshots or interaction events to us. It contains no embedded analytics or advertising service. Websites loaded in a preview still communicate with their own servers as they normally would in your browser.
A screenshot can contain personal or confidential information visible on the page. Review the image and use the editor’s redaction tools before choosing to share it.
3. Why the extension needs permissions
- activeTab: temporarily access the tab where you activate the simulator and capture the screenshots you request.
- scripting: insert the packaged preview interface, styles and device-emulation scripts into the pages you choose.
- storage: save preferences locally and maintain temporary simulation state.
- offscreen: process images, stitch full-page captures and compose device frames in a hidden extension document.
- contextMenus: provide right-click commands for previewing pages and taking screenshots.
- declarativeNetRequestWithHostAccess: apply temporary device-identity request headers and remove framing restrictions from eligible frame responses so a page can open inside the simulator.
- Local file access (file:///*): preview HTML files you open yourself, after you enable Chrome’s “Allow access to file URLs” setting.
- Optional HTTP/HTTPS site access: keep a simulation working when you navigate to other permitted sites. You can grant or revoke this access in Chrome.
Header rules are scoped to the active simulation’s tab and permitted origins. They can adjust User-Agent and related device hints, and remove X-Frame-Options, Content-Security-Policy and Content-Security-Policy-Report-Only from the eligible simulated frame response. Main-frame document requests are not changed. Because the rules are tab-scoped, the underlying page’s subresource requests can also be affected while the simulator is active. Rules are removed when the simulation ends.
On a site you have allowed, a temporary device-identity script registration supports earlier emulation while that site is being simulated. In other tabs on the same site, the script checks for a simulation frame and otherwise does nothing. The registration is removed when no simulation requires it.
4. Use and sharing of extension data
Page content, addresses, interaction events, settings and captured images are used only to provide the preview, device comparison, touch simulation, screenshot and editing features you activate.
The extension does not upload this information to the developer or third-party services. It does not sell this data, use it for advertising or unrelated purposes, or use it to determine creditworthiness or make lending decisions.
You decide whether to export, copy or share a screenshot. If you independently send us an image or other information by email, we receive what you choose to send and use it to respond to your request.
Chrome Web Store Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
5. Local storage and retention
- Settings and device choices remain in Chrome’s local extension storage until you reset them, clear the extension’s data or uninstall it. Chrome storage sync is not used.
- Simulation state, including tab references and navigation information, is temporary. A local-file access handoff may retain the file URL and tab reference for up to ten minutes while you enable access.
- Screenshots and editor drafts are cached locally in IndexedDB. Normal editor cleanup and cache eviction remove temporary records. An interrupted session can leave records until later cleanup or removal of the extension’s data.
- Exported images remain wherever you save them until you delete them. Uninstalling the extension does not remove downloaded files or images you have shared.
We cannot access, retrieve or delete data that exists only in your browser or on your computer.
6. Your choices and privacy rights
You can turn off the simulator, revoke optional site or local-file access, change or reset preferences, delete exported images, and uninstall the extension through Chrome.
If you enable the extension in a private window, Chrome may share extension preferences with your normal profile. Files you save remain on your computer after the private window closes.
Depending on the law that applies to you, you may have rights to access, correct or delete personal information, restrict or object to processing, request portability, or complain to a data-protection authority. Contact adrei7650@gmail.com about information you have directly provided to the developer. We may need limited information to identify the relevant correspondence and verify your request.
For data stored only on your device, use Chrome’s extension controls or uninstall the extension. Keep any exported files you need before deleting them.
7. Websites opened through the extension
Websites you load in the simulator can use their own cookies, storage, accounts and network services, just as when you visit them normally. This activity is governed by those websites’ privacy policies. Local extension processing does not prevent a previewed website from communicating with its own servers.
Installing the extension opens a welcome page. Removing it can open an uninstall-survey page, and selecting Rate us opens either the feedback page or the extension’s Chrome Web Store reviews. These destinations are fixed URLs. The extension does not append the page you were previewing, screenshots or a unique installation identifier to those URLs.
Opening an external page is a normal website visit. Information processed by those websites, or voluntarily submitted through their forms, is outside the scope of this extension policy.
8. Security
Screenshot processing and temporary image storage run in Chrome extension contexts. The extension’s executable code is included in its package. It contains no embedded analytics or advertising service and does not send extension usage reports to the developer.
Protect your device and browser profile, especially on a shared computer. Screenshots may include personal information visible on the page; review and redact them before sharing. No method of storage or transmission is completely secure.
9. Children
See website on mobile is a website-testing tool and is not directed at children under 13. If you believe a child has directly sent personal information to the developer, contact us so we can review and remove it as appropriate.
10. Changes and contact
We will update this policy and its “Last updated” date when the extension’s practices change. Material changes to how the extension handles data will also be disclosed inside the extension before the changed handling begins.
For privacy questions or concerns about the extension, email adrei7650@gmail.com.