Password Peek - Privacy Policy

Information Password Peek handles

To provide its reveal/hide control, Password Peek may inspect the structure of normal HTTP and HTTPS pages for password input fields and nearby visibility controls. It uses this information only to decide whether to add a local eye button and where to position it.

• Password field presence and display state
• Whether a website already provides a visibility control
• Basic layout information needed to position the eye button
• The current site origin when the user opens a report form

Password Peek does not read, store, transmit, or log the actual password value typed into a field.

Collection, transmission, and storage

Password Peek changes only the local display type of an input field, for example from password to text and back again. This happens in the current page on your device. Password values, form contents, page HTML, authentication tokens, and browsing history are not sent to FrootyStudios or to an analytics, advertising, or tracking service.

Revealed fields are automatically hidden again after 30 seconds, when the page is hidden, or when a form is submitted.

Permissions and why they are used

• HTTP and HTTPS host access - detect password fields on normal websites and add the local show/hide control beside eligible fields.
• contextMenus - provide right-click menu options to report a site issue or request support for a site.
• scripting - run a small packaged helper on eligible web pages after install or update when needed, such as reloading a page so it receives the latest content script.

Password Peek does not access cookies, downloads, bookmarks, clipboard contents, personal communications, or browser history.

Optional issue reports and support requests

Password Peek provides optional report links through its context menu. These links open a Google Form with limited context prefilled:

• Site origin, such as https://example.com
• Issue type
• Extension version

The form may allow you to enter a description or upload a screenshot. Do not include passwords, account secrets, or sensitive personal information in reports. If you choose to submit a report, the information you provide is received by FrootyStudios through Google Forms and is also processed by Google under Google's applicable terms and privacy policy.

Optional uninstall feedback

When Password Peek is uninstalled, Chrome may open an optional feedback form hosted by Google Forms. You may close the page without submitting anything. If you choose to submit feedback, it is used only to understand problems and improve Password Peek.

Third parties and remote code

Password Peek contains no third-party analytics or advertising SDK and does not download or execute remote code. Extension behavior is implemented by packaged JavaScript, CSS, HTML, and image assets included with the extension.

Data sharing and sale

FrootyStudios does not sell Password Peek user data. Password Peek does not share password values, page HTML, form data, or browsing history with FrootyStudios, advertisers, data brokers, or unrelated third parties. Voluntary reports and uninstall feedback are handled as described above.

Data retention and deletion

Password Peek does not persist password-field data in an external service. Local page state ends when the relevant tab or extension context closes. To stop all local processing, close the page, disable Password Peek, or uninstall the extension. For deletion requests concerning feedback or reports you voluntarily submitted, contact us using the address below.

Children's privacy

Password Peek is a general-purpose browser utility and is not directed to children. FrootyStudios does not knowingly use Password Peek to collect personal information from children.

Changes to this policy

If Password Peek's data practices or this policy change, the updated policy will be published on this page with a new "Last updated" date. Material changes will be disclosed as required by applicable Chrome Web Store policies.