Privacy Policy — U-Eyes

Last updated: August 16, 2026

In short: U-Eyes simulates mobile devices, takes screenshots, and records video entirely on your device. Screenshots and recordings stay on your computer unless you explicitly click to upload or share them. We do not collect your browsing history, page contents, or personal data, and we never sell or share user data.

This Privacy Policy describes how the U-Eyes: Mobile Simulator browser extension ("the extension", "we", "us") handles data. It applies to the extension as distributed through the Chrome Web Store.

What the extension does

U-Eyes turns the tab you are viewing into a simulated mobile device: it renders the page at the resolution of a phone or tablet you pick, sends a mobile user agent, and lets you capture screenshots (including full-page captures and device mockups) or record the simulated screen as a video. It activates only on the tab where you click the U-Eyes toolbar icon, and it stops when you click the icon again or navigate that tab.

Data the extension accesses

• The page you are simulating. To draw the simulator and capture images or video, the extension works with the content of the tab you activated it on. This happens locally in your browser. Page content is not sent to us, and it is never transmitted anywhere unless you yourself click one of the sharing features described below.
• Screenshots and recordings. Captures are created and held in your browser, and are saved to your computer when you download them. They are not uploaded automatically.
• Settings and preferences. Your chosen device, zoom, theme, and other options are stored in your browser using the extension storage API. If you have Chrome's built-in sync enabled, Chrome may sync this settings data across your own devices through your Google account; that syncing is performed by your browser under Google's privacy policy, not by us.
• Install date and a usage counter. The extension stores the date you installed it and a count of how many times its features have been used, so it can manage free-tier limits and subscription status. These are numbers and a date — they contain no information about which sites you visit or what you capture.

Data we collect

We do not collect your browsing history, the URLs you visit, the contents of pages you simulate, your screenshots, or your recordings. There is no analytics or telemetry in the extension, no advertising, and no error reporting sent to us.

To determine whether a subscription or free-tier limit applies, the extension exchanges a small amount of non-identifying usage data (such as how often it has been used) with our servers when you open the simulator. This does not include your identity, the site you are on, or anything you have captured.

Features that send data, and only when you choose them

• Cloud upload / share link. If you click the upload button on a screenshot or recording, that file is uploaded to Imgur and you receive a shareable link. Uploads are anonymous, but anyone who has the link can view the file, and the file is then subject to Imgur's privacy policy and terms. Do not upload captures containing confidential information. Nothing is uploaded unless you press the button.
• High-resolution resize. If you use the "hi-res" download, the image is handed to a small helper page we host at eyeballer.dev, embedded in your browser, which resizes it client-side. The image is processed in your browser; we do not store it.
• Feedback form. If you fill in the in-app feedback form, the name, email address, and message you type are sent to us through the form provider Formspree so we can reply. We use it only to answer you and improve the extension.
• Subscription. If you choose to subscribe, the payment is handled on our website by our payment provider. We do not receive or store your card details.

Data sharing and selling

We do not sell, rent, or trade user data, and we do not share it with anyone for advertising or profiling. The only data that reaches third parties is what is listed directly above, at the moment you use those features, and solely to provide them.

Why the extension requests its permissions

• activeTab and scripting — required to build the simulator inside the tab you are on. The extension injects its code only into the tab where you click its icon, not into every page you browse.
• tabCapture and offscreen — required for the screenshot and screen-recording features. The offscreen document is the place Chrome requires media recording to run for Manifest V3 extensions. Captured frames stay in your browser.
• declarativeNetRequest — used to make the simulation accurate: for the tab you activated, it sets a mobile user-agent header so sites serve their mobile version, and removes the X-Frame-Options response header so the page can be displayed inside the simulated device frame. The rule is applied locally by your browser and is scoped to that tab; it is removed as soon as you turn the simulator off. The extension cannot read, intercept, or record the contents of your network traffic.
• declarativeNetRequestFeedback — used only during development to verify that the above rule matched correctly. It does not send anything anywhere.
• storage — required to save your settings and the free-tier counters locally in your browser.

Chrome Web Store user data policy

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Children

The extension is a developer and designer utility and is not directed at children. It does not knowingly collect personal information from anyone, including children.

Changes to this policy

If our data practices change, we will update this page and revise the "Last updated" date above.

Contact

Questions about this policy or the extension? Email us at tmtk.apps@gmail.com.