FAQ - What data does the Browser Extension track?
This article explains what data the Ploy Browser Extension processes and when each data type is used.
Some data types only apply if your organization has enabled specific features such as anonymous tracking or signup detection.
Authentication and account context
For signed-in users, the extension uses work account details from your Ploy account. This can include your name, work email, member or organization identifiers, profile image URL, and linked identity labels when available. Ploy uses this data to power access management and task workflows in the extension.
Usage tracking
The extension tracks SaaS usage at the domain level for services where Ploy has confirmed a user has an account. It records the domain and the time it was tracked.
For example, Ploy may record that a user visited miro.com on a given date. It does not export full browsing history. Tracking is limited to the domain level, such as notion.so, and is deduplicated to at most once per day per domain.
Anonymous tracking mode
If your organization has enabled anonymous tracking, the extension can detect a work email from supported identity provider or account pages, including Google, Microsoft, and Okta flows. It can then associate tracked SaaS domains with that email before the user signs in to the extension.
This mode only applies when your organization has explicitly provisioned anonymous tracking.
Signup detection and reporting
If your organization has enabled signup detection, the extension may process data when it detects a potential signup to a new SaaS service. This can include the service domain, signup page URL, signup method type, site metadata, and an optional signup email if one appears in the form.
The extension also classifies password strength as low, medium, or high. It does not store the password itself.
If a user sees a modal during signup, Ploy may also collect the answers they provide, such as why they signed up, what kind of data they expect to share, optional free-text responses, and false-positive feedback.
This only applies to signups that match the authenticated user’s work email. Personal signups are ignored.
User extraction and import workflows
When an admin uses extraction or import features, the extension can process extracted user records such as email, optional name, and optional role. It can also send rule-generation context from the current page, including a cleaned HTML snapshot, page metadata, and extraction quality or run metadata.
Ploy uses this data to set up and run account and user inventory import workflows.
Organization controls
Organizations control anonymous tracking through policy configuration and token provisioning. Organizations also control signup detection reporting in the tenant portal.
For an overview of how the extension works, see Browser Extension.