Rokt SDK Helper Extension Privacy Notice

Last updated: October 28, 2026.

This notice describes data handling specific to the Rokt SDK Helper Chrome extension and serves as the extension's privacy policy for the purposes of the Chrome Web Store Developer Program Policies. It supplements, and does not replace, the Rokt Privacy Policy and Notice at Collection, which governs Rokt's processing of personal information generally. Where the two differ in respect of the extension, this notice applies.

What this product is

The Rokt SDK Helper is a Chrome extension that developers can use in a Chrome side panel to test a Web SDK+ integration for Rokt Ads and estimate the integration's potential Event Match Quality (EMQ).

Data the Rokt SDK Helper accesses and processes

While the side panel is open, the extension processes information locally from the tab being tested. Depending on the page and integration, this information can include:

• The URL of the tab being tested and changes to that URL.
• Network requests associated with the Rokt SDK+ integration, including requests for the Web SDK+ script, Rokt and mParticle upload requests, and requests to apps.rokt-api.com.
• SDK and page state needed for diagnostics (such as API key presence, initialization status, and sandbox vs production mode).
• Identifiers available in the SDK+ context, such as mParticle ID (mPID), hashed email address, and order or confirmation references.
• Attribute values used to estimate EMQ, including email addresses, names, phone numbers, and location information such as postal code, city, state, and country when available.
• Conversion amounts and currency values used to validate formatting.

The extension requests host access on all sites so it can run on any advertiser domain, including first-party CNAME event endpoints. Network observation is scoped to requests associated with the Rokt SDK+ integration.

The extension does not access or process passwords, authentication cookies, messages, health information, payment card numbers, keystrokes, mouse movements, scrolling activity, GPS location, or browsing data from tabs that are not being tested.

The extension is publicly available and can be operated by anyone, regardless of whether the data environment in the SDK initialization script is configured for production or development. The extension processes the information listed above only on the device of the individual operating it, and does not transmit it to Rokt or to any third party, except for the parts that the optional usage analytics below describes, and only if you turn it on.

Operators should run the extension only against data they are entitled to access. Where a page under test contains personal information belonging to another person, that information is processed only on the operator's device for the diagnostic purposes described in this notice, and is not transmitted by the extension to Rokt, except as described in Usage analytics.

How the Rokt SDK Helper uses data

Apart from the optional usage analytics described below, the Rokt SDK Helper uses the information it processes from the page only to run diagnostic checks in the side panel, estimate the integration's potential EMQ, and generate an optional HTML summary that is saved locally.

If you turn on usage analytics, Rokt uses the usage records only to improve the extension: to see how many people use it and on which sites, which checks fail most often, and whether the extension itself works correctly.

The extension does not use data for advertising, profiling, retargeting, or research.

Usage analytics

Rokt relies on your consent to collect usage analytics. You can withdraw it at any time by turning Share usage analytics off.

Usage analytics is off until you turn it on. The side panel asks you until you choose. The Share usage analytics setting is under the gear icon in the side panel header. When it is off, the extension sends nothing. When you turn it on, the extension also reports the check shown in the side panel at that time. It does not report checks that you only looked at while usage analytics was off.

When usage analytics is on, the extension sends Rokt records about each check and about how the side panel works. A record can contain:

• Random identifiers for the installation, for each check, and for each time the side panel is open. They are not linked to your name, email address, or Google account.
• The domain of the site under test, such as example.com, but never the full web address or path. It is sent only for sites where the Rokt SDK or an API key is found, including when you download a report.
• Whether a Rokt API key was found, and on how many different sites this installation has seen the same key, but never the key itself.
• The check results: which checks failed or warned, how far the funnel got, the EMQ band, and the conversion type names the site uses. A name is replaced with "redacted" if it contains an @ sign, "://" or six or more digits, starts with "www.", or is longer than 64 characters. This filter is best-effort: other personal details in a conversion type name may not be caught.
• How the side panel was used: how long a check was on screen, why it ended (for example, you closed the tab or went to another site), which controls you used, and the type of any error in the panel.
• The extension version, and whether it was installed from the Chrome Web Store or as a developer build.
• Technical details that Datadog adds to every record: the browser and operating system and their versions, the full browser user-agent string, the device type, your language and time zone, the connection type, and the side panel's size, scroll depth, and loading and response times. These describe the side panel itself, not the page under test.

A record never contains:

• The Rokt API key.
• The full web address or path of any page.
• The domain of any other site.
• Any other content or values from the page, including email addresses, names, phone numbers, location, order or confirmation references, mParticle IDs, hashed identifiers, attribute values, or conversion amounts. The one exception is text that a site puts in a conversion type name and that the filter above does not replace, such as a person's name or an order reference with fewer than six digits.
• Error messages or error details.
• Anything from a tab where the side panel was not open.

Data sharing

Apart from the optional usage records described above, Rokt does not share the information the extension processes from the page with any third party.

The Rokt SDK Helper observes network requests made by the page being tested. Apart from the optional usage records described above, it does not transmit those requests or their contents itself, and it does not send a copy of the page data it accesses or processes to Rokt, the extension publisher, or any third party.

If you turn on usage analytics, the extension sends the usage records over HTTPS to Datadog, Inc., a service provider that stores and processes them on Rokt's behalf. The records are stored in the United States. The extension sends them with a Datadog client token that can add records but cannot read them. Datadog receives your IP address as part of the network connection, but Rokt has configured Datadog not to store it or the location derived from it.

Apart from sending usage records to Datadog, the extension uses no other third-party telemetry or analytics. It sends the records with Datadog's browser SDK for Real User Monitoring (RUM), which is included in the extension. The SDK is configured to send only these records and the technical details listed above. It does not record your screen, your clicks, network requests, or errors. Rokt does not sell the usage records or share them with advertising platforms or data brokers.

Storage, retention, and deletion

The extension stores diagnostic results and preferences locally on your device using Chrome storage. This data remains in Chrome storage until you reset it from the side panel or uninstall the extension.

Locally stored diagnostic results are not encrypted. Use the reset control in the side panel after testing against a production environment.

Uninstalling the extension removes its Chrome storage data but does not delete HTML summaries that you previously downloaded.

The extension writes to your clipboard only when you select Copy. It does not read from your clipboard.

Optional HTML summaries are downloaded to your device as local files. The extension does not upload or share these files.

The installation identifier, your usage analytics choice, and each API key found, with shortened hashes of the names of the sites where it was found, are stored in Chrome storage. The hashes are used only to count those sites. The keys and the hashes are never sent. Uninstalling the extension removes them. A new installation creates a new identifier and asks you again.

When usage analytics is on, Datadog's SDK also keeps a random session identifier in the extension's local storage. It expires after 15 minutes without use, is removed when you turn usage analytics off, and is deleted when you uninstall the extension.

Usage records are pseudonymous, not anonymous: every record from one installation has the same installation identifier, and a record can include the domain of the site under test. Apart from the conversion type name exception above, they do not contain your name or email address.

Rokt keeps usage records, including any backup copies, for 90 days, and then they are deleted automatically. The side panel does not show the installation identifier, and the records contain nothing else that identifies you, so Rokt cannot find the records that came from your installation. To stop new records, turn off Share usage analytics or uninstall the extension. For privacy questions or requests about usage records, contact privacy@rokt.com. For other questions about them, contact ads-sdk-helper-publisher@rokt.com.

Security

The Rokt SDK Helper limits the exposure of observed data by processing it locally on your device. The only data it transmits is the optional usage records described above, including the technical details that Datadog adds to them. It sends them over HTTPS with a client token that can add records but cannot read them.

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.

Apart from the optional usage records, the Rokt SDK Helper uses the information it processes from the page only to provide its diagnostic features. It does not use that information for advertising or retargeting, transfer it to third parties, or make it available for review by Rokt personnel.

The optional usage records are used only to improve the extension, as described above. They are transferred only to Datadog as Rokt's service provider. Rokt personnel review them mainly as counts and charts, and can view individual records to investigate errors in the extension.

Changes to this policy

Rokt will update this policy and the Chrome Web Store privacy disclosures before releasing any change that affects how the Rokt SDK Helper accesses, processes, stores, or shares data.

Contact

For questions about the Rokt SDK Helper, contact ads-sdk-helper-publisher@rokt.com. For privacy questions, or to make a request in relation to personal information, contact privacy@rokt.com.