Privacy policy

Data handled

During an explicitly started test, FunnelVerify handles:

• The tested store’s hostname and sanitized page URL.
• Shopify detection signals and limited product context.
• Supported Meta event fields: event name, Pixel ID, timestamp, request status, value, currency, product or content IDs, quantity, content type, event ID, and transaction-related ID when present.
• Funnel progress, findings, and completed report summaries.
• Optional store-specific automation target overrides you save.

URL query strings and fragments are removed before storage. Unknown request fields are discarded.

Data not collected

• Cookies, authentication headers, passwords, or browser history.
• Customer names, email addresses, phone numbers, or postal addresses.
• Payment details or checkout-form contents.
• Complete raw request bodies or unrelated browsing and network activity.
• Shopify Admin data. FunnelVerify does not access Shopify Admin.

Local storage behavior

Active tests are stored in chrome.storage.session and are cleared when the browser session ends. Completed reports and automation targets are stored in chrome.storage.local inside your Chrome profile and survive restarts.

FunnelVerify retains at most 500 normalized events per test and 20 completed tests. The oldest completed test is removed when the limit is exceeded. Reports can be printed or saved as PDF with Chrome’s print dialog; they are not uploaded.

Chrome permissions

• activeTab: inspect the page where you open FunnelVerify.
• scripting: inject packaged detection scripts. No remote code is executed.
• sidePanel: show the guided test interface.
• storage: keep the active test and local reports.
• webRequest: observe—not block or modify—supported Meta Pixel requests during a test.
• Optional host access for https://*/*: requested at test time for the current storefront origin and required Meta tracking origins. It is not granted at installation.

Storefront interactions

Automatic tests may open a product page, add one item using the storefront’s own cart flow, start standard checkout, and attempt to remove that test item. FunnelVerify never clicks Pay now and never places an order. It does not accept cookie consent on your behalf.

Third-party services

This website is static and does not set cookies or load advertising trackers. The extension observes Meta Pixel requests that the tested storefront already sends to Meta. FunnelVerify does not create, modify, or add data to those requests.

After install, the extension may open this tutorial in a normal browser tab. It may also fetch a small JSON config from FunnelVerify’s site to locate the current tutorial URL. That request does not include test reports or store data.

Data retention and user controls

Use Delete local data in the side panel to clear active and completed FunnelVerify data. Removing the extension also removes its Chrome storage.

Children’s privacy

FunnelVerify is not directed at children under 13, and it is not intended for anyone under 16.

Policy updates

This policy will be updated before FunnelVerify adds any backend, account, analytics, or off-device data transfer.

Contact

Privacy questions: support@funnelverify.com

Legal entity and postal address: not published yet.