Is Plan To Eat Recipe Clipper safe?

Clean risk

Plan To Eat Recipe Clipper sends the active page URL and full page HTML to Plan to Eat when you import a recipe.

When you click the Import button, the extension asks the active tab for its current URL and the page's full HTML. It sends both values as recipe import data to Plan to Eat's imported recipe API.

Plan to Eatv1.1.1Chrome Web Store
2Risk
Who publishes it

Plan to Eat, LLC - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
Plan to Eat
Declared legal entity
Plan to Eat, LLC
Registered address
789 West 10th Street, Loveland, CO 80537, US

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 1.1.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every site you visit

    *://*/*

  • Act on the current tab, but only after you click the extension

    activeTab

  • See the address and title of every tab you have open

    tabs

  • Show a panel beside the page

    sidePanel

  • Run its own code inside the pages you visit

    scripting

Where it sends data

Destinations our analysis observed Plan To Eat Recipe Clipper contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • app.plantoeat.com/api/v1/imported_recipe

    Plan To Eat Recipe Clipper sends data to app.plantoeat.com/api/v1/imported_recipe. No other extension we have analysed sends data here.

Updated 30 September 2026pnlpbkniadcljbhebdjokkkeobenpefj